1. Three cornerstones to ensure successful automation testing
To ensure the success of the automation testing of software projects, if there are three aspects can be done well, then the success of the project is automated test success is within reach. So, what are they? They are data, automation, and tools, respectively. Here we discuss them separately.
Data: The effectiveness of test data is critical to validating increasingly complex software functions, and the efficiency of automated testing can be ensured if the test data is repeatable. So for the data, we require it to be customizable, recoverable, and reusable. If the above content can be automated, then the data section should be more fully prepared. Typically, our manual test data is mixed with automated test data and is usually affected by each other. Especially if your software project has many release times, every time you work with an automated test script for a previous project you will find that the data is almost unusable, and we almost need to duplicate the data for each script, which is costly and the efficiency of the automated test is not apparent. Of course there are many different solutions to this situation, and my advice is that the data in the Automated Test section can exist independently. Of course, you have to ensure that its effectiveness, here do not do a specific discussion, you can try to think more exchange solutions.
Automation: With regard to automation, we mainly talk about automated testing, that is, our user needs can be translated into automated test scripts that test software to ensure that the functionality and business processes of the software are not compromised after it has been transformed and refactored. For automated testing, we want to be able to have a high level of automated test coverage to get a lot of time costs. We also want fewer scripts to maintain. So in the context of automated test scripts, we should consider, build, and maintain it from the perspective of software development. Instead of simply turning a manual test case into an automated test. If you simply turn manual test cases into automated test cases, we will spend a lot of time maintaining test scripts, testing object libraries, and so on. Of course, we mention automation here, and we also mean that other aspects of software engineering are also being automated, not just automated testing. If most or most of our projects can be automated, our productivity will be improved. For example, if we can have automated test scripts, then our automated test execution should be automatically invoked, and the final test results and metrics should be automatically acquired. In simple terms, everything should be automated.
......
2. Automated test productivity
Recently, one of the interesting questions asked by colleagues is automated test productivity. What is our automated test capacity, and how do we know whether our annual automated test productivity has increased or decreased? In response to this question, I think this is actually a requirement for us to have data metrics to measure an enterprise or team's automated testing capabilities. As for the definition of this indicator, I believe that each enterprise must have its own standards. But I think the data acquisition should be similar, that is to say, those involved in the operation of the data should be not too much. Before mentioning these data I would like to talk about the test of the ability of manual testing methods, usually people will write how many test cases each year, how many tests carried out, how many passed, there are invalid defect how many and so on these data to consider. For automation, we will also consider the relevant data, such as our automated test coverage, how many times our scripts are run, how many times we save, how much time I have to maintain the script, and so on, with these basic data, we can customize our own automated test productivity model, Complete the measurement of automated testing capabilities of your own business or team.
3. Automated Testing Framework
About the automated testing framework, this is actually a very interesting phenomenon. Why, because we will find that most automated test teams will implement an automated test framework and then be promoted as a standard or specification within the team. And once we have the automated test framework, we'll find that our automated test script development is more efficient and much more regulated. This is a good thing, but here's what I want to say, don't overdo it, the framework of automated testing is to follow the principle of reuse as much as possible. Do not engage in a similar keyword framework that I have implemented before, and I think all the so-called keyword testing frameworks are extremely inefficient, and maintenance costs are extremely high.
......
See the full text please click to download: http://www.51testing.com/html/98/n-1298298.html
This article is included in the "51 Test World" electronic magazine, phase 36th.
Copyright NOTICE: This article is from 51Testing Software test network Electronic magazine-"51 Test World" 36th. 51Testing Software test Network and related content providers have all the copyrights of 51testing.com content, without express written permission, no one or unit shall copy, reprint or mirror the contents of this website, otherwise it will be held liable.
