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 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 Test
- UAT Tests
- Unit Tests
- Usability Tests
- Non-functional Tests
- Performance test
- Load test
- Stress test
- Soak test
Test or not to test
- Who makes decisions about what to test?
- The cost of testing irrelevant items
- Calculating ROI (what if something fails analysis)
- 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 (selecting and prioritizing scenarios)
- Designing tests
- Preparing data
- Preparing the environment
- Creating or recording tests
- Executing the test
- Analysis and reporting
- Conclusions and improvement
- When to say "stop"
The Product Owner and Tests
- The customer representative and test priority
- Prioritizing tests
- Writing effective user stories for UAT
- Acceptance criteria
- Group exercise to develop customer requirements, write stories based on those requirements, and create tests
The sprint
- Sprint backlog and test user stories
- Group exercise to plan a sprint
Concluding a sprint
- The Scrum review meeting serves as a test
Is Agile and Scrum right for you?
- Review of the Scrum process
- Comparison with other methodologies
- Benefits of pair programming
- Q&A 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.
