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 come from?
- Traditional Business Analysis
- Use Cases, Scenarios, and Tests
- Non-functional requirements
- Performance
- Conformance
- UML in Business Analysis
Introduction to testing
- Functional Tests
- Regression Tests
- UAT Tests
- Unit Tests
- Usability Tests
- Non-functional Tests
- Performance tests
- Load tests
- Stress tests
- Soak tests
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 both a process and a strategy
- Identifying testing needs
- Gathering requirements (use cases, user stories)
- Scoping (selecting and prioritizing scenarios)
- Designing tests
- Preparing data
- Preparing the environment
- Creating or recording tests
- Executing the test
- Analysis and reporting
- Conclusions and improvements
- 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 requirements, and creating tests
The sprint
- Sprint backlog and test user stories
- Group exercise to plan a sprint
Concluding a sprint
- The Scrum review meeting is a test
Is Agile and Scrum suitable 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.
