CN107391377B - Method for testing software integration based on combined flow chart - Google Patents
Method for testing software integration based on combined flow chart Download PDFInfo
- Publication number
- CN107391377B CN107391377B CN201710618329.8A CN201710618329A CN107391377B CN 107391377 B CN107391377 B CN 107391377B CN 201710618329 A CN201710618329 A CN 201710618329A CN 107391377 B CN107391377 B CN 107391377B
- Authority
- CN
- China
- Prior art keywords
- flow chart
- data
- logic
- written
- bit rate
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method for testing software integration based on a combined flow chart, which comprises the following steps: (1) acquiring program flows of all systems used in combination; (2) drawing a flow chart according to a program flow and combining; (3) arranging data logic and business logic among different systems according to the flow chart; (4) and performing source tracing verification on each system according to the data logic and the service logic. The method is visual and intuitive, various operations are clear at a glance, no ambiguity is generated, the method is convenient to understand, the algorithm is easy to find when in error, and the algorithm can be directly converted into a program.
Description
Technical Field
The invention relates to the field of software testing, in particular to a method for testing software integration based on a combined flow chart.
Background
Each software product or software development project needs an excellent set of test schemes and test methods. The test case is the guide of the test work, is the criterion that the software test must obey, and is the fundamental guarantee of the stable quality of the software test. A Test Case (Test Case) is a set of Test inputs, execution conditions, and expected results tailored for a particular target to Test a certain program path or verify whether a certain specific requirement is met. The importance of software testing is undoubted. However, how to complete the test in the shortest time with the least input of manpower and resources, find the defects of the software system and ensure the good quality of the software is the target of the exploration and pursuit of the software company.
However, as software continues to evolve, more and more software systems are integrated, i.e., relatively independent and interdependent. For such an integrated software system, how to complete the test in the shortest time with the least investment of manpower and resources, find the defects of the software system, and ensure the excellent quality of the software is a problem to be solved urgently.
Disclosure of Invention
The invention aims to: aiming at the problems in the prior art, the method for testing software integration based on the combined flow chart is provided, and the problem of how to test the integrated software system with low cost, high efficiency and high quality is solved.
The invention aims to be realized by the following technical scheme:
a method for testing software integration based on a combined flow diagram, the method comprising:
(1) acquiring program flows of all systems used in combination;
(2) drawing a flow chart according to a program flow and combining;
(3) arranging data logic and business logic among different systems according to the flow chart;
(4) and performing source tracing verification on each system according to the data logic and the service logic.
As a further technical solution, the definition of the drawing flow chart is as follows: start and end marks, characterized by oval symbols, for indicating the start or end of a process, the "start" or "end" being written within the symbols; an activity flag, characterized by a rectangle symbol, for indicating that at a single step of the process, a brief description of the activity is written within the rectangle; the decision mark is characterized by a diamond symbol and is used for representing a decision or a bifurcation point in the process, and the description of the decision or the bifurcation is written in the diamond; a streamline indicator represented by a line with an arrow to indicate the progress of the step in the sequence, the arrow of the streamline indicating the flow direction of one process; the file mark is characterized by brackets and is used for representing written information belonging to the process, and the title or the description of the file is written in the symbol; the connection mark is characterized by a circle symbol and is used for representing the standby of the flow chart, a letter or a number is arranged in the circle, and the same letter or number is used for the connection mark in the interconnected flow charts to represent how the processes are connected.
As a further technical solution, the data logic and the service logic include: the data presented by the system A is acquired by the system B in two modes of automatic discovery or manual configuration; the data automatically acquired by the system B is the number of bytes and the time range, and the data required to be presented and recorded into the database by the system A is the bit rate.
As a further technical solution, the tracing verification includes: and finding the byte number and the time range of the data provided on the page of the system B, and obtaining the bit rate through an algorithm so as to verify the function and the data of the system A.
As a further technical solution, the algorithm for obtaining the bit rate is: the bit rate is the number of bytes (B) × 8/time or the bit rate is the number of bytes (KB) × 1024 × 8/time.
Compared with the prior art, the method is visual and intuitive, various operations are clear at a glance, no ambiguity is generated, the method is convenient to understand, the algorithm is easy to find when in error, and the algorithm can be directly converted into a program.
Drawings
FIG. 1 is a flow chart of a combination of different system processes.
Detailed Description
The invention is described in detail below with reference to the figures and specific embodiments.
Example 1
The applicant researches and discovers that: before the different systems are used in an integrated mode, most of the different systems pass the test of the systems. Therefore, the test key points of different system integration are not that all integrated software programs are tested once, so that the human resources are wasted, and the final test effect is not remarkable. For this case, the flow chart can be used to arrange the data logic and the business logic between different systems. By utilizing the advantages of visual image and clear operation, under the visual logic, the test case is rapidly perfected, the test key is grasped, and the purpose of high-efficiency test is achieved.
Based on the foregoing research, the applicant provides a method for testing software integration based on a combined flowchart in the present invention, as shown in fig. 1, the method includes:
step 1, acquiring program flows of all systems used in combination;
step 2, drawing a flow chart according to the program flow and combining the flow chart;
step 3, data logic and service logic among different systems are arranged according to the flow chart;
and 4, performing source tracing verification on each system according to the data logic and the service logic.
Example 2
The applicant researches and discovers that: before the different systems are used in an integrated mode, most of the different systems pass the test of the systems. Therefore, the test key points of different system integration are not that all integrated software programs are tested once, so that the human resources are wasted, and the final test effect is not remarkable. For this case, the flow chart can be used to arrange the data logic and the business logic between different systems. By utilizing the advantages of visual image and clear operation, under the visual logic, the test case is rapidly perfected, the test key is grasped, and the purpose of high-efficiency test is achieved.
Based on the foregoing research, the applicant provides a method for testing software integration based on a combined flowchart in the present invention, as shown in fig. 1, the method includes:
and step 1, acquiring program flows of all systems used in combination.
And 2, drawing a flow chart according to the program flow and combining the flow chart. The definition of the drawing flow chart is as follows: start and end marks, characterized by oval symbols, for indicating the start or end of a process, the "start" or "end" being written within the symbols; an activity flag, characterized by a rectangle symbol, for indicating that at a single step of the process, a brief description of the activity is written within the rectangle; the decision mark is characterized by a diamond symbol and is used for representing a decision or a bifurcation point in the process, and the description of the decision or the bifurcation is written in the diamond; a streamline indicator represented by a line with an arrow to indicate the progress of the step in the sequence, the arrow of the streamline indicating the flow direction of one process; the file mark is characterized by brackets and is used for representing written information belonging to the process, and the title or the description of the file is written in the symbol; the connection mark is characterized by a circle symbol and is used for representing the standby of the flow chart, a letter or a number is arranged in the circle, and the same letter or number is used for the connection mark in the interconnected flow charts to represent how the processes are connected.
And 3, organizing data logic and service logic among different systems according to the flow chart.
And 4, performing source tracing verification on each system according to the data logic and the service logic.
Example 3
The applicant researches and discovers that: before the different systems are used in an integrated mode, most of the different systems pass the test of the systems. Therefore, the test key points of different system integration are not that all integrated software programs are tested once, so that the human resources are wasted, and the final test effect is not remarkable. For this case, the flow chart can be used to arrange the data logic and the business logic between different systems. By utilizing the advantages of visual image and clear operation, under the visual logic, the test case is rapidly perfected, the test key is grasped, and the purpose of high-efficiency test is achieved.
Based on the foregoing research, the applicant provides a method for testing software integration based on a combined flowchart in the present invention, as shown in fig. 1, the method includes:
and step 1, acquiring program flows of all systems used in combination.
And 2, drawing a flow chart according to the program flow and combining the flow chart. The definition of the drawing flow chart is as follows: start and end marks, characterized by oval symbols, for indicating the start or end of a process, the "start" or "end" being written within the symbols; an activity flag, characterized by a rectangle symbol, for indicating that at a single step of the process, a brief description of the activity is written within the rectangle; the decision mark is characterized by a diamond symbol and is used for representing a decision or a bifurcation point in the process, and the description of the decision or the bifurcation is written in the diamond; a streamline indicator represented by a line with an arrow to indicate the progress of the step in the sequence, the arrow of the streamline indicating the flow direction of one process; the file mark is characterized by brackets and is used for representing written information belonging to the process, and the title or the description of the file is written in the symbol; the connection mark is characterized by a circle symbol and is used for representing the standby of the flow chart, a letter or a number is arranged in the circle, and the same letter or number is used for the connection mark in the interconnected flow charts to represent how the processes are connected.
And 3, organizing data logic and service logic among different systems according to the flow chart. The data logic and the service logic comprise: the data presented by the system A is acquired by the system B in two modes of automatic discovery or manual configuration; the data automatically acquired by the system B is the number of bytes and the time range, and the data required to be presented and recorded into the database by the system A is the bit rate.
And 4, performing source tracing verification on each system according to the data logic and the service logic.
Example 4
The applicant researches and discovers that: before the different systems are used in an integrated mode, most of the different systems pass the test of the systems. Therefore, the test key points of different system integration are not that all integrated software programs are tested once, so that the human resources are wasted, and the final test effect is not remarkable. For this case, the flow chart can be used to arrange the data logic and the business logic between different systems. By utilizing the advantages of visual image and clear operation, under the visual logic, the test case is rapidly perfected, the test key is grasped, and the purpose of high-efficiency test is achieved.
Based on the foregoing research, the applicant provides a method for testing software integration based on a combined flowchart in the present invention, as shown in fig. 1, the method includes:
and step 1, acquiring program flows of all systems used in combination.
And 2, drawing a flow chart according to the program flow and combining the flow chart. The definition of the drawing flow chart is as follows: start and end marks, characterized by oval symbols, for indicating the start or end of a process, the "start" or "end" being written within the symbols; an activity flag, characterized by a rectangle symbol, for indicating that at a single step of the process, a brief description of the activity is written within the rectangle; the decision mark is characterized by a diamond symbol and is used for representing a decision or a bifurcation point in the process, and the description of the decision or the bifurcation is written in the diamond; a streamline indicator represented by a line with an arrow to indicate the progress of the step in the sequence, the arrow of the streamline indicating the flow direction of one process; the file mark is characterized by brackets and is used for representing written information belonging to the process, and the title or the description of the file is written in the symbol; the connection mark is characterized by a circle symbol and is used for representing the standby of the flow chart, a letter or a number is arranged in the circle, and the same letter or number is used for the connection mark in the interconnected flow charts to represent how the processes are connected.
Fig. 1 is a flow chart of a combination of two systems.
And 3, organizing data logic and service logic among different systems according to the flow chart. The data logic and the service logic comprise: the data presented by the system A is acquired by the system B in two modes of automatic discovery or manual configuration; the data automatically acquired by the system B is the number of bytes and the time range, and the data required to be presented and recorded into the database by the system A is the bit rate.
For example, it is obvious from fig. 1 that the data presented by system a is obtained by system B through automatic discovery or manual configuration.
And 4, performing source tracing verification on each system according to the data logic and the service logic. The source tracing verification comprises the following steps: and finding the byte number and the time range of the data provided on the page of the system B, and obtaining the bit rate through an algorithm so as to verify the function and the data of the system A. The algorithm to get the bit rate is: the bit rate is the number of bytes (B) × 8/time or the bit rate is the number of bytes (KB) × 1024 × 8/time.
For example, according to the detailed design of the system A, B in fig. 1, the logical method of data integration of the system is grasped: the data automatically acquired by the system B is the byte number and the time range, and the byte number and the time range are displayed on the page. System a requires the data presented and entered into the database to be at the bit rate. The algorithm is as follows: the bit rate is the number of bytes (B) × 8/time, the bit rate is the number of bytes (KB) × 1024 × 8/time, and so on. And compiling a test case, performing source tracing verification in an acquisition mode provided by the system B when verifying the function and the data correctness, finding the number of bytes and the time range of data provided on a page of the system B, and obtaining the bit rate through an algorithm so as to verify the function and the data of the system A.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, it should be noted that any modifications, equivalents and improvements made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (3)
1. A method for testing software integration based on a combined flow diagram, the method comprising:
(1) acquiring program flows of all systems used in combination;
(2) drawing a flow chart according to a program flow and combining;
(3) arranging data logic and business logic among different systems according to the flow chart; the data logic and the service logic comprise: the data presented by the system A is acquired by the system B in two modes of automatic discovery or manual configuration; the data automatically acquired by the system B is the number of bytes and the time range, and the data which needs to be presented and input into the database by the system A is the bit rate;
(4) performing source tracing verification on each system according to the data logic and the service logic; the source tracing verification comprises the following steps: and finding the byte number and the time range of the data provided on the page of the system B, and obtaining the bit rate through an algorithm so as to verify the function and the data of the system A.
2. The method of claim 1, wherein the flow chart is defined as follows:
start and end marks, characterized by oval symbols, for indicating the start or end of a process, the "start" or "end" being written within the symbols;
an activity flag, characterized by a rectangle symbol, for indicating that at a single step of the process, a brief description of the activity is written within the rectangle;
the decision mark is characterized by a diamond symbol and is used for representing a decision or a bifurcation point in the process, and the description of the decision or the bifurcation is written in the diamond;
a streamline indicator represented by a line with an arrow to indicate the progress of the step in the sequence, the arrow of the streamline indicating the flow direction of one process;
the file mark is characterized by brackets and is used for representing written information belonging to the process, and the title or the description of the file is written in the symbol;
the connection mark is characterized by a circle symbol and is used for representing the standby of the flow chart, a letter or a number is arranged in the circle, and the same letter or number is used for the connection mark in the interconnected flow charts to represent how the processes are connected.
3. The method of claim 1, wherein the bit rate is derived from an algorithm comprising: the bit rate is the number of bytes (B) × 8/time or the bit rate is the number of bytes (KB) × 1024 × 8/time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710618329.8A CN107391377B (en) | 2017-07-26 | 2017-07-26 | Method for testing software integration based on combined flow chart |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710618329.8A CN107391377B (en) | 2017-07-26 | 2017-07-26 | Method for testing software integration based on combined flow chart |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107391377A CN107391377A (en) | 2017-11-24 |
| CN107391377B true CN107391377B (en) | 2021-01-05 |
Family
ID=60341686
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710618329.8A Active CN107391377B (en) | 2017-07-26 | 2017-07-26 | Method for testing software integration based on combined flow chart |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107391377B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109190992A (en) * | 2018-09-14 | 2019-01-11 | 成都信息工程大学 | A kind of generation method and device of the operation flow based on use-case |
| CN117172256B (en) * | 2023-07-31 | 2024-03-12 | 台州道致科技股份有限公司 | Laboratory management method and system based on modularized setting |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101645012A (en) * | 2009-09-11 | 2010-02-10 | 兰雨晴 | Combinational selection method of foundational software platform integrated test |
| CN104850490B (en) * | 2014-02-18 | 2017-11-24 | 国际商业机器公司 | Method and system for software test |
| CN104407971B (en) * | 2014-11-18 | 2017-04-12 | 中国电子科技集团公司第十研究所 | Method for automatically testing embedded software |
| CN105786695B (en) * | 2014-12-26 | 2019-09-17 | 北大医疗信息技术有限公司 | Data test method and system |
| CN105677563B (en) * | 2016-01-05 | 2018-08-14 | 南昌航空大学 | A kind of integration testing sequence generating method based on SysML module maps |
-
2017
- 2017-07-26 CN CN201710618329.8A patent/CN107391377B/en active Active
Non-Patent Citations (2)
| Title |
|---|
| Ye Wu等.UML-Based Integration Testing for Component-Based Software.《International Conference on COTS-Based Software Systems 》.2003, * |
| 集成测试与***测试方法;王亮;《舰船标准化工程师》;20070726(第3期);第31-34页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107391377A (en) | 2017-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105868171B (en) | A kind of method of calibration and device of Excel file | |
| CN109086199B (en) | Method, terminal and storage medium for automatically generating test script | |
| CN102279749B (en) | Method and equipment for merging codes | |
| US20130262934A1 (en) | Method and apparatus for automatically generating a test script for a graphical user interface | |
| CN103838672A (en) | Automated testing method and device for all-purpose financial statements | |
| CN104182335A (en) | Software testing method and device | |
| CN103530223A (en) | Method and device for automatically generating unit test cases | |
| CN106649239A (en) | Method and device for generating report in cloud monitoring system based on visualization | |
| CN106919612A (en) | A kind of processing method and processing device of SQL script of reaching the standard grade | |
| CN107391377B (en) | Method for testing software integration based on combined flow chart | |
| US20150261505A1 (en) | Method and system for generating stateflow models from software requirements | |
| CN104375934A (en) | Method for testing reliability of Android mobile phone software | |
| CN111061696A (en) | Method and device for analyzing transaction message log | |
| CN106325596A (en) | Automatic handwriting error correction method and system | |
| CN111325031B (en) | Resume analysis method and device | |
| CN110069279A (en) | Method and device for checking direct current control protection program and storage medium | |
| CN103136103A (en) | Test case reduction method for error locating demand | |
| CN103440197B (en) | A kind of method automatically generating difference test report based on contrast test | |
| CN103617122B (en) | A kind of comparison method of source code | |
| CN103761095A (en) | Method for generating universal header data information of upgraded file | |
| CN111309791A (en) | Automatic data acquisition method for detection instrument | |
| CN103913672A (en) | Satellite low-frequency interface automatic testing system | |
| CN106201790A (en) | A kind of adjustment method based on DSDT table and debugging system | |
| CN112860913A (en) | Ontology creation method of knowledge graph | |
| CN104536897A (en) | Automatic testing method and system based on keyword |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 610041 No. 06, floor 15, unit 2, building 1, No. 28, north section of Tianfu Avenue, Chengdu hi tech Zone, China (Sichuan) pilot Free Trade Zone, Chengdu, Sichuan Patentee after: Chengdu Shumo Technology Co.,Ltd. Address before: 13 / F and 14 / F, unit 1, building 4, No. 966, north section of Tianfu Avenue, high tech Zone, Chengdu, Sichuan 610041 Patentee before: COLASOFT Co.,Ltd. |
|
| CP03 | Change of name, title or address | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220406 Address after: 610041 12th, 13th and 14th floors, unit 1, building 4, No. 966, north section of Tianfu Avenue, high tech Zone, Chengdu, Sichuan Patentee after: Kelai Network Technology Co.,Ltd. Address before: 610041 No. 06, floor 15, unit 2, building 1, No. 28, north section of Tianfu Avenue, Chengdu hi tech Zone, China (Sichuan) pilot Free Trade Zone, Chengdu, Sichuan Patentee before: Chengdu Shumo Technology Co.,Ltd. |
|
| TR01 | Transfer of patent right |