# DevLuvs

## Introduction

### Objectives

#### Purpose

This test plan present all testing approaches of Software Quality Assurance (QA) Engineers of DevLuvs Web Application. Having this documentation started means that all ambiguous and vague requirements has been cleared and answered.

Expectations for the Test Plan are as follows:

1. Testing Scope and Limitations
2. Test Items
   1. Features that are covered from versions that were release based on the Story Map
3. Test design and Strategy
   1. Defines Testing Criteria
   2. Defines Testing Types
4. Resources
   1. Software Quality Assurance (QA) Engineers
   2. Design Quality Assurance (QA)
5. Testing environment
   1. Staging
      1. <https://studio-devluvs-highoutput.vercel.app/> - advised to use as of September 29, 2022
      2. <https://dev.devluvs.com/>
      3. <https://studio-devluvs.vercel.app/>

#### Definition

Devluvs -

Landing Page

Dashboard Page

Notebook

Tutorials

Personal Notebooks

Collection Notebooks

#### Scope and Limitations

### Test Items

* Landing Page
  * Add email on waitlist
* Login
  * Login as Normal User
  * Login as Admin User
* Logout
  * Login as Normal User
  * Login as Admin User
* Sign-up
  * Sign-up with only the Email link provided
* Dashboard
  * Access and View all public Posts
  * Search Public Posts
  * Access View Contribution Board Scores
* Posts
  * Create New Posts
  * Add Pages on your New Posts
  * Add Photos on your pages
  * Add Code on your pages
  * Edit Posts
  * Publish Posts
  * Save your posts as Drafts
  * View Preview of your posts (without Publishing or saving it as Draft)
  * View details of the post
  * View sidebar of the post
  * View other comments on the post
  * Heart Comments on the Post
  * Heart Posts
  * Share posts on LinkedIn
  * Share posts on Facebook
  * Share posts on Twitter
  * Add to Notebook
  * Create a notebook on “Add a Notebook”
  * Access and view lists of Published Posts
  * Access and view lists of Draft Posts
  * Delete published posts
  * Delete Draft posts
  * Unpublish published posts - converting to Draft
* Notebook
  * Create a notebook
  * Edit a notebook
  * Access and View all Notebooks
  * Access and view all posts on certain notebook
  * Delete notebook
  * Edit Title and Description on Notebooks
  * Remove posts on Notebook
* Settings
  * Change Username
  * Change profile photo

### Testing Strategy

#### Testing Types and Levels

| NAME                                            | METHOD                                                                            | RESPONSIBLE          | ENTRY CRITERIA                                                                                                    | EXIT CRITERIA                                                              |
| ----------------------------------------------- | --------------------------------------------------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| GUI Testing                                     | Manual Testing                                                                    | Design QA            | Test Environment and                                                                                              |                                                                            |
| Figma or the app design are provided            | Website Design should be aligned to the approved design created by the UI/UX Team |                      |                                                                                                                   |                                                                            |
| Compatibility Testing                           | Manual Testing                                                                    | Software QA          | Test Environment is provided                                                                                      | The application pass from the required devices listed                      |
| Smoke Testing                                   | Manual Testing                                                                    | Software QA          | New builds test environment is provided                                                                           | The application should be out of major and obvious defects.                |
| Functional Testing                              | Manual Testing                                                                    | Software QA          | Smoke Testing has been done. New builds test environment where the Smoke Test is done and Test Data are provided. | -All Test Cases are passed                                                 |
| -All functional defects are found and resolved. |                                                                                   |                      |                                                                                                                   |                                                                            |
| Regression Testing                              | Manual and Automation Testing                                                     | Software QA          | New builds test environment and Test Data are provided                                                            | Test Cases should passed and system should defects are found and resolved. |
| Sanity Testing                                  | Manual and Automation Testing                                                     | Software QA          | New builds test environment and Test Data that are already added to the system are provided                       | Test Cases should passed and system should defects are found and resolved. |
| User Acceptance Testing                         | Manual Testing                                                                    | Business Team/Client | Production Environment and Live Test data are provided                                                            | MVP is followed a                                                          |

### Resources

#### Test Tools

| NAME                    | TOOL   |
| ----------------------- | ------ |
| Task/Project Management | Linear |
| Defect Management       | Linear |
| Test Coverage Monitor   | ——     |

#### Manpower

| ROLE          | QUANTITY | RESPONSIBILITY                     | NAME |
| ------------- | -------- | ---------------------------------- | ---- |
| Test Manager  | 1        |                                    | ‣    |
| Test Lead     | —        |                                    |      |
| Manual QA     | 1        | Do checking on the system manually | ‣    |
| Automation QA | 1        | Do Automation on the system        | ‣ ‣  |


---

# 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/devluvs.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.