Forum Discussion
There's a lot of variability in the market out there. A lot of it depends, somewhat, on your strategy for automated testing.
If you're doing primarily a record/playback structure with each test case being constructed as either a keyword test or a script test, then most likely you'll find your testers doing most of the automation work. You might find a tester or two who can write some code who can modularize some of the common code into functions/tests that can be called repeatedly.
If, however, you're going with a more advanced framework structure with tests being driven by data content and test cases not being individual keyword tests or script functions but more dynamically constructed at runtime based upon the data, then I think you'll find that there is a developer skill needed.
I would say that, usually, the developer developing the test framework is not a developer who is developing the AUT. That actually would be a bad idea to have the application developer developing the framework... it's for the same reason as you don't let developers test their own code... too close to the product.
What I've implemented and seen implemented in several companies is that the work is divided. Developing the framework and maintaining the code is relegated to one particular group of folks who have skills in both development and in automated testing. Building the test cases within that framework then goes to actual testers and QA staff.
Now, if you're generally calling things from a "top level" structure... automated regression and functional tests is QA... automated unit testing is Development.
Related Content
- 7 months agomengbinhao
- 5 years agoMr-Shlomi
- 3 years agombeckham
- 4 years agoJosh_147
Recent Discussions
- 52 minutes agoSvetaG