not finding them! • Have visibility and directive to push code out when it is working, and roll it back when it is not. • Become responsible for continuous improvement and help to assure quality across the development cycle. The QA Evolution (1/2 )
from the first line of code and work your way up in the testing pyramid ◦ Continuously integrate, deliver and deploy working software ◦ Get early feedback and keep quality high at all times How should we do that?
Their goal is to accelerate deployment, rather than hold it back • Releasing new and functional builds at any point through the SDLC can become a disaster if quality is not ensured constantly • Knowing which tests to automate is critical to guarantee quality and bring speed Do organizations really need QAs?
Share constant feedback on what actually is going on • Communicate on how the code relates back to a requirement or user story • Share feedback on which tests should be automated and which are actually affecting the feature that’s being released
should be on covering critical scenarios ◦ Have a solid base of unit and functional tests, and anything automatable • Regression tests have to be built incrementally ◦ When making a bug fix, add a test for that bug • Manual testing should only be used for exploration