Software Developer in Test. Who's that?
•Descargar como PPTX, PDF•
1 recomendación•1,581 vistas
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.
Recomendados
Recomendados
Más contenido relacionado
Último
Último (20)
Destacado
Destacado (20)
Software Developer in Test. Who's that?
- 1. Software Developer in Test Who's that?
- 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?
- 5. Hi, I am a QA! Who I become in 8-10 years? Developer? Scrum Master? Business Analyst?
- 6. There has always been a wall
- 7. Bringing QA inside a team has not removed it
- 8. Once requirements are clear ...
- 13. 5th sprint ... I heard Selenium is great Do it
- 14. Why Selenium is popular?
- 16. 11th sprint ... Rely on our tests! They are … not stable Why??!!
- 17. 40 % of tests are now outdated We have to test them manually again
- 19. This is moment Selenium stops being popular
- 21. Test automation is like a drugs good habit
- 23. An application is not a black box anymore
- 24. User Interface is not the only API
- 25. And Selenium is not the only way of testing :)
- 26. Tests can use the closest Interface
- 27. Test Pyramid follows that principle
- 29. You are not a developer!
- 30. Think twice before changing production code
- 32. Do you want others trust on your tests?
- 33. Get involved into pair programming
- 34. Keep test and production code in one branch
- 35. Review pull requests Try to understand the code and especially tests Do not hesitate adding your comments to code Code never lies
- 38. { "balance":94, "currency":"EUR" } Wallet Service Currency Service 94 EUR Retrieve my balance /getRate
- 39. Does TDD work with SDET involved?
- 40. Short Iteration
- 41. So who is SDET?
- 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
- 43. SDET vs Automation QA
- 44. SDET Profile 5+ years as QA 2+ java experience: Java Core, Collections, etc ... Http, Rest/Soap, json, xml, html, css selectors, xpath JUnit, Mockito, Wiremock, Hamcrest, AssertJ SQL (most used queries: join, having, in etc ...) Very preferable: Spring, Tomcat, Hibernate Continuous Integration
Notas del editor
- 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