Software Developer is Test is relatively new role in IT. Industry is more used to names like QA, Test Automation Engineer, Developer.
Still that kind of role distribution shows poor effectiveness and brings such things like huge suites of end to end tests as a quality gate. If you want to implement test pyramid, you might consider such kind of a role in your team.
What skills this person should have? Which challengers and daily problems he/she faces? Can he/she make production code changes?
These and many more other questions an auditory can learn and perhaps reconsider their daily quality assuring approach.
2. Tymofii Sukhachov
10 years in industry
Both developer and QA experience
Mostly work with java and related technologies
Working at Booxware GmbH as SDET
tsuhachev@gmail.com
http://www.roboqa.net
3. â QA engineer evolution
â Separation of concerns
â Who is SDET?
4.
5. Hi, I am a QA! Who I become in 8-10 years?
Developer? Scrum Master? Business Analyst?
42. You are Software Developer in Test
â You know and understand an architecture of your system
â Test design follows Test Pyramid principle
â You work closely with developer implementing a tests
â You can implement a test at any level of a Test Pyramid
â Developer trusts and understands your tests
if
Software Developer is Test is relatively new role in IT. Industry is more used to names like QA, Test Automation Engineer, Developer ...
Still that kind of role distribution shows poor effectiveness and brings such things like huge suites of end to end tests as a quality gate. If you want to implement test pyramid, you might consider such kind of a role in your team.
What skills this person should have? Which challengers and daily problems he/she faces? Can he/she change production code?
These and many more other question an auditory can learn and perhaps reconsider their daily quality assuring approach.
Finally someone can click buttons for me!
After trying Selenium you know
Having a strong QA background you start learning ...
To some extent you can be a developer now.
There are plenty of other ways of testing rather than via UI
Do not try to do developerâs work. Help him produce a better software instead
Maybe your line is somewhere else
You can also have a pyramid with a way different layers, but whatâs important, the line has to be well defined
It also does not mean SDET cannot write Unit tests or developer cannot create API tests , it is a responsibility
Develop them together
Please learn and follow pair programming best practices
Both SDET and Developer can work together and review each other. Sometimes that can add an overhead while merging
How many tests you can think of here ? Make sure you can test the logic of a service assuming other service works well. Still you have to have a test which checks their integration.
TDD is unit test driven. Tests other than unit slows down tdd and make it ineffective . Do not try to start TDD from Integration or upper layer test