Test plan

1. Introduction

1.1 Purpose

The purpose of the Iteration Test Plan is to gather all of the information necessary to plan and control the test effort for a given iteration. It describes the approach to testing the software. This Test Plan for Art+Game supports the following objectives:

Identifies the items that should be targeted by the tests.
Identifies the motivation for and ideas behind the test areas to be covered.
Outlines the testing approach that will be used.
Identifies the required resources and provides an estimate of the test efforts.

1.2 Scope

This document describes the used tests, as they are unit tests and functionality testing.

1.3 Intended Audience

This document is meant for internal use primarily.

1.4 Document Terminology and Acronyms

SRS Software Requirements Specification
n/a not applicable
tbd to be determined

1.5 References

| Reference | |—| | SAD | | UseCases (Kinda) |

2. Evaluation Mission and Test Motivation

2.1 Background

By testing source code, we ensure our application to run smoothly. The goal is to make sure, that our application does not run into any unexpected errors.

2.2 Evaluation Mission

The mission of this test plan is to prevent errors in production and ensure an outstanding software quality.

2.3 Test Motivators

Our testing is motivated by

quality risks
technical risks,
use cases
functional requirements

3. Target Test Items

The listing below identifies those test items (software, hardware, and supporting product elements) that have been identified as targets for testing. This list represents what items will be tested.

Items for Testing:

Unity Testing Framework

4. Outline of Planned Tests

4.1 Outline of Test Inclusions

Testing the game with EditTests and PlayTests.

4.2 Outline of Other Candidates for Potential Inclusion

Stress Testing the application. Findung security holes.

4.3 Outline of Test Exclusions

n/a

5. Test Approach

5.1 Initital Test-Idea Catalogs and Other Reference Sources

n/a

5.2 Testing Techniques and Types

5.2.1 Game Testing

5.2.2 Fun Testing

n/a

5.2.3 Business Cycle Testing

n/a

5.2.4 User Interface Testing

n/a

5.2.5 Performance Profiling

n/a

5.2.6 Load Testing

n/a

5.2.7 Stress Testing

n/a

5.2.8 Volume Testing

n/a

5.2.9 Security and Access Control Testing

n/a

5.2.10 Failover and Recovery Testing

n/a

5.2.11 Configuration Testing

n/a

5.2.12 Installation Testing

n/a

6. Entry and Exit Criteria

6.1 Test Plan

6.1.1 Test Plan Entry Criteria

6.1.2 Test Plan Exit Criteria

6.1.3 Suspension and Resumption Criteria

n/a

7. Deliverables

7.1 Test Evaluation Summaries

7.2 Reporting on Test Coverage

n/a

7.3 Perceived Quality Reports

n/a

7.4 Incident Logs and Change Requests

n/a

7.5 Smoke Test Suite and Supporting Test Scripts

n/a

7.6 Additional Work Products

7.6.1 Detailed Test Results

7.6.2 Additional Automated Functional Test Scripts

n/a

7.6.3 Test Guidelines

Easy tests should be tested for functionality. Due to timing constraints,the quality of a test might suffer. E.G. not all possible inputs can be tested.

7.6.4 Traceability Matrices

n/a

8. Testing Workflow

Developers should execute tests locally before pushing source code.

9. Environmental Needs

This section presents the non-human resources required for the Test Plan.

9.1 Base System Hardware

The following table sets forth the system resources for the test effort presented in this Test Plan.

Resource	Quantity	Name and Type
n/a	n/a	n/a

9.2 Base Software Elements in the Test Environment

The following base software elements are required in the test environment for this Test Plan.

Software Element Name	Version	Type and Other Notes
n/a	n/a	n/a

9.3 Productivity and Support Tools

The following tools will be employed to support the test process for this Test Plan.

Tool Category or Type	Tool Brand Name
Code Hoster	github.com

9.4 Test Environment Configurations

n/a

10. Responsibilities, Staffing, and Training Needs

10.1 People and Roles

This table shows the staffing assumptions for the test effort.

Human Resources

Role	Minimum Resources Recommended (number of full-time roles allocated)	Specific Responsibilities or Comments
Test Manager	1	Provides management oversight. Responsibilities include: planning and logistics agree mission identify motivators acquire appropriate resources present management reporting advocate the interests of test evaluate effectiveness of test effort
Test Designer	2	Defines the technical approach to the implementation of the test effort. Responsibilities include: define test approach define test automation architecture verify test techniques define testability elements structure test implementation
Tester	4	Implements and executes the tests. Responsibilities include: implement tests and test suites execute test suites log results analyze and recover from test failures document incidents
Test System Administrator	1	Ensures test environment and assets are managed and maintained. Responsibilities include: administer test management system install and support access to, and recovery of, test environment configurations and test labs
Database Administrator, Database Manager	1	Ensures test data (database) environment and assets are managed and maintained. Responsibilities include: support the administration of test data and test beds (database).
Implementer	4	Implements and unit tests the test classes and test packages. Responsibilities include: creates the test components required to support testability requirements as defined by the designer

10.2 Staffing and Training Needs

n/a

11. Iteration Milestones

Milestone	Planned Start Date	Actual Start Date	Planned End Date	Actual End Date
n/a	n/a	n/a	n/a	n/a

12. Risks, Dependencies, Assumptions, and Constraints

13. Management Process and Procedures

n/a