CN117370196A - Agile development automatic test method and system - Google Patents
Agile development automatic test method and system Download PDFInfo
- Publication number
- CN117370196A CN117370196A CN202311397667.5A CN202311397667A CN117370196A CN 117370196 A CN117370196 A CN 117370196A CN 202311397667 A CN202311397667 A CN 202311397667A CN 117370196 A CN117370196 A CN 117370196A
- Authority
- CN
- China
- Prior art keywords
- test
- functional
- script
- case
- test case
- 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.)
- Pending
Links
- 238000011161 development Methods 0.000 title claims abstract description 24
- 238000010998 test method Methods 0.000 title claims abstract description 10
- 238000012360 testing method Methods 0.000 claims abstract description 296
- 238000013515 script Methods 0.000 claims abstract description 134
- 238000011990 functional testing Methods 0.000 claims abstract description 107
- 238000000034 method Methods 0.000 claims abstract description 34
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 230000006870 function Effects 0.000 description 39
- 238000012423 maintenance Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 230000007613 environmental effect Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 238000012430 stability testing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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
- G06F11/3684—Test management for test design, e.g. generating new test cases
Abstract
The invention provides an agile development automatic test method and system, wherein the method comprises the steps of obtaining functional test requirements of different versions to be tested, establishing a plurality of functional test cases, and generating a unique test case ID for each functional test case; correspondingly generating a test script for each functional test case; constructing an association relation between test script information and the ID of the test case to which the test script information belongs; acquiring test script information associated with the read test case ID according to the read test case ID, calling a corresponding test script and executing a test module in the test script; and storing the execution result and generating a result report of the test execution. The invention solves the problem that in the prior art, under the condition that the functional test case and the automatic test script form independent systems respectively, effective matching and collaborative management are difficult to carry out; as demand changes or version updates are frequent, the efficiency of responding to changes is low.
Description
Technical Field
The invention relates to the technical field of automatic testing, in particular to an agile development automatic testing method and system.
Background
In the agile development process of software projects, it is important to ensure comprehensive, continuous and timely feedback of the software quality condition; as each iteration proceeds, the development of new functions, the repair of defects, and the reconstruction of code are all unavoidable. Therefore, the regression test is required to ensure that the history function is not affected while the current iteration new characteristic test is completed. However, relying on manual, complete and timely regression testing is often an impossible task to accomplish, subject to objective resource and time constraints; to address this challenge, automated testing is a key means to improve the efficiency of regression testing, stability testing, and compatibility testing. The automatic test plays a role in guaranteeing the product quality and realizing continuous construction, and is an indispensable part in particular in a agile development mode, however, the conventional test tools have some disadvantages:
conventional UI automation test based on recording-playback tools is still page source code-oriented for writing or generating test scripts, specifically, the test scripts generated by the recording tools are generally only applicable to specific tools, and have poor maintainability, and once the functions or user interfaces of the applications change, the recorded scripts may not normally run, so that a test team is forced to re-record new scripts, thereby increasing maintenance cost and reducing test efficiency. Secondly, the script technology based on an automatic test framework solves the problem of poor maintainability of recorded scripts, but a tester needs to be familiar with the use of tools such as XPath, testNG and the like besides mastering a Webdriver interface, so that a plurality of companies need to use full-time function test engineers and automatic test engineers, and the respectively written function use cases and the test scripts lack unified management and internal association; in addition, under the condition that the requirements are frequently changed and the release of the version is frequent, the test script is difficult to update in time by a tester; thereby causing a hysteresis in the test script and increasing the time cost in coping with the change.
The existing automatic test system solves the management problems of the function use cases and the automatic scripts, but the function use cases and the automatic scripts still form a set of system respectively, and the function use cases and the automatic scripts operate independently and are difficult to match effectively; the functional test engineer and the automated test engineer still need to be maintained separately and fail to achieve an efficient response to the change. In addition, the test report of the existing platform only reflects whether the execution of the script passes or not, and the coverage and execution condition of the functional use cases cannot be fully displayed.
Disclosure of Invention
Aiming at the defects existing in the prior art, the invention provides a agile development automatic test method and system, which solve the problems existing in the prior art: under the condition that the functional test cases and the automatic test scripts respectively form independent systems, effective matching and collaborative management are difficult to carry out on the functional test cases and the automatic test scripts; as demand changes or version updates are frequent, the efficiency of responding to changes is low.
In one aspect, an embodiment of the present invention provides an agile development automation test method, including the steps of:
step A, obtaining functional test requirements of different versions to be tested, establishing a plurality of functional test cases based on the functional test requirements of the versions to be tested, and generating a unique test case ID for each functional test case;
step B, correspondingly generating a test script for each functional test case, wherein the test script comprises a plurality of method modules, and the method modules are formed by packaging test codes corresponding to each functional test case;
step C, constructing an association relation between test script information and the ID of the test case, wherein the test script information comprises a test script name and a method module name;
step D, reading the test case ID of the functional test case in the version to be tested, acquiring the test script information associated with the read test case ID according to the read test case ID, calling the corresponding test script and executing the test module therein;
and E, storing the execution result and generating a result report of the test execution.
Preferably, all the test scripts generated in the step B are stored, and a plurality of corresponding test scripts are established along with the iterative updating of different versions; the test script is used for testing a plurality of functional test cases corresponding to one functional test requirement or a plurality of functional test cases corresponding to a plurality of functional test requirements.
Preferably, in step C, the association relationship between the test script information and the test case ID is constructed: and adding the test script name and the method module name of the test case ID to the corresponding functional test case.
Preferably, in step E, after all the test scripts are executed, the test result of the execution is recorded to refer to the corresponding result report.
Preferably, the information of the test report includes: error reporting information, test case pass information and coverage information.
On the other hand, the embodiment of the invention also provides an agile development automatic test system, which comprises:
and the use case management module is used for: the method comprises the steps of acquiring functional test requirements of different versions to be tested, establishing a plurality of functional test cases based on the functional test requirements of the versions to be tested, and generating a unique test case ID for each functional test case;
script management module: the test script is correspondingly generated for each functional test case;
an environment configuration module: the method is used for configuring required environment variables according to the test script information, and adding environment variable parameters when executing the test script;
and the test execution module is used for: the test case ID is used for reading the function test case in the version to be tested, calling the corresponding test script and executing the test module therein;
a report generation module: and the method is used for storing the execution result and generating a result report of the test execution.
Preferably, the case management module is further configured to manage the running states of the plurality of functional test cases in the version to be tested:
acquiring historical version information, and searching for historical function test requirements and historical function test cases corresponding to the historical version;
copying the function test cases corresponding to the historical versions to generate the function test cases of the versions to be tested;
comparing the functional test requirements of the version to be tested with the functional test requirements of the historical version, and finding out the newly added, cancelled or changed functional test requirements in the version to be tested according to the comparison result;
setting an operation state to be an enabling state for a function test case corresponding to the newly-increased function test requirement; and setting the running state of the functional test case corresponding to the canceling or changing functional test requirement to be a disabled state.
Preferably, the test execution module performs a test further comprising: and searching a functional test case with the running state being an enabling state in the version to be tested, positioning the test script name and the method module name associated with the functional test case by reading the test case ID of the functional test case, calling the corresponding test script and executing the test module in the test script.
Preferably, the environment configuration module adds environment variable parameters for executing the test script, including specific parameters of access address, user name and user password.
Preferably, the report generating module further comprises: after all the test scripts are executed, recording the test results of the execution to consult the corresponding result report.
Compared with the prior art, the invention has the following beneficial effects:
1. the system testing efficiency is improved: the test personnel does not need to completely rely on the test script coding personnel to modify the test script codes, the requirement of the version test can be met by modifying the start and stop of the state of the functional use case, the system test personnel can manage the test content more flexibly, and the working efficiency of the test personnel is obviously improved. Meanwhile, an automatic script developer does not need to maintain a plurality of scripts of different versions any more, and only needs to iterate continuously in one set of scripts, so that convenience in script maintenance is improved.
2. Optimizing resource utilization and reducing execution time: and each test script execution no longer needs to run all contents in the script in full quantity, so that the consumption of resources is effectively reduced, and the time required for execution is shortened. The test execution is more efficient, and particularly in a regression test scene, the functional test cases to be tested can be selectively executed, so that unnecessary execution is avoided, and the overall execution efficiency is improved.
3. The test result is more visual: through the test script result report, the test script result report can be reversely related to the function use case, so that the execution result of the version of the function test is intuitively reflected. The relevance enables other people who do not understand the technology but understand the business to clearly understand the passing and coverage conditions of the version functional test, and improves the communication and understanding effects among the cross-team.
Drawings
FIG. 1 is a schematic flow chart of an automated testing method for agile development according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a framework of an agile development automation test system according to an embodiment of the present invention.
Detailed Description
The technical scheme of the invention is further described below with reference to the accompanying drawings.
As shown in fig. 1, the embodiment of the invention provides an agile development automation test method, which comprises the following steps:
step A, obtaining functional test requirements of different versions to be tested, establishing a plurality of functional test cases based on the functional test requirements of the versions to be tested, and generating a unique test case ID for each functional test case;
step B, correspondingly generating a test script for each functional test case, wherein the test script comprises a plurality of method modules, and the method modules are formed by packaging test codes corresponding to each functional test case;
step C, constructing an association relation between test script information and the ID of the test case, wherein the test script information comprises a test script name and a method module name;
step D, reading the test case ID of the functional test case in the version to be tested, acquiring the test script information associated with the read test case ID according to the read test case ID, calling the corresponding test script and executing the test module therein;
and E, storing the execution result and generating a result report of the test execution.
Preferably, all the test scripts generated in the step B are stored, and a plurality of corresponding test scripts are established along with the iterative updating of different versions; the test script is used for testing a plurality of functional test cases corresponding to one functional test requirement or a plurality of functional test cases corresponding to a plurality of functional test requirements.
It should be noted that, the test script of the previous version may be based, and if the current version has no new function with respect to the previous version, no editing or modification is required. If the current version adds the function, only adding codes corresponding to the test script of the added function; while reduced or modified functional portions may be retained without requiring additional maintenance work on the test script. With the iteration of the versions, all historical versions of the test script are always reserved so as to ensure that different versions can be called for execution at any time.
As shown in fig. 2, an embodiment of the present invention further provides an agile development automation test system, including:
and the use case management module is used for: the method comprises the steps of acquiring functional test requirements of different versions to be tested, establishing a plurality of functional test cases based on the functional test requirements of the versions to be tested, and generating a unique test case ID for each functional test case;
script management module: the test script is correspondingly generated for each functional test case;
an environment configuration module: the method is used for configuring required environment variables according to the test script information, and adding environment variable parameters when executing the test script;
and the test execution module is used for: the test case ID is used for reading the function test case in the version to be tested, calling the corresponding test script and executing the test module therein;
a report generation module: and the method is used for storing the execution result and generating a result report of the test execution.
The case management module is further configured to manage an operation state of the plurality of functional test cases in the version to be tested:
step S1, acquiring history version information, and searching a history function test requirement and a history function test case corresponding to the history version;
s2, copying the function test cases corresponding to the historical versions to generate the function test cases of the versions to be tested;
step S3, comparing the functional test requirements of the version to be tested with the functional test requirements of the historical version, and finding out the newly added, cancelled or changed functional test requirements in the version to be tested according to the comparison result;
s4, setting the running state of the function test case corresponding to the newly added function test requirement as an enabling state; and setting the running state of the functional test case corresponding to the canceling or changing functional test requirement to be a disabled state.
It should be noted that, the case management module can perform comprehensive management on functional test cases of different versions, not only basically except for adding, deleting and checking operations, but also supports batch copying of all functional test cases of a certain version into the current version to be tested, and can quickly establish similar test cases between different versions, so that the functional test cases of the current version to be tested are more convenient to manage, cumbersome steps of creating one by one are omitted, and management efficiency is improved.
The test execution module performing a test further includes: and searching a functional test case with the running state being an enabling state in the version to be tested, positioning the test script name and the method module name associated with the functional test case by reading the test case ID of the functional test case, calling the corresponding test script and executing the test module in the test script.
When the test script starts to be executed, firstly, reading functional test cases with the running state being enabled in the version to be tested, searching the test case ID of each enabled functional test case, and associating the ID with the corresponding test script name and method module name; and then, acquiring the names of the method modules associated with the functional test cases in the test script, and executing the corresponding test methods one by one according to the method names, wherein if a method matched with the acquired method names cannot be found in the test script, the execution of the method is skipped, so that only the test steps related to the current test requirements are executed, and the accuracy and the efficiency of the test are improved.
Under a specific condition, if the deletion function in the version 1.0 is obtained, creating a corresponding function test case and a test script according to the deletion function; whereas in version 1.1 the delete function is cancelled. In the conventional art, it is necessary to modify and maintain test script codes related to the deletion function; however, in the technical scheme of the invention, only the running state of the functional test case is switched to be disabled, the test script code is not required to be modified, the test script can be directly executed later, and the test script code corresponding to the disabled functional test case is not executed any more, so that the workload and time cost required for maintaining the test script are obviously reduced, the agility of the whole test flow is improved, and the team can respond to the changing requirement in the project more quickly.
The environment configuration module adds environment variable parameters for executing the test script, wherein the environment variable parameters comprise specific parameters of access address, user name and user password.
It should be noted that, in the process of developing a script, considering that the script may be executed in a plurality of test environments, and the access address and the user information of the application system in different test environments may be different, the address, the user name and the password are set as configurable environment variables: "URL", "USER" and "PASSWORD".
In a specific implementation, a tester may create a specific test environment for a test item, add environmental variable parameters when the test script is executed:
the "URL" variable is set to "http://192.168.0.1:8080" to define the access address of the test,
the "USER" variable is set to "test01" to define the USER name used in the test,
setting the "PASSWORD" variable to "qwe-! @ # "to define the user password used in the test.
When the script is executed, the environment configuration module can dynamically transfer corresponding address, user name and password parameters according to the specific requirements of the current test environment, flexibly configure variable data according to the needs, and ensure that the test can be executed correctly and effectively in each environment.
The report generation module records the test result of the execution after the test script is completely executed so as to consult the corresponding result report; the information of the test report includes: error reporting information, test case pass information and coverage information.
It should be noted that, the information of the test report also includes the name of the functional test case and the test case ID, so that the tester can locate a specific functional test case according to the test result; the test report records the information of whether each test case passes the test successfully, and the corresponding error information is recorded for each test case which fails the test, so that a developer or a tester can quickly locate and repair the problem. Secondly, through the starting or stopping state of the obtained functional test cases, which functional test cases are tested and which functional test cases are not tested can be checked. Meanwhile, the coverage information of the functional test cases can be reflected through the test report, namely, the duty ratio data of the functional test cases which are tested and the overall functional test cases are calculated.
The application scene of the invention is as follows:
scene one: a company develops a set of mature OA systems with landing projects in multiple provinces and cities throughout the country, but customers of different projects have personalized needs. The system tester small A and the automatic test script developer small B are responsible for testing the OA system so as to ensure that the system functions of different versions in each project normally operate. Because the project environment is distributed in different regions nationwide, the small A has to create an independent test running environment for each region, which results in complex and tedious work of environmental maintenance. In addition, because of the functional differences between different versions, small B requires the writing of separate automated test scripts for each version, which is very labor intensive. And the small A also needs to wait for the small B to complete script development before executing the script and verifying the function, so that the construction period is long.
Through the scheme of the patent, the automatic test script developer small B only needs to maintain one set of test script, uses the basic version of the product as a base line, iterates new functions of different versions continuously, and uploads the latest test script to the test system. This approach significantly reduces the workload of small B and makes integration of new functions more efficient; for System tester, panel A, she no longer needs to wait for Panel B to complete code writing. In the version of a certain area, if the current version function is completely covered, the small A only needs to deactivate the system test cases which do not belong to the version in the test system, so that the corresponding test method in the test script is not executed any more, and the normal test of the version is not influenced. This provides greater flexibility and efficiency in testing work.
In addition, the small A can also configure the access address, user password and other information of each OA system in different areas in the test system, so that the OA systems in project environments in different areas can be tested simultaneously in the same test system. The difficulty of environmental maintenance is reduced, and the testing work is more intelligent and flexible, so that the testing work is better suitable for project requirements of different areas.
Scene II:
a business management system is developed by a boss enterprise, and is updated by continuous versions for years. And the small C is used as an automatic test script maintainer and is responsible for updating and maintaining the automatic test script along with the change of the system version. Over time, the number of functional points of the system increases gradually, the volume of the automation script also increases gradually, and the number of test functional points is close to thousands. However, in some regression verification, only a few functional points of a certain functional module in the test system are required, but the whole test script still needs to be executed, resulting in very long execution time.
Through the scheme of the patent, when carrying out regression testing, testers can selectively set the state of the functional test case to be tested as "enabled", and set the states of other functional cases as "disabled". When executing huge test scripts, the system can only execute a plurality of test methods corresponding to the starting state, thereby greatly improving the execution efficiency of the scripts. In the regression verification, even if the test script contains a large number of functional points, the test script can be selectively executed, so that the execution time is reduced, and the overall test efficiency is improved.
Scene III:
small D is a very responsible project manager who focuses on each link of the project implementation, and in particular on the quality of the product that is ultimately delivered to the customer. The small D desires to be able to obtain a test report for each automated test in order to know the latest test results in time. However, as a manager, he is not well versed in the technology and development language, and does not understand well the meaning of the script method described in the automated test report, so it is difficult to clearly understand the specific situation of the product at this time, including which functional points passed the test, and which have problems.
Through the scheme of the patent, the execution report of the test script takes the functional test case as a statistical dimension and is presented to the small D in an intuitive way. The test report shows the detailed information such as the ID of the functional test case, the name of the functional test case, the passing information of the test case, the coverage information and the like. Thus, even the project manager who only knows the business but not the technology can clearly know which of the current products passes the test on the business function points and which function points still have problems. This intuitive report form helps the small D monitor the test progress and quality of the item more easily, enabling him to push the item forward more targeted.
Finally, it is noted that the above embodiments are only for illustrating the technical solution of the present invention and not for limiting the same, and although the present invention has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications and equivalents may be made thereto without departing from the spirit and scope of the technical solution of the present invention, which is intended to be covered by the scope of the claims of the present invention.
Claims (10)
1. An agile development automation test method, characterized in that the method comprises the following steps:
step A, obtaining functional test requirements of different versions to be tested, establishing a plurality of functional test cases based on the functional test requirements of the versions to be tested, and generating a unique test case ID for each functional test case;
step B, correspondingly generating a test script for each functional test case, wherein the test script comprises a plurality of method modules, and the method modules are formed by packaging test codes corresponding to each functional test case;
step C, constructing an association relation between test script information and the ID of the test case, wherein the test script information comprises a test script name and a method module name;
step D, reading the test case ID of the functional test case in the version to be tested, acquiring the test script information associated with the read test case ID according to the read test case ID, calling the corresponding test script and executing the test module therein;
and E, storing the execution result and generating a result report of the test execution.
2. The automated testing method for agile development according to claim 1, wherein all test scripts generated in step B are saved, and a plurality of corresponding test scripts are built along with iterative updating of different versions; the test script is used for testing a plurality of functional test cases corresponding to one functional test requirement or a plurality of functional test cases corresponding to a plurality of functional test requirements.
3. The automated testing method for agile development according to claim 1, wherein in step C, the association relationship between the test script information and the test case ID is constructed: and adding the test script name and the method module name of the test case ID to the corresponding functional test case.
4. The automated testing method for agile development of claim 1, wherein in step E, after all the test scripts are executed, the test results of the execution are recorded to review the corresponding result report.
5. The automated testing method of agile development of claim 4, wherein the information of the test report comprises: error reporting information, test case pass information and coverage information.
6. An agile development automated test system, comprising:
and the use case management module is used for: the method comprises the steps of acquiring functional test requirements of different versions to be tested, establishing a plurality of functional test cases based on the functional test requirements of the versions to be tested, and generating a unique test case ID for each functional test case;
script management module: the test script is correspondingly generated for each functional test case;
an environment configuration module: the method is used for configuring required environment variables according to the test script information, and adding environment variable parameters when executing the test script;
and the test execution module is used for: the test case ID is used for reading the function test case in the version to be tested, calling the corresponding test script and executing the test module therein;
a report generation module: and the method is used for storing the execution result and generating a result report of the test execution.
7. The automated testing system of claim 6, wherein the case management module is further configured to manage an operating state of the plurality of functional test cases in the version to be tested:
acquiring historical version information, and searching for historical function test requirements and historical function test cases corresponding to the historical version;
copying the function test cases corresponding to the historical versions to generate the function test cases of the versions to be tested;
comparing the functional test requirements of the version to be tested with the functional test requirements of the historical version, and finding out the newly added, cancelled or changed functional test requirements in the version to be tested according to the comparison result;
setting an operation state to be an enabling state for a function test case corresponding to the newly-increased function test requirement; and setting the running state of the functional test case corresponding to the canceling or changing functional test requirement to be a disabled state.
8. The agile development automation test system of claim 7, wherein the test execution module further comprises: and searching a functional test case with the running state being an enabling state in the version to be tested, positioning the test script name and the method module name associated with the functional test case by reading the test case ID of the functional test case, calling the corresponding test script and executing the test module in the test script.
9. The automated testing system of claim 6, wherein the environment configuration module adds environment variable parameters for executing test scripts including access address, user name, and user password specific parameters.
10. The agile development automated testing system of claim 6, wherein the report generation module further comprises: after all the test scripts are executed, recording the test results of the execution to consult the corresponding result report.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311397667.5A CN117370196A (en) | 2023-10-25 | 2023-10-25 | Agile development automatic test method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311397667.5A CN117370196A (en) | 2023-10-25 | 2023-10-25 | Agile development automatic test method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117370196A true CN117370196A (en) | 2024-01-09 |
Family
ID=89388892
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311397667.5A Pending CN117370196A (en) | 2023-10-25 | 2023-10-25 | Agile development automatic test method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117370196A (en) |
-
2023
- 2023-10-25 CN CN202311397667.5A patent/CN117370196A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110851356B (en) | Selenium-based Web application automatic test framework and construction method and system thereof | |
| US7490319B2 (en) | Testing tool comprising an automated multidimensional traceability matrix for implementing and validating complex software systems | |
| EP0632371B1 (en) | Process for configuration management | |
| KR100513551B1 (en) | Software installation and test method and system for customized computer system | |
| US10127141B2 (en) | Electronic technology resource evaluation system | |
| US8706771B2 (en) | Systems and methods for analyzing and transforming an application from a source installation to a target installation | |
| EP2228726B1 (en) | A method and system for task modeling of mobile phone applications | |
| US9658846B2 (en) | Software configuration control wherein containers are associated with physical storage of software application versions in a software production landscape | |
| KR102237877B1 (en) | Intelligent software auto development system with real-time collaboration support and method thereof | |
| JP2001142738A (en) | Scripter and interpreter | |
| EP2417543A2 (en) | Software database system and process of building and operating the same | |
| US20060047723A1 (en) | Custom database system and method of building the same | |
| EP2196901A1 (en) | Systems and methods for tracking software stands in a software production landscape | |
| US7707211B2 (en) | Information management system and method | |
| US20100011018A1 (en) | Custom database system and method of building the same | |
| Cagnin et al. | PARFAIT: Towards a framework-based agile reengineering process | |
| CN117370196A (en) | Agile development automatic test method and system | |
| CN115344966A (en) | CAD assembly body part replacement method and system | |
| US20080022258A1 (en) | Custom database system and method of building and operating the same | |
| US8631393B2 (en) | Custom database system and method of building and operating the same | |
| WO2005089350A2 (en) | Custom database system and method of building the same | |
| CN113220592B (en) | Processing method and device for automatic test resources, server and storage medium | |
| JP3068037B2 (en) | Service management function execution method | |
| CN111259063B (en) | Method and device for realizing data export in API mode | |
| CN117687681A (en) | Version management method and system for low-code application |
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 |