|
|
|
INTRODUCTION
|
|
|
|
# INTRODUCTION
|
|
|
|
|
|
|
|
|
|
|
|
This is the master test plan for a product called Contriboard.
|
|
|
|
|
|
|
|
Project and project objective
|
|
|
|
## Project and project objective
|
|
|
|
Objective of the master test plan
|
|
|
|
The objective of the Master Test Plan is to inform all of the individuals involved in testing about the testing process approach, including the mutual relations and activities. This plan describes approach and activities.
|
|
|
|
|
|
|
|
Involved in creating the master test plan
|
|
|
|
## Involved in creating the master test plan
|
|
|
|
This test plan is created by Mikko Kemppinen and Arttu Henell.
|
|
|
|
|
|
|
|
Client
|
|
|
|
### Client
|
|
|
|
Clients are normal people who are using Contriboard.
|
|
|
|
|
|
|
|
Provider
|
|
|
|
### Provider
|
|
|
|
JAMK University of Applied Sciences provides Challenge Factory with workspace, skills, computers and technology.
|
|
|
|
|
|
|
|
Scope
|
|
|
|
### Scope
|
|
|
|
New upcoming testable features can be found in Roadmap. Application's testable functionalites are determined via use cases. Each use case is tested with correct and incorrect inputs for high coverage. Stability, scalability and performance are also in the scope range.
|
|
|
|
|
|
|
|
Out of scope
|
|
|
|
Acceptants and acceptance criteria
|
|
|
|
### Out of scope
|
|
|
|
### Acceptants and acceptance criteria
|
|
|
|
Acceptance of tested functionality is based on the correct way of working for that specific functionality. Any function cannot overthrow the application. Serious errors can't exist in the compulsory functionalities of the application. Manual test cases are predetermined for passing or failing.
|
|
|
|
|
|
|
|
DOCUMENTATION
|
|
|
|
TEST STRATEGY
|
|
|
|
# DOCUMENTATION
|
|
|
|
|
|
|
|
# TEST STRATEGY
|
|
|
|
Main functionalities are tested via Robot Framework, FMBT and manual testcases.
|
|
|
|
|
|
|
|
APPROACH
|
|
|
|
# APPROACH
|
|
|
|
Each test scenarios are created by following imaginary stories about clients using the application. For effective automation testing the stories follow an common storyline for a normal user.
|
|
|
|
|
|
|
|
TEST LEVELS
|
|
|
|
# TEST LEVELS
|
|
|
|
1. Unit testing
|
|
|
|
The programmer creates functional tests during the coding phase with Karma. Created test can be found here(functional testing).
|
|
|
|
2. System testing
|
| ... | ... | |
| ... | ... | |