What you need to automate?
Asking, "What to automate?", You must first answer the question: "Is it appropriate to test automation in a project." If the answer is "yes", it must be based on the requirements for testing an object, create a plan that will develop automated tests. By creating such a document, you need to be clear, "that automate?" "How to automate?" and "What to automate?". We will not go into details of how and what to test a particular feature, simply list the places where, in our view, need to apply automation:
- Difficult places in the system (backend processes, logging file, the record in the database)
- A commonly used functionality, the risks of errors which are quite high. Automating the verification of critical functionality that can ensure the rapid location of errors, and hence their rapid solution.
- Routine operations, such as Perebory data (forms with many input fields. Automate filling of fields of various data and test them after saving)
- Validation messages (automated filling of fields is not correct data and check the appearance of a validation)
- Long end-to-end scenario
- Checking data, requiring precise mathematical calculations
- Validation data search
And also, much more, depending on the requirements for the system under test and the opportunity to choose an instrument for testing.
For more efficient use of test automation is better to develop some test cases are checked:
- Basic operations to create / read / update / delete entities (so-called CRUD operations – Create / Read / Update / Delete).
Example: create, delete, view and change user data.
- Typical scenarios for using the application, or individual actions.
Example: The user visits a site mail, browses the letter, looks new, writes and sends a letter out from the site. This so-called end-to-end scenario, which tests a set of actions. We suggest you use just such scenarios, since they allow to return the system to a state as close to the original, so – minimally affecting the other tests.
- Interfaces that work with files and other times, inconvenient for manual testing.
Example: The system creates a xml file, whose structure should be checked.
This is the functionality of automated testing that can get the best value.
See Also