๐จโ๐ปDevLuvs
Source: https://highoutput.notion.site/Test-Plan-e7193f8c78784d47a8bc5d2949367d84
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:
Testing Scope and Limitations
Test Items
Features that are covered from versions that were release based on the Story Map
Test design and Strategy
Defines Testing Criteria
Defines Testing Types
Resources
Software Quality Assurance (QA) Engineers
Design Quality Assurance (QA)
Testing environment
Staging
https://studio-devluvs-highoutput.vercel.app/ - advised to use as of September 29, 2022
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 | โฃ โฃ |
Last updated