In this talk, I will talk about test coverage. I will show experience from real project and explain why it’s important to know the magic number “42” and why we understand it wrong. As a next movement, we will look at the test to code mapping. I will show real tools and highlight ideas that will help QA engineer to succeed with their testing efforts.

1. Test coverage
SERGEY Pirogov
EPAM

2. Test coverage
Do you know whats makes you weak ?

3. Sergey Pirogov
https://t.me/automation_remarks

4. TestsRequirements

5. Traceability matrix

7. @Test
@JiraStory(id=”Jira-54”, manual = {
@Case(“Inputted password is masked by bullets”),
@Case(“Masked password can not be copied”),
})
void userCanLoginWithValidCredentials(){
open(LoginPage)
.enterUsername(“demo”)
.enterPassword(“123”)
.pressEnter()
at(MainPage).userName.shouldBe(“demo”)
}
Trying to automate

9. Coverage

12. Untested code somewhere here

13. Quality gates

14. Write tests,
love mom,
believe in pipeline

15. Included e2e tests as quality gates

17. Coverage
===
Actionable feedback

18. Test to code mapping

20. Benefits
Minimize regression testing scope
Reduce duplication of automated tests
Reduce manual tests
Collect production usage
Reverse engineer impact for tests

21. The challenge

22. Production code
==
Tested code

24. Drill4j for backend

25. Drill4Js for UI and Node

26. Agent Agent

27. Demo

28. Drill4j
drill4j.github.io
t.me/drill4j
github.com/Drill4J