Testing Strategy

Energy Vision - Test Strategy

Scope

This document exists to secure a common understanding of how we will ensure quality in the Envis project. The document will be worked on until the team can agree and approve on it, after which more specific test plans will be made.

Test Approach

It defines

• Process of testing
• Testing levels
• Roles and responsibilities of each team member
• Types of Testing ( Load testing, Security testing, Performance testing etc.)
• Testing approach & automation tool if applicable
• Adding new defects, re-testing, Defect triage, Regression Testing and test sign off

Process of testing

Testing levels

• Unit testing
• Component testing -> includes testing for a11y and performance
• Integration testing -> Testing wherever we access API's
• System testing -> SEO, a11y on a higher level, testing multiple screen sizes, etc
• Acceptance testing -> User Stories, definition of done

Responsibilities

First of all testing is a responsibility of the team. Everyone should do their part in ensuring good quality and compliance with any rules that may apply.

In addition the following specific responsibilities are defined:

Role	Responsibility
Dev team	- Test for a11y while developing - Use screen readers - Use Lighthouse
PO	Acceptanse testing - verify functionality to acceptance criteria in user stories
TBD

Test Environment

• Define number of requirement and setup required for each environment
• Define backup of test data and restore strategy

Testing Tools

• Automation and Test management tools needed for test execution
• Figure out number of open-source as well as commercial tools required, and determine how many users are supported on it and plan accordingly

Release Control

• Release management plan with appropriate version history that will make sure test execution for all modification in that release

Risk Analysis

• List all risks that you can estimate
• Give a clear plan to mitigate the risks also a contingency plan

Review and Approvals

• All these activities are reviewed and sign off by the business team, project management, development team, etc.
• Summary of review changes should be traced at the beginning of the document along with approved date, name, and comment