At Surevine, we have Test Engineers as part of the development teams (alongside Software Engineers, of course, but also Team Leads and Infrastructure Engineers). The Test Engineers do a lot of testing, of course, but are also continuously involved in the work the Software Engineers are doing, to ensure that the code is testable and - where possible - tested properly with unit tests etc.
But we don't expect Software Engineers to test their own code - the purpose of testing is for an additional pair of eyes to find issues as well as simple QA. We do, however, expect Software Engineers to understand testing properly, in order to support the Test Engineers - and the team, as a whole, tests its own output.
This is what I came here to say. That's how my org works -- there are devs writing unit tests and test engies writing integration and end to end tests within the same team. QA begins when a feature is complete sans unit tests, so by the time it's formally "in QA" on JIRA, it's pretty much done and just needs a quick regression run of the automated tests.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
At Surevine, we have Test Engineers as part of the development teams (alongside Software Engineers, of course, but also Team Leads and Infrastructure Engineers). The Test Engineers do a lot of testing, of course, but are also continuously involved in the work the Software Engineers are doing, to ensure that the code is testable and - where possible - tested properly with unit tests etc.
But we don't expect Software Engineers to test their own code - the purpose of testing is for an additional pair of eyes to find issues as well as simple QA. We do, however, expect Software Engineers to understand testing properly, in order to support the Test Engineers - and the team, as a whole, tests its own output.
This is what I came here to say. That's how my org works -- there are devs writing unit tests and test engies writing integration and end to end tests within the same team. QA begins when a feature is complete sans unit tests, so by the time it's formally "in QA" on JIRA, it's pretty much done and just needs a quick regression run of the automated tests.