Test plan

Version	Date	SQA
0.1	July 20, 2022

0.1: Introduction

1.0 Objectives

1.1 Purpose

This test plan presents all Testing approaches of Software QA Engineers to Subit application. Having this documentation started means that all ambiguous and vague requirements has been cleared and answered. What to expect in the test plan:

1. Testing Scope and Limitation

2. Test Items

   1. Features that are covered from version 0.1 and 0.2 in the story map

3. Test design and Strategy

   1. Defines Testing Criteria

   2. Defines Testing types

4. Resources

   1. QA engineers

5. Test environment

   1. (As of this writing, no environment provided yet for testing)

1.2 Definition

Subit- A finance software that provide financial services such Spending as analytical insights and reports, centralized collection of subscription receipts, notification and alerts.

Insights- The page that contains analytical report of the user spendings and high priority subcribed applications notification window. Alerts and notifications - ****Can be found at the insight page and was shown as info box with subscription details

Receipts - Application receipts that are wither added by email or updloaded pdf file.

1.3 Scope and limitation

• Subit only support applications from Vercel, Atllassian, Figma, Notion, Github.

• Receipts pdf file or subscribed emails for the said applications are the only accepted at the “Add Reciept” feature.

• Users registrations requires their email address.

• Testing will cover the following features of Subit

  • Insights

    • Spending distribution analytics

    • Notifications

  • Receipts

  • Applications

  • Settings

• For the applications first release version, the testing will only be in manual

• Before release test will be run from staging environment.

• Test steps to be used are in Gherkin non UI approach.

• In first release, the test will be run in PC/Mac browsers

  • Chrome

  • Safari

  • Firefox

2.0 Test Items

• Login

  • Sign in as user

• Logout

  • Logout as user

• Add Receipt

  • upload PDF receipts

  • forward invoices to Subit address

• Insights

  • Notifications (high priority subscribed applications)

  • Analytical report (user spending

• Receipts

  • Applications

  • Status

  • Type

• Applications

  • Application name

  • Total Spending

  • Start Date

  • Monthly change

• Settings

  • User’s email credentials

  • My Account tab

3.0 Testing Strategy

3.1 Testing Types and Levels

Name	Method	Responsible	Entry Criteria	Exit Criteria
GUI Testing	Manual	SQAE	Test environment has been provided Figma or the app design is provided	No more ambiguous design Application UI are align to the approved design layout All changes from the first approval has been applied to the application environment
Compatibility Testing	Manual	SQAE	Test environment has been provided.	The application pass from the required devices that is is used.
Smoke testing	Manual/Automated	SQAE	New version/builds test environment has been provided. Test data are available	Smoke test case passed Major and obvious defects are found
Functional testing	Manual	SQAE	Smoke testing has been done New version/builds of test environment has been setup Test data are available	All test cases are passed All software functionality defects are found.
Regression testing	Manual/Automated	SQAE	New version/builds test environment has been provided. Test data are available	Defects from the features major changes has been found Regression test cases are passed. Regression test case are with automation test.
Sanity Testing	Manual/Automated	SQAE	New prod release/build has been provided Test data for viewing are available	The prod release is stable to proceed further into more functional testing. Sanity test cases are passed Sanity Feature are with automation test.
User Acceptance testing	Manual	SQAE	Demo/Prod build is provided Live and test data is present	Major defects has been identified and hot-fixed. build is ready for go Live

4.0 Resources

4.1 Test Tools

Name	Tools
Task/Project Management	JIRA
Defect Management	JIRA
Test Coverage Monitor	Requirements Traceability Matrix

4.2 Manpower

Role	Quantity	Responsibility	Name
Test Manager	1
Test Lead	1
Tester	1

4.3 Hardware

Item	Quantity	Description
PC	1	Windows OS
Macbook(Browserstack)	1	Mac OS