1. Why do Automation
- Because now processes more agile, little point a lot of work, short cycle
- Lesser each line function, replicated many functions
- 2, in terms of quality assurance, usually only tests undertaken; no unit test code development after write
- Each new function much longer product cycles, more complex functions, more functions, each version, all functions must again point
- Mention bug, resolve bug, bug generated more than
- Each version, just change a bug, will not develop its own verification (self-test), testers need to test the full amount, verify that there is no cause other bug
- 3 this week on-line version, bug fully resolved, but the next on the line again, bug reproduce; so do quick verification automation features before release
- bug history function of demand, it is recommended
- Long cycle, multi-function
- For example: There is a historical feature, is the first version of the full amount of the test, the next version, will not be the full amount of each test point is not the same; because the whole amount has been previously tested, no problem; the next version because this version is not enough time or demand the full amount will not be tested
- Version of the long cycle, function too cumbersome, repeat
2. If your current project, what kind of turn into a regular choice of automation?
- Stability, less logic is simple, fast implementation module
- The main flow
- High repeatability
- Important functional modules, the core business
- Online high in terms of bug module
- Most users use modules, maximum functionality
3, how to allocate time if the two projects
- According to the project urgent, priority, project time and to plan
4, interface, or automated testing time allocation
- First understand the functional requirements, the need to test 1-2 weeks, automated testing familiar with the business before
- Automated test cycle is long, complex and multi-functional, regression function of history
- web automation, excessive dependence on the page, the same page, the page features stable
- such as:
- Early development was still in development when I test personnel, can not be suspected of the use cases written by the flow demand, once the connector OK first test interface, the interface OK indicates basic function is to achieve, once a page out I just need to take the process a page on the line
- That is, whether the latter can be made automatic; preparatory work is quite complicated our ability to locate BUG tester is great. So at this stage I will try to locate the BUG on specific points
5, the function would want to use automatic conversion of all cases
- Do not need
- why
- web automation functions to stabilize what to do what
- web automation does not cover so high. Some UI interface will become
- automating repetitive web test cases into automated
- web automated testing each round have to go little bit of function points - mainly regression testing
******* Please respect the original, as to reprint, please indicate the source: Reprinted from: https://www.cnblogs.com/shouhu/ , thank you! ! *******