РОМАН ШАЙДА "How to build your own Testing Strategy"

1. How to build your own
Testing Strategy

3. http://qaschool.com.ua

4. - snowboarder
- music lover
- traveller
- gamer
- and a lot more)

6. Or no? :)

7. Life in Norway: “There's no such thing as bad
weather, only bad clothes”

8. Build your strategy!
But how?

9. What to start with?

10. Correct!

11. Let’s start from
high-level overview:

12. Let’s start from
high-level overview:

13. Let’s start from
high-level overview:

14. Let’s start from
high-level overview:

15. Let’s start from
high-level overview:

16. Let’s start from
high-level overview:

17. What else do we need?

18. Correct!

19. Test plan should be design
based on the following criterias:
1.
2.
3.
4.
5.
6.
7.
8.

20. Test plan should be design
based on the following criterias:
1. Project Roadmap
2.
3.
4.
5.
6.
7.
8.

21. Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3.
4.
5.
6.
7.
8.

22. Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4.
5.
6.
7.
8.

23. Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4. Most commonly used environments
5.
6.
7.
8.

24. Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4. Most commonly used environments
5. Application / site analytics
6.
7.
8.

25. Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4. Most commonly used environments
5. Application / site analytics
6. Risk Analysis
7.
8.

26. Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4. Most commonly used environments
5. Application / site analytics
6. Risk Analysis
7. Definition of testing types
8.

27. Test plan should be design
based on the following criterias:
1. Project Roadmap
2. Resource Planning / Budget
3. Acceptance Criteria
4. Most commonly used environments
5. Application / site analytics
6. Risk Analysis
7. Definition of testing types
8. Test Plan diagram

28. Discuss

29. 1. Project roadmap

30. 1. Project roadmap

31. 2. Resource Planning / Budget
(manual testing / automated testing)

32. 2. Resource Planning / Budget
(manual testing / automated testing)

33. 3. Gherkin DSL = Acceptance Criteria

34. 3. Gherkin DSL = Acceptance Criteria
Wait, what?

35. 3. Gherkin DSL = Acceptance Criteria

36. 3. Gherkin DSL = Acceptance Criteria
(UX prototypes is a good plus)

37. 4. Most commonly used environments
(OS/Browsers/Mobile devices)

38. 4. Most commonly used environments
(OS/Browsers/Mobile devices)

39. 5. Application / site analytics

40. 5. Application / site analytics

41. 6. Risk Analysis

42. 6. Risk Analysis

43. 7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:

44. 7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:
● Unit Testing

45. 7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:
● Unit Testing
● Integration Testing

46. 7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:
● Unit Testing
● Integration Testing
● Functional Testing

47. 7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:
● Unit Testing
● Integration Testing
● Functional Testing
● ...

48. 7. Definition of testing types
Types of testing should be defined based on project-specific
resources/budget/roadmap/AC/environment analysis:
● Unit Testing
● Integration Testing
● Functional Testing
● ...
● Black/White Box Testing
● Stress Testing
● Performance Testing
● Usability Testing
● Acceptance Testing
● Regression Testing
● Beta Testing
● ...

49. 8. Test plan diagram

50. 8. Test plan diagram

51. 8. Test plan diagram

52. 8. Test plan diagram

53. 8. Test plan diagram

54. 8. Test plan diagram

55. Okay…Now we are ready to create a Test
Strategy!

56. What is the Test Strategy?
Test Strategy is the document which describes
how to deal with the Test Plan

57. What is the Test Strategy?
Test Strategy is the document which describes
how to deal with the Test Plan
© на хлопський розум

58. Based on the “preparation phase” and Test Plan
design we can build our Testing Strategy!

59. Main Components of a Test Strategy are:

60. Main Components of a Test Strategy are:
1. Test Suites/Sets creation

61. Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions

62. Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes

63. Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes
4. Meetings

64. Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes
4. Meetings
5. Tasks lifecycle

65. Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes
4. Meetings
5. Tasks lifecycle
6. Defects update and submission

66. Main Components of a Test Strategy are:
1. Test Suites/Sets creation
2. Test Executions
3. Processes
4. Meetings
5. Tasks lifecycle
6. Defects update and submission
7. CI processes

67. Discuss

68. 1. Test Suites/Sets creation

69. 1. Test Suites/Sets creation

70. 2. Test Executions

71. 2. Test Executions

72. 2. Test Executions

73. 3. Processes

74. 3. Processes

75. 3. Processes

76. 3. Processes

77. 4. Meetings

78. 4. Meetings

79. 4. Meetings
- - Stand-Up Meeting (15 minutes, Every Day)
- - Grooming (Refinement Session, 0.5 to 1 hours, 1-2 Times per Week)
- - Sprint Review Meeting at the End of the Sprint (2-4 Hours)
- - Sprint Planning (2-4 Hours)
- - Retrospective Meeting at the End of the Sprint (1 Hour)

80. 5. Tasks lifecycle

81. 5. Tasks lifecycle
- Levels:
Epic -> Story -> Task/Bug/Feature/Sub task

82. 5. Tasks lifecycle
- Levels:
Epic -> Story -> Task/Bug/Feature/Sub task
- - Dev team Steps - QA team Steps - DevOps Steps

83. 6. Defects update and submission

84. 6. Defects update and submission

85. 6. Defects update and submission
- Description:
- - Environment: test/stage/prod
- - Country(optional)
- - Language(optional)
- - Browser/Device: chrome/firefox/ie/mobile device
- - Browser/Device version: chrome/firefox/ie/mobile device versions
- - Build version: Build version
- Steps to reproduce:
- should contain detailed steps how to reproduce the bug
- Actual result: -//-
- Expected result: -//-
- Notes:(optional)

86. 7. CI processes

87. 7. CI processes

88. 7. CI processes
JIRA fields:
- Affects Version/s:
- Fix Version/s:
Example:
It should return the branch, date, release number and environment info:
BRANCH:
Development
RELEASE:
SPRINT-1
Date of latest build:
DATE:
Wed May 9 10:46:45 CEST 2018

89. Great Success! :)

90. Q/A ?
Contact:
dimencionr@gmail.com
https://www.facebook.com/roman.shayda
https://linkedin.com/in/romanshayda/
https://www.youtube.com/user/dimencionrider
https://github.com/dimencionrider