(1) no frame stage (simple recording/playback)
in the early stage, there was no frame for automated testing, automated Testing is just a simple recording/playback process. It is used to record and record the operation process or data and form a script. Repeat the manual operation process through script playback. This mode combines scripts with data. From the perspective of software development, we know that the idea of software engineering is high cohesion and low coupling. Simple recording playback completely violates this idea. Simple recording playback features low reusability and high maintenance costs.
(2) data-driven framework phase
the biggest drawback of the no-framework phase is that scripts are mixed with data. To solve this problem, the automated testing framework has developed to the data drive framework stage. This framework reads data from the data file and writes the data read from the data file to the script through parameterization (for example, reading data from the database ), because different data correspond to different test cases, scripts are completely separated from data, which increases the script usage and greatly reduces the script maintenance cost. Although the data-driven framework solves the problem of scripts and data, the tested objects and operations are not separated.
(3) keyword-driven framework stage
the keyword-driven framework is an improved framework model based on the data-driven framework. It breaks down the test logic by keywords and forms the business logic encapsulated by the data file and keywords. The main keywords include three types: tested object (item), Operation (operation), and value (value ). It is represented as item. Operation (value) in the object-oriented form ). The main idea driven by keywords is: separation of scripts and data, separation of interface element names and internal test object names, and separation of test description and implementation details
(4) the hybrid model framework phase
keyword-driven framework brings the automated testing framework into a new phase, and the Automated Testing Tool quicktest also uses this concept well, however, in actual automated testing, it is found that the keyword-driven framework brought by the testing tool still cannot complete the Testing task well. Although the framework separates the data from the script, the framework cannot do this if you want to more flexibly call the data in the test case or output the test results; and it cannot be well solved if you want to read data from other file storage formats. Therefore, in the early stage of automated testing, engineers will develop a framework that conforms to the actual test to support subsequent testing. This is generally referred to as the hybrid model automated testing framework.