Agile Testing Course based on the ISTQB Agile Tester Syllabus

This course structure follows the ISTQB Agile syllabus, preparing participants to sit for the ISTQB Agile Tester Certification and enabling them to practice Agile testing in real-world scenarios.

1. ISTQB – Agile Tester https://arshadqa.com

2. Objectives https://arshadqa.com

3. Why Agile?

4. Benefits of Agile 1. Maintains interest of stakeholders 2. Productivity of team 3. Speed-to-market is significantly increased 4. Quality of the product is remarkable high 5. Fun part of Agile https://arshadqa.com

5. https://arshadqa.com

6. ISTQB Agile Tester exam preparation https://arshadqa.com

7. ISTQB Foundation New Syllabus https://arshadqa.com

8. Introduction To ISTQB https://arshadqa.com

9. https://arshadqa.com

10. Introduction To ISTQB About Examination: Prerequisite Exam type – Objective Number of Questions Duration Schedule Location/Venue Passing Score Additional Info https://arshadqa.com

11. ISTQB Agile Tester Syllabus https://arshadqa.com

12. ISTQB Agile Tester exam preparation https://arshadqa.com

13. 1. Agile Software Development https://arshadqa.com

14. 1.1 The Fundamentals of Agile Software Development https://arshadqa.com

15. Waterfall Model

16. 1.1.1 Agile Software Development and the Agile Manifesto

17. 1.1.1 Agile Software Development and the Agile Manifesto https://arshadqa.com

18. Individual and Interactions Over processes and tools

19. Working Software over comprehensive documents

20. Customer collaboration over contract negotiation

21. Responding to Change over following a plan

22. Agile Principles

23. 12 Principles https://arshadqa.com

24. 1.1.2 Whole-Team Approach

25. https://arshadqa.com

26. 1.1.3 Early and Frequent Feedback

27. https://arshadqa.com

28. 1.2 Aspects of Agile Approaches https://arshadqa.com

29. 1.2.1 Agile Software Development Approaches

30. Scrum

31. Sprint Burn Down Chart https://arshadqa.com

32. XP https://arshadqa.com

33. Kanban

34. 1.2.2 Collaborative User Story Creation

35. https://arshadqa.com

36. 1.2.3 Retrospectives https://arshadqa.com

37. https://arshadqa.com

38. 1.2.4 Continuous Integration

39. https://arshadqa.com

40. https://arshadqa.com

41. 1.2.5 Release and Iteration Planning https://arshadqa.com

42. https://arshadqa.com

43. 2. Fundamental Agile Testing Principles, Practices, and Processes https://arshadqa.com

44. 2.1 The Differences between Testing in Traditional and Agile Approaches

45. 2.1 The Differences between Testing in Traditional and Agile Approaches

46. 2.1.1 Testing and Development Activities

47. Agile Testing

48. 2.1.2 Project Work Products https://arshadqa.com

49. 2.1.2 Project Work Products https://arshadqa.com

50. 2.1.3 Test Levels https://arshadqa.com

51. 2.1.4 Testing and Configuration Management https://arshadqa.com

52. 2.1.4 Testing and Configuration Management

53. 2.1.5 Organizational Options for Independent Testing https://arshadqa.com

54. 2.1.5 Organizational Options for Independent Testing

55. 2.2 Status of Testing in Agile Projects Change takes place rapidly in Agile projects. This change means that test status, test progress, and product quality constantly evolve, and testers must devise ways to get that information to the team so that they can make decisions to stay on track for successful completion of each iteration https://arshadqa.com

56. 2.2.1 Communicating Test Status, Progress, and Product Quality There are lot of simple tools and techniques in place by which agile teams can monitor the status of iteration. Different tools and techniques available for Agile teams to record their status are: Daily standup, it is a daily planning meeting; this meeting is not be exactly meant to update daily status Various soft dashboards. Sprint Burndown charts. Big visible task boards at the team location. Wiki portal where everyone can update the daily progress. Lastly, emails in simple language that everyone can understand

57. Daily Standup Meeting https://arshadqa.com

58. https://arshadqa.com

59. 2.2.2 Managing Regression Risk with Evolving Manual and Automated Test Cases

60. 2.2.2 Managing Regression Risk with Evolving Manual and Automated Test Cases

61. 2.3 Role and Skills of a Tester in an Agile Team https://arshadqa.com

62. 2.3.1 Agile Tester Skills https://arshadqa.com

63. 2.3.2 The Role of a Tester in an Agile Team https://arshadqa.com

64. 3. Agile Testing Methods, Techniques, and Tools

65. 3.1 Agile Testing Methods

66. 3.1.1 Test-Driven, Acceptance Test-Driven and Behavior-Driven Development

67. Test-Driven Development The process for test-driven development is: Add a test that captures the programmer’s concept of the desired functioning of a small piece of code Run the test, which should fail since the code doesn’t exist Write the code and run the test in a tight loop until the test passes Refactor the code after the test is passed, re-running the test to ensure it continues to pass against the refactored code Repeat this process for the next small piece of code, running the previous tests as well as the added tests

68. Acceptance Test-Driven

69. Benefits of BDD:

70. 3.1.2 The Test Pyramid https://arshadqa.com

71. 3.1.3 Testing Quadrants, Test Levels, and Testing Types

72. 3.1.4 The Role of a Tester

73. https://arshadqa.com

74. 3.2 Assessing Quality Risks and Estimating Test Effort A typical objective of testing in all projects, Agile or traditional, is to reduce the risk of product quality problems to an acceptable level prior to release. Testers in Agile projects can use the same types of techniques used in traditional projects to identify quality risks (or product risks), assess the associated level of risk, estimate the effort required to reduce those risks sufficiently, and then mitigate those risks through test design, implementation, and execution. However, given the short iterations and rate of change in Agile projects, some adaptations of those techniques are required

75. 3.2.1 Assessing Quality Risks in Agile Projects

76. 3.2.2 Estimating Testing Effort Based on Content and Risk During release planning, the Agile team estimates the effort required to complete the release. The estimate addresses the testing effort as well. A common estimation technique used in Agile projects is planning poker, a consensus-based technique.

77. Poker Planning https://arshadqa.com

78. 3.3 Techniques in Agile Projects Many of the test techniques and testing levels that apply to traditional projects can also be applied to Agile projects. However, for Agile projects, there are some specific considerations and variances in test techniques, terminologies, and documentation that should be considered

79. 3.3.1 Acceptance Criteria, Adequate Coverage, and Other Information for Testing

80. 3.3.2 Applying Acceptance Test-Driven Development https://arshadqa.com

81. 3.3.3 Functional and Non-Functional Black Box Test Design

82. 3.3.4 Exploratory Testing and Agile Testing

83. 3.4 Tools in Agile Projects https://arshadqa.com

84. 3.4.1 Task Management and Tracking Tools

85. 3.4.2 Communication and Information Sharing Tools

86. 3.4.3 Software Build and Distribution Tools

87. 3.4.4 Configuration Management Tools

88. 3.4.5 Test Design, Implementation, and Execution Tools

89. 3.4.6 Cloud Computing and Virtualization Tools

90. Thanks