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

### 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

<table><thead><tr><th>Role</th><th>Quantity</th><th>Responsibility</th><th width="150">Name</th></tr></thead><tbody><tr><td>Test Manager</td><td>1</td><td></td><td></td></tr><tr><td>Test Lead</td><td>1</td><td></td><td></td></tr><tr><td>Tester</td><td>1</td><td></td><td></td></tr></tbody></table>

4.3 Hardware

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hov-qa.gitbook.io/hov-qa-engineers/projects/subsit/test-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.