Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Where do requirements originate?
- Traditional Business Analysis
- Use Cases, Scenarios, and Tests
- Non-functional requirements
- Performance
- Conformance
- UML in Business Analysis
Introduction to testing
- Functional Tests
- Regression Testing
- UAT Tests
- Unit Tests
- Usability Tests
- Non-functional Tests
- Performance Testing
- Load Testing
- Stress Testing
- Soak Testing
To test or not to test
- Who decides what to test?
- The cost of testing irrelevant items
- Calculating ROI (what if analysis fails)
- The role of the Test Manager
The testing process
- Testing as a process and strategy
- Identifying testing needs
- Gathering requirements (use cases, user stories)
- Scoping (choosing and prioritizing scenarios)
- Designing tests
- Preparing data
- Preparing the environment
- Creating or recording tests
- Executing the tests
- Analysis and reporting
- Conclusions and improvements
- Knowing when to stop
The Product Owner and Tests
- The customer representative and test priority
- Prioritizing tests
- Writing effective stories for UAT
- Acceptance criteria
- Group exercise: producing customer requirements, writing stories based on those requirements, and creating tests
The Sprint
- Sprint backlog and user stories for testing
- Group exercise: planning a sprint
Completing a Sprint
- The Scrum review meeting as a form of testing
Is Agile and Scrum right for you?
- Review of the Scrum process
- Comparison with other methodologies
- Benefits of pair programming
- Question and Answer session
Requirements
None.
14 Hours
Testimonials (2)
There has been a wide coverage of many topics. This fostered our own discussong internally
Pierre - Seebyte
Course - Agile Software Testing
The theory, the examples, the excercices, the explanations.
