This document discusses software testing techniques and best practices. It covers test design techniques like equivalence partitioning and boundary value analysis. It emphasizes the importance of tests being fast, isolated, repeatable, self-validating, and thorough. The testing pyramid hierarchy of tests is explained. Test-driven development and various test utilities are also outlined. The conclusions emphasize that tests help increase confidence in code, prevent accidental breaks, and ensure documentation remains relevant.

1. Ducks Don’t Like Bugs
Ivan Dryzhyruk

2. 2www.luxoft.com
Team: 6 people
QA: what you need
Bugs: a few
Who Are We?

3. 3www.luxoft.com
Agenda
Tests and Testing. What Are They?
Test Design Techniques
The Testing Pyramid
F.I.R.S.T.
Best Practices
TDD
Tools
Conclusions

4. 4www.luxoft.com
What is Testing?
Software Testing –
checking the correspondence
between real and expected
behavior of the program, all carried
out via a finite set of tests.

5. 5www.luxoft.com
Goals of Testing
1. Increase the likelihood that an application designed for
testing will work correctly under any circumstance.
2. Increase the likelihood that the application designed for
testing will meet all the described requirements.
3. Provide current information on the status of the product.

6. 6www.luxoft.com
Test Design Techniques
- Equivalence Partitioning
- Boundary Value Analysis
- Cause/Effect
- Domain Analysis Testing
- Error Guessing
- Decision Tables
- Cause-Effect Graph
- State Transition Testing
- Use Case Testing
- Pairwise Testing

7. 7www.luxoft.com
Successful Scenario

8. 8www.luxoft.com
Equivalence Partitioning

9. 9www.luxoft.com
Boundary Value Analysis

10. 10www.luxoft.com
Cause / Effect
Cause:
Initiation action
Effect:
What happens as a result of the cause

11. 11www.luxoft.com
Error Guessing

12. 12www.luxoft.com
The Testing Pyramid

13. 13www.luxoft.com
F.I.R.S.T.
- Fast
- Isolated / Independent
- Repeatable
- Self-validating
- Thorough / Timely

14. 14www.luxoft.com
Fast
- Slow tests will not be run.
- The spread of tests running = the time to find bugs.
- The relevance of the test result can expire.

15. 15www.luxoft.com
Isolated / Independent
- The order of tests is not specifically defined.
- Tests should not depend on the results of other tests.

16. 16www.luxoft.com
Repeatable
- Test should produce one result each time
they are run.
- A zero-tolerance policy for failing tests. If
your team is ignoring test results, then why
have tests at all?

17. 17www.luxoft.com
Self-validating
- Verify if the test is right or not.
- The result of the test should be an obvious pass
or fail.

18. 18www.luxoft.com
Thorough / Timely
- Write the test before implementation.
- The worst scenario is writing tests by code
result.
- The execution of tests should not take long.

19. 19www.luxoft.com
Given-When-Then
public void shouldReturnPreviouseTraidingDay() {
//given
LocalDate atraidingDayctual = LocalDate.of(30,3,2020)
LocalDate expected = = LocalDate.of(27,3,2020)
//when
LocalDate actual = new EodService()
.calculatePreviouseTraidingDay(traidingDay);
//then
assertEquals(expected, actual);
}
Presented Daniel Terhorst-North and Chris Matts as part of
Behavior-Driven Development (BDD)

20. 20www.luxoft.com
Don’ts:
- no condition logic
- no loops
- no exception catching
- no calculation of in / out values
- no sources as destination objects
- no dependency on random values
- no dependency on the current date

21. 21www.luxoft.com
No Influence on Product Code

22. 22www.luxoft.com
Tests are Code
- Write unit tests as you write your
application code
- Every bug you fix should have a
test that verifies the bug is fixed
- Naming it is the hardest task
Test: is it REAL code?

23. 23www.luxoft.com
Tests are Documentation
- Tests show how to use your
module or application
- Tests stay intertwined with code
and do not age out

24. 24www.luxoft.com
TDD

25. 25www.luxoft.com
Test Utilities
- Mockito
- AssertJ
- Awaitility
- Code coverage utilities
- Sonar
- REST-assured
- JBehave
- Serenity

26. 26www.luxoft.com
Mockito

27. 27www.luxoft.com
AssertJ

28. 28www.luxoft.com
Awaitility

29. 29www.luxoft.com
Code Coverage Utilities

30. 30www.luxoft.com
Sonar

31. 31www.luxoft.com
REST-assured

32. 32www.luxoft.com
JBehave

33. 33www.luxoft.com
Serenity

34. 34www.luxoft.com
Conclusions
Tests will help you:
1. Be more confident in your code.
2. Be sure that no one will break your code accidentally.
3. Ensure documentation relevance.

35. Thank You!