ConfPad

The cheapest way to develop is the one where the artifacts are delivered to users in ONE iteration. Without 10+ iterations of improvements due to errors found. We will talk about the shift left testing approach that is gaining popularity. Its purpose is to prevent the occurrence of errors instead of searching for mistakes already made in the software. Testing with a left shift assumes that testing and development work in tandem and as the name suggests, testing is carried forward to the earliest stages of development. - You will learn why you need to test requirements and documentation. And also consider what engineering practices help make this a part of the culture in the team. (code review, pull request, spec by example, bdd, atdd) - I'll talk about different kinds of automated tests and when to write them, in order to reduce the number of manual tests in the late stages of product development. (tdd, bdd, atdd, component and integration tests) - We will analyze how joint team activities and functional duties of each team member change to conform this methodology. (Planning, grooming, retrospective, demo, dsm, compiling a test strategy, planning testing). - I will tell why it is so important to design the test models using test-design practices, rather than relying solely on exploratory testing. We will look at the testing of control flow, cycles, data flows. I will show practical examples of why developers need to master the skills of test design. - In conclusion, I will tell about one of the ways to calculate test coverage and how it differs from code coverage. As an example, we will draw a graph of requirements and check the coverage of the test model. The entire talk will be done with the example of testing a very simple application, consisting of a single service, a database and a WEB-page. Shift left testing underlies the Agile and DevOps methodologies.