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 gets tested?
- The cost of testing irrelevant features
- Calculating ROI (what if analysis fails)
- The role of the Test Manager
The testing process
- Testing is both a process and a strategy
- Identifying testing needs
- Gathering requirements (use cases, user stories)
- Scoping (choosing and prioritising scenarios)
- Designing tests
- Preparing data
- Preparing the environment
- Creating or recording tests
- Executing the test
- Analysis and reporting
- Conclusions and improvement
- Knowing when to stop
The product owner and tests
- The customer representative and test prioritisation
- Prioritising tests
- Writing effective stories for UAT
- Acceptance criteria
- Group exercise to produce customer requirements and write stories based on the 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 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.
