When it comes to acceptable test automation, the most important step is to have a proper framework for test automation team in place. This article has some projects have proven automated testing for a number of different application scenarios - or automated regression led by a team, with agile adaptability - helps organizations enjoy long-term success of test automation.
The company launched a new test automation initiative - any sales related to design marketing tool - a tendency to think that their success depends on a perfect line. As a test automation consultant, I like to provide a real basis of what I saw in the field of inspection. If you are not ready, the first on-line may be rough and rugged road, but in the long run, but it was not to destroy your manufacturing test automation initiatives.
Recently I saw some of the companies do not appear ready to start test automation. The execution risk "strategy" is to test who might want to insist on test automation for these reasons:
- They do not think it lives very well
- They do not want (or no time) to learn new tools
- They worry that it's too complicated and it needs to keep up with the progress of efforts to exceed the perceived benefits
An inadequate plan - planned or not - on the line is clearly not the best of the best way to initiate a test automation initiative. Anyway, I found recovery than those without a proper test automation retreat team structure away from the achieve sustained robust test automation generally easier on the line.
I like to go for a number of different test scenarios using automation to share some of the practices proven to help a lot of organizations enjoy long-term success - even when the initial on-line is not ideal.
Automation one by one project team is brought on line our test automation
The best piece of advice I can offer is to start from the little things, then bigger. The first practice has proved that begins with the creation automation team.
The team from different iterations of the project and start from the most important test automation. This allows you to demonstrate progress in the initiative and let you see some of the changes affect the application of the main application functionality.
I suggest that the most influential test case from the beginning: those covering your top business risks. This creates a strong return to the establishment of a folder, it provides the fastest application whether changes are working to undermine the feedback function.
Automation team should include at least one test design expert, he reviews the demand and use of test case design should be to develop automated test cases. Then, test design automation expert or two or three experts who can assess the need for test data management, then they can work to specify test cases. At the same time, test design experts will focus on the next item.
Depending on the software you want to test and how much you customize it, an automation engineer is necessary. They will ensure that conventional control is created and maintained.
With the expansion of the size of the team will, depending on the number of test cases and the team handled the project. These recommendations only to the initial on-line. Once on the line to begin, you will want to start recruiting as many people.
Once test cases are automated, they can run all night on the virtual machine, and then report the results on a daily basis. To test automation The most important thing is to join the operation in the implementation of test cases indeed! If you are not being performed by your use cases, you will not get any value from them, whether you test how well the design and how well it covers your main business risks.
Depending on your company structure (agile or not, or an independent test team members who test), mainly in the automation team may teach everyone about the implementation of automated on-line best practices and when they start their own test automation needs to be considered project-based diversity.
Before the test began using test automation, you must make a decision: Who is responsible for these test cases? This is the main. If the automation team (or later return to the team) is responsible, then they have to do more to communicate with testers who and business aspects. If it is the tester's responsibility, they need enough time to ensure that all test cases in the execution and in line with business needs. Each organization needs to decide what is best for them, depending on their structure and mode of operation.
No matter which direction you are responsible for ensuring save enough time to communicate. On the one hand, new test cases need to be created and then return to the audit team to perform. On the other hand, regression test results (especially the failed test case) needs to be shared so that team members are responsible for or testers can review them and update the test if necessary. At least, ensure that the testers were independently checked the results of the regression and make appropriate adjustments, so the team return from a shared folder to launch a new test case, they own review.
Return team leadership and guidance testers are on each item
I have seen the most efficient setting is the establishment of an initial automation team, which includes a return to the team once the test automation foundation was set up, the other must be prepared to drive it forward.
Return to the team responsible for creating test cases are still in the initial years of the project is to maintain existing test cases, execute test cases, test infrastructure protection, and to establish and supervise test automation project widened. You can take this excellent team called the testing center.
About this build, there may be more changes in the project and directed by the test design expert, he was concerned the right format and provides a preview of what it should look like. They are like software, artists (or in our case, test the artist).
Return to the team is the "anchor group", if you have a question about a problem or you want to introduce new and innovative. It should be the responsibility of the owner and should return to the team, because they have the best overview of the test folder.
From the perspective of a resource, you need a highly skilled team of people in return, but you can be lucky enough to escape with little experience as a tester team members. If the testers need more knowledge than the training provided, they can always ask the return team, then they can share their knowledge built up to help.
Agility to adapt to the environment
For agile teams, driven test automation team of agile testers. This person should be more advanced than an automation expert - they need to understand the test case design, requirements, creation and execution of test cases, and test core best practices, and what they need to test and how to test it's good to understand.
I would suggest a continued development and testing of the establishment from one to another Sprint Sprint:
When the development is over n-1 characteristic Sprint, the test begins. Meanwhile, the development of sustained characteristic 2 (Sprint n), and the like. Just make sure to fix the bug and deeper improve retention time.
We separate development and test it?
Finally, when it comes to architecture, I want to a pair of problems occur frequently increase my two cents: our developers need to test it, or we need to separate development and test it? We use software development engineer in test (referred to as SDETs) do?
In theory, you can also have developed tests to save time and money because most developers know the code. But tell the truth: the development never enough time to complete the development tasks for each person you want to accomplish. If they are also responsible for test automation, that means they do not even have time to complete those tasks. And even if most developers who know the code, you can check them to determine the boundary conditions do? Expected risk and try to ask the right questions? Explore the system and bring it to fail?
My opinion is that some people do not write code more suitable for this. Others who focus on acquiring real business goals through the application and try every possibility of a guidance system can guide a wrong thinking. From the area I had seen, it is usually not a development strengths.
Rotary tables
All of these recommendations are based on my test automation to help users adapt to personal experience. I know that every reader may have different views on this - and I encourage you to share the following thoughts about it. What helped you the most? How can you build test automation in your company? What are the challenges you are faced with?