Project Test Plan

Project Overview

Project Test Plan (PTP) covers the Development, System, Acceptance, and Production Deployment test strategy for DAaaS frontend, which relates to all project phases. This document provides high-level insight into the testing performed in the different layers of the system and explains the practice followed by the project team from the early project days to interim deployment, UAT and Production release. However, as the project progress, aspects of the Test Plan will be updated as and when the project scope change.

Project and Business Objective

Data Analytics as a Service (DAaaS) frontend project is a new GUI platform for an existing system. The objective is to select libraries and frameworks to support the creation of a library of software components that can be used to create specialist GUIs for different aspects of DAaaS.

---

Project Test Strategy

Project Test strategy is fragmented into development testing, system testing, and User evaluation and is carried out by various member of the team in different project phases.

In-scope

• Functional and quality requirements user stories testing
• Unit and Integration testing for the developed code
• UI testing for usability
• WebAPI endpoints tested for functional, performance and security scenarios
• Browser compatiblity testing in Chrome, Firefox and Edge

Out-of-scope

• Migration testing
• Penetration testing
• Accessibility testing
• Browsers that are not listed in-scope

---

Development Testing

Development testing is managed and maintained by the project developers throughout the development phase. Automated Unit and Integration tests will be created and monitored around all the features where business logic materialises. Formal and informal peer reviews are performed throughout the project to ensure coding standards and good practice guidelines are followed.

System Testing

System testing is performed to verify that the delivered system fulfils the captured user requirements. Project tester upholds the system and regression testing of WebAPI and GUI test responsibilities; this includes the broad system testing lifecycle. System testing lifecycle begins when project development starts by defining the test scenario and carries on with the test execution, finding issues, results recording and concludes with regression and deployment testing. Automated regression tests shall be created where possible on a stable build and executed in a dedicated Test environment using managed test data.

Test scenarios will be developed for all the stories planned in the release either ahead of the development or during development and recorded in the story. Post-development the project tester will prepare and execute the test scenarios, to verify the functionality of user stories developed for the sprint. Activities for system test execution include:

• Execute pre-prepared test scenarios
• Update test scenarios to reflect any additions/changes in the story post development
• Identify and communicate defects to the developers
• Test with a variety of test data
• Carry out unscripted testing

Quality requirements testing

Scalability

Performance and scalability assessment will be performed throughout the development phase along with functional requirements testing to ensure DAaaS frontend perform well under the expected workload. System ‘Response time’ will be tested on all WebAPI endpoints with production like data. Performance testing will be a shared responsibility between the project tester and developers. Taurus may be used to measure the WebAPI endpoints response time. SiteSpeed may be used to measure the web page load time.

Security

Functional requirements security like authentication, user access role, data confidence and similar will be in testing scope. In addition to that, OWASP ASVS Level 1 recommendations, which are in-line with the project requirements scope, will be assessed.

Compatibility

Browser compatibility testing will be carried out in the latest versions of Chrome, Firefox, Edge and Safari. GhostLab a synchronized browser testing tools will be used to perform browser compatibility testing.

User Acceptance Testing

In sprint review meetings, the project team will demonstrate the requirements implementation in the Test environment. Post-review meeting, the business users may perform the user acceptance testing in a stable environment to evaluate the functionality and usability of the application. Functional testing may be focussed on acceptance of the system requirements and Usability testing focussing on the GUI design, look and feel, ease of application use from the Business perspective.

Production Deployment Testing

Test deliverables