Testing Assignment
Table of Contents
1 About This Sprint
In this sprint we momentarily pause the steady onmarch of UML and instead focus on how to test the designed software.
In this sprint you create a test plan for your system, based on your system sequence diagrams.
2 User Stories covered in this Sprint
- As a product manager I want to make sure that we are building software of high quality.
- As a product manager I want to make sure that fixed bugs do not re-appear so that I can build the product incrementally.
- As a teacher I want to evaluate the students’ ability to identify and describe meaningful tests from early design artefacts so that I know they understand how test and design go hand in hand.
3 Introduction
The basics of a test plan is that you should identify what to test, how to test it, and when to test or re-test it. Using your current understanding of the system, for example your system sequence diagrams, you are able to create a first version of your test plan (To be specific, the how and when is not depending on you having produced any design artefacts at all yet, but it makes sense to bundle this with the what).
4 Learning Material
Please review the sprints concerning
5 Experiential Learning
5.1 Assignment: Create Test Suite
Create a regression test suite. You will continue to use and extend this test suite later in the course. At this stage, you are focussing on adding test cases for your API endpoints. Use the system events from your System Sequence Diagrams as API endpoints, and express the tests in your chosen test framework.
Tasks:
- List all the system events from all the system sequence diagrams.
- For each system event, identify preconditions (e.g. if the system event depends on that another event is triggered first).
- For each system event, identify what inputs are allowed.
- For each system event, identify what outputs are expected.
- For each system event, Write one or several test in your test framework that tests for the allowed inputs and the expected outputs.
Commit and push this document to your project repository.
Conditions of Satisfaction:
When marking this part of the assignment we are looking for the following:
- size of assignment: Are there test cases for all system events from all the system sequence diagrams?
- For each test case: Does it test normal input as well as explore boundary values?
- For each test case: Does the test case evaluate a meaningful behaviour?
6 Sprint Acceptance Tests
You are done with this sprint when:
- You bave created an automated test suite for your API endpoints
- You have committed/pushed this suite to your project repository
You may also have
- Updated your Sprint Test Plan
- Updated your Course Backlog
- Set up a continuous integration solution to run your tests on commit