Forum Discussion
I think both nowadays. It may vary per contract. Let me explain...
Testing is primarily the task of QAs or Software Testers. The acceptance criteria for QAs before they should start the actual testing is that it already passed through Unit Tests...although I've also encountered some devs who just hand the codes over without unit tests at all.
The past 3 technologies I've handled (iOS, Android and API), I've encountered some unit tests that seems to be "automated" as well. For iOS, I've encountered some unit tests in Xcode that seem to be automated (according to the dev these are unit tests that are written in Objective-C and some were in Swift) which they also asked us to run due to time constraints. For the API, I've seen some tests written in a language similar to Gherkin (BDD) which they call Spock tests being ran by dev. Any devs our there to confirm? :smileywink:
While both QA and Devs may create tests that appear to be using Automation technology, as I mentioned earlier, the official standard is that QAs have their own set of Automation tests (if applicable, since some project parts may not be worth automating). It should be different from developer's tests. This way, we will be able to filter issues that might have escaped dev's eyes. At the end of the day, it's not really dev vs. QA but what matters is that we deliver software with the least number of bugs that can be seen by the end user. I used to have a manager who said, "There's no such thing as a 100% bug free software".
I agree with some of the replies to your question. Automation testers are in the middle of a dev and manual testers. While we are not really developers, we need to have some coding skills to make the tests and an end user's mentality in mind (for UATs). I'd say, the best of both worlds :smileyhappy:
Related Content
- 7 months agomengbinhao
- 5 years agoMr-Shlomi
- 3 years agombeckham
- 4 years agoJosh_147
Recent Discussions
- 6 hours agoSvetaG