Scribd
Upload
14 views

CCMS Smoke Test Plan (1)

The Test Plan outlines the testing process for each sprint cycle, focusing on smoke tests to ensure build stability. It details entry and exit criteria, testing scope, risk mitigation strategies, and testing approaches, including manual and automated testing. The document also includes work estimation for onboarding and payment test suites, specifying tasks, responsible members, and estimated efforts.

Uploaded by

psabdulla65
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views

CCMS Smoke Test Plan (1)

The Test Plan outlines the testing process for each sprint cycle, focusing on smoke tests to ensure build stability. It details entry and exit criteria, testing scope, risk mitigation strategies, and testing approaches, including manual and automated testing. The document also includes work estimation for onboarding and payment test suites, specifying tasks, responsible members, and estimated efforts.

Uploaded by

psabdulla65
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Test Plan

Document Detail

Title: Test Plan


Version: V1
Date: 23rd Aug 2022
Author: Priyadharshini
Contributor:
File Location:

Change Control
Issue Date Version Details Updator
V1 Draft
V2 Added test plan scope

1
1. PURPOSE
Purpose of the test plan document is to provide details on how the testing process will be
conducted within each sprint cycle and for targeted release.

2. Entry Criteria
2.1 Infra in place for Test
1. Pre-prod environment setup - an environment which simulates prod
architecture. URL <>
2. Testing will be done in the same pre-prod, also called dev environment
3. Test Data will be created while performing testing and retained for later use.
4. Staging environment if available for testing. DevOps will set up CI CD pipelines.

2.2 Success of both Build and Unit tests job


1. Post PR commit, Unit test should trigger.
2. On Success of unit tests -> Should trigger build process.
3. Once the build is deployed to the Staging/dev environment, Smoke test will chip
in.

2.3 What actions to be occurred on success/failure of smoke test (need to be decided- one or
all)
1. On Success
a. Dashboard for Reports, Or Github Actions
b. Trigger regression test suite/cycle
2. On Failure
a. Notify via any communication channels - recent PR details.
b. File Bug in JIRA/Track Space(Depend upon the client requirement)

2.4 Schedule - Frequency of Execution


a. Once job for build succeeds
b. Scheduled daily

2.5 POINT of Contact -


a. Framework: QA Lead

3. Exit Criteria

1. Smoke test suite should pass manually and test results uploaded.
2. Automation Smoke suite should pass

2
3. Tests failed with results evaluated, point of contact notified and JIRA tickets raised and tracked
against the test case.

4. TEST SCOPE

This document will focus on ONLY Smoke tests , first 4 scenarios to match entry criteria and
identify the build stability to further test application.
Onboarding Smoke scenarios identified below -
1. Authentication (login, logout, forgot password)
2. Locations (add, edit)
3. Rooms (add, edit)
4. Students (add, edit, enroll, unenroll)

Payments Smoke scenarios identified below -


1. Invoices (create, edit, send)
2. Recurring Plans (create, edit)

5. UPDATE/MODIFICATION of SMOKE TEST


Any update in smoke test count and coverage will be pre-approved by the Product Manager.

6. TEST OUT OF SCOPE - NOT To Be Tested


1. White Box testing - Log and DB assertion not part of Smoke test suite
2. Initially Signup and provider onboarding will not be part of the smoke test suite and will
be pre-requisite data on application.
3. Later, Smoke test will be extended to include provider onboarding.
4. Performance testing
5. Cross Browser testing
6. Device compatibility testing

8. RISK AND MITIGATION PLAN


8.1 Planned Holidays
8.2 Risk
8.2.1 Development of sprint tagged ticket is not completed yet
8.2.2 Configuration issues failed the deployment
8.2.3 Smoke test coverage
8.2.4 Product bugs(across smoke test functionality) would delay the automation efforts.

3
8.3 Mitigation Plan

Build process to be streamlined to ensure deployment process is automated and new libraries
should be validated under unit tests.

Smoke tests should be validated with the Product Manager and updated followed with
approval.
Build failure should be reported early and notified to point of contact.

9. Testing Approaches -

Manual Test -
Until Smoke suite is binded to CI CD pipeline, above scenarios would be tested manually. Tests
will be tracked under smoke test suite, maintained on spreadsheet.

CCMS Smoke test cases url: CCMS Test Case

Automation Test -
1. Automation testing is also used wherein a set of automated test cases are used to run the
smoke tests.
2. This would require identification of Tools, Framework, SignUp/review/approval criteria/ CI-CD
details. This will be documented in the Automation Test Plan.
1. Test Framework – Cypress
2. Test Runner – Mocha
3. CI Platform – Github actions
4. Running a Test Suite at Frequent Intervals — GCP

10. Test Deliverables -


1. Test results and Reports from automation test run.
2. Test Plan Document
3. Test Case Document
4. Bug Report from JIRA

11. ENVIRONMENTS Statistics

4
Testing will be done in a pre-prod environment.
11.1 Browsers
The application should be tested in the latest version of Google Chrome, MS Edge, Safari
11.2 Operating System
The application should be tested in latest versions of Windows and Mac OS

12. Work Estimation


For other applications/modules - identifications of selectors, tests addition and extends infrastructure
to support new modules will be only more recorded efforts once below infra finish.

12.1 Onboarding test suite

S. No. Task Members Estimate of efforts (days)


1 Write Smoke Test cases QA 1
2 Smoke test review and incorporate comments QA Lead 1
3 Smoke Test Execution Manual QA
4 Manual Execution Test Reports QA .5
5 Initial library installation and configuration QA
6 Document library version and standard QA Lead 1
7 Write first smoke script in cypress using javascript QA 1
8 Run test script through test runner QA 1
9 Framework design QA
10.1 GitHub actions for CI CD QA Lead
Common method extraction written in command.js
10.2 file QA
10.3 Test Data (Fixture file :json file) QA
Cross browser testing/Parallelisation/ headless
10.4 mode QA
10.5 Page object file, Page Selector file QA
10.6 Configure screenshot and recording QA 5
11 Add remaining tests in smoke test suite QA 2
12 Code review QA Lead 1
13 Code review comments incorporate QA 2
14 Plugin for CI CD - GCP QA Lead 3
15 Automation test report analysis QA 3
Total 20.5

12.2 Payment Test suite

5
S. No. Task Members Estimate of efforts (days)
1 Write Smoke Test cases QA .5
2 Smoke Test Execution Manual QA
3 Manual Execution Test Reports QA .5
Write first payment smoke script in cypress using
4 javascript QA 2
5 Run test script through test runner QA .5
6 Cross browser testing for Safari on Cypress 10+
version QA 1
7 Add remaining tests in smoke test suite QA 10
8 Code review and comments incorporated QA Lead 2
9 Automation test report analysis QA 1
10 Refactor structure QA 2
11 Add page object model for invoice/recurring plans QA 4
Total 22.5

You might also like