Automation version verifying method and system based on B/S structural system

Abstract

The invention discloses an automation version verifying method and system based on a B/S structural system. The method comprises the following steps: (1) obtaining newest codes from a configuration management tool according to configuration files to generate a new testing edition; (2) building a testing environment according to the preset configuration files, and installing, configuring and starting a system to be tested; (3) backing up basic data according to the configuration files, and emptying existing testing data to enable the system to be in an initialized state as the state submitted to a client; (4) automatically guiding in a test case which needs to be executed in version verification according to the configuration files; (5) selecting to execute the test case performed with version verification according to the configuration files; and (6) generating a test report according to version verification results. The automation version verifying method and system based on the B/S structural system comprises a version generation module, a core control module, a testing environment building module, a data processing module, a version verification case lead-in module, a version verification executing module and a testing report module.

Description

technical field [0001] The invention relates to the field of computer software, in particular to an automatic version verification method and system based on a B / S structure system. Background technique [0002] Independent software testing has to go through many rounds of testing from the beginning of the test to the end of the test, that is, to release many test versions. In addition, some serious problems may be encountered during the test, causing all tests to be interrupted, and then the problems have to be fixed. Re-release the version (this happens more often in systems with B / S structure), and for incrementally developed software systems, more test versions need to be released. In a company with this model of testing as an independent department (the testing group is a testing center responsible for the testing of all projects in the company), according to the strict testing process, each version released by the development team to the testing department for testing ...

AI Technical Summary

Problems solved by technology

[0005] (1) Slow version generation: Since manual versioning requires all code packages to be put together, a large-scale system is often jointly developed and integrated by multiple project teams. This requires the cooperation of multiple groups to complete the work of version generation. It takes more time and involves more people;

[0006] (2) Changing more configuration files is prone to errors: the manual version generation method relies too much on operators, and there may be missing changes due to too many configuration files that need to be changed. Such a direct result will lead to version release fail;

[0007] (3) Waste of resources: Because the version verification is mainly for the verification of the core functions and the main process of the system, this kind of verification can only be done serially but not in parallel, which takes up a lot of working time;

[0008] (4) Frequent version releases require a lot of repetitive work: in the early stage of testing, due to system instability and many functional defects, frequent version releases may be required during the test process, and the entire process of version generation and verification needs to be repeated for each version release. time consuming

Images