TESTING 4 ALL BOOTCAMP

This is a self-learning module, available to learners over a 2-month period during which they are supported by a team of software testing experts. Using an experiential, hands-on learning approach with the Software Testing Simulator, the Fundamentals module enables learners to experience and acquire software testing skills across a range of typical test activities, types and techniques. The use of the simulator ‘brings to life’ underlying testing knowledge and theory into real applications. It is a ‘Learn by doing’ approach, meaning anyone can have a go at this module.

A variety of typical iterative software development scenarios are simulated in self-contained sprint assignments, with realistic content that enables testers to analyse the scenarios, then design and execute tests to meet the acceptance criteria and detect carefully seeded defects in the System Under Test (SUT).

As well as establishing the correct behaviour of the SUT, learners establish what was wrong in terms of defects detected, and crucially, following analysis of the assignment debrief, they can work out for themselves where they went wrong.

Key Learner Outcomes
1. Did your Analysis identify adequate test coverage?
2. Did you Accurately Design tests to implement the coverage required?
3. Did you Execute the tests Diligently?
4. Did you Observe the behaviour of the software to Detect the defects?
5. Did you Accurately Record and Report the defects?

The Data Driven Test Automation module provides the learner with the skills necessary for working in scenarios which call for the repetition of tests, notably regression testing. Using the Test Automation framework in the Software Testing Simulator, this module takes the learner through a typical process to design and build test data inputs, convert them into a format that can be used by the framework, then automatically execute the tests against the SUTs using the framework.

Anomalies from expected behaviour are assessed against known defects in the scenario to highlight any deficiencies in the test data inputs, thereby ensuring tests need to be both effective and efficient for regression testing purposes.

Coming soon

Supporting the 'shift-left' principle, learners use a checklist-based review to identify defects in documentation. The Software Testing Simulator has a workflow for a 'Document Under Test' (DUT) which enables the learner to record the potential issues with the acceptance criteria against the checklist items. Those issues can then be classified in terms of risk and priority using the guidelines in the assignment.

Coming soon

The ATDD module takes the learner through a journey from start to finish, from an imperfect set of requirements through to working software that meets the requirements. It includes:

• The early review of the test basis.
• Specification of tests in a 'Given, When, Then' natural language format.
• The build of both effective tests and efficient tests utilising the data-driven test automation framework.
• Model artefacts, provided at various points in the ATDD process to assist the learning.

The ATDD can be run on an individual basis in a learner's own time, or it can be used as an excellent collaborative learning experience for a class.

Coming soon

This module 'puts it all together' and gives the learner the skills to take on multiple software testing activities equipped with the analytical and critical thinking skills needed to rise to many different testing challenges.

The Advanced module takes the learner into new territory, experiencing testing at different levels using a business theme and epic scenarios. It compares the 'end-to-end' testing model against a 'top-down' feature testing model, and uses further combinatorial techniques, including pairwise, in the context of risk-based testing. More complex scenarios are covered, including the use of multiple test techniques in a given scenario that can be combined to optimise test coverage based on risk.

The module also includes testing from different risk-based business perspectives using the business scenario outlined in the theme and epic. It includes situations in which defects occur at different levels of previously tested software, why that might occur and the classification of defects in terms of risk and priority. It also looks at optimisation of testing coverage in test design, considering good and bad approaches.

Coming soon