⚙️Mehira

About

Building a software startup is hard. And, with very limited resources in terms of time and money, it is crucial that a software startup team deliver working software as quickly as possible. SaaS applications usually require a common set of components such as user management, authentication, file storage, and billing. If these components can be made available as nicely packaged off-the-shelf components that can be reused indefinitely, software startup teams can focus on what really matters, building the components that make their software unique.

TEST PLAN

0.1: Introduction

1.0 Objectives

1.1 Purpose

This test plan presents all Testing approaches of Software QA Engineers to the Mehira 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

1. Mehira - Mehira will focus on building components that are easy to use. AWS components tend to be complex because they cater to a very large audience. By carefully setting the scope smaller and clearly defining the target users, we will be able to design simpler APIs and easier-to-use SDKs.

2. Dashboard - to follow

3. Customer - the page wherein the Leads, Account, Group, and Preference data of a certain project is displayed

4. Billing - the page where the customer finds his/her current plan, billing information, and plan listing is displayed

5. Email - page where the user can view, send, delete, update, and create email templates

6. File Storage - to follow

7. Setting - The page wherein the Admin can invite members, view, remove, and resend invitations from the pending invite list, edit and delete a project, edit, delete, and add email domain identity, and can add an environment

1.3 Components

2. Customer Management, Authentication and Authorization

• customer authenticates with email address

• customer authenticates with Google account

• customer authenticates with Github account

• customer authenticates with Slack account

• member sees all customer accounts

• member creates a customer account

3. Billing

• customer sees the pricing tiers

• customer updates the payment method

• customer updates the subscription

• customer sees all the invoices

• customer receives the invoices through email

• member configures the pricing tiers

4. Email

• member sends an email

• member creates an email template

• member sends bulk emails

5. File Storage

• customer uploads a file

• customer downloads a file

• member sees the list of files

• member downloads a file

6. Notifications

7. CDN

8. Data Storage

9. Feature Flags

10. Serverless Computing

11. User Personas

Persona	Role
Owner	Creator of organization
Member	user invited by Owner into the organization
User	refers to either Owner or Member
Customer	users managed by the organization

1.4 Scope and limitation

• Mehira will focus on building components that are easy to use

• Users need to register first using their email addresses

• Users registrations requires their email address.

• Testing will cover the following features of Mehira

  • Customer Registration

  • Customer Authentication

  • Customer Account Management

  • Lead Generation

  • Email

  • Billing

  • Settings

  • File Storage

  • Documentation

  • Preferences

• For the applications first release version, the testing will only be done both manual and automation

• Before release test will be run from staging environment.

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

2. 0 Test Items

• Registration

  • Register as a User

• Customer Authentication

  • Authenticate as a customer using his/her email address

• Login

  • Login as a User

• Logout

  • Logout as a User

• Customer tab

  • Leads

    • gathers lead

    • imports lead

    • exports lead

    • searches lead

    • filters lead

    • views lead

    • edits lead

    • creates lead

    • deletes lead

  • Accounts

    • sees customer account details

    • sees newly created customer account

    • creates customer account

    • edits customer account

    • deletes a customer account

    • imports customer account via CSV file

    • exports customer accounts via CSV file

    • searches for a customer account

    • filters customer accounts by Group or Date created

  • Groups

    • searches a group of customer accounts

    • edits group of customer accounts

    • views group of customer accounts

    • adds customer account to a group

    • creates a group

    • deletes a group

  • Preference (to follow)

• Billing

  • sees the plan listing

  • sees the billing dashboard

  • subscribes to the application

  • pays for chosen plan

  • updates plan

  • updates payment method

  • updates billing period

  • updates billing email

• Email

  • views email templates

  • creates new email template

  • edits an email template

  • deletes and email template

  • sends an email with selected template, and recipient (s)

  • views sent email

• File Storage (to follow)

• Setting

  • deletes an environment

  • edits an environment

  • adds project

  • views email domain entities

  • views environments

  • views projects

  • invites members

  • views pending invites & members

  • removes a member from the pending invite list

  • resends the invitation to a member from the pending invite list

  • edits a project

  • deletes a project

  • edits an email domain identity

  • deletes an email domain identity

  • adds an email domain identity

  • adds an environment

3.0 Testing Strategies

3.01 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	Manuak	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	Height.app
Defect Management	Height.app
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