• 1. Introduction
  • 1.1 Version Control
  • 1.2 Overview
  • 1.3 Scope
  • 1.4 Terminology
• 2. FEATURES TO BE TESTED
  • 2.1 Login (LG)
  • 2.2 Register (RG)
  • 2.3 Accessibility (AC)
  • 2.4 Hardware Usage (HU)
• 3.FEATURES NOT TO BE TESTED
• 4. ITEM PASS/FAIL CRITERIA
  • 4.1 Exit Criteria:
• 5. REFERENCES
• 6. TEST DESIGN SPECIFICATIONS
  • 6.1 Login (LG)
    • 6.1.1 Sub features to be tested
      • 6.1.1.1 Admin (LG.AD)
      • 6.1.1.2 User (LG.US)
    • 6.1.2 Test Cases
  • 6.2 Register (RG)
    • 6.2.1 Sub features to be tested
      • 6.2.1.1 Admin (RG.AD)
      • 6.2.1.2 User (RG.US)
    • 6.2.2 Test Cases
  • 6.3 Accessibility (AC)
    • 6.3.1 Subfeatures to be tested
      • 6.3.1.1 System (Sys.AD)
    • 6.3.2 Test Cases
  • 6.4 Hardware Usage (HU)
    • 6.4.1 Subfeatures to be tested
      • 6.4.1.1 System(Sys.AD)
    • 6.4.2 Test Cases
• 7. Detailed Test Cases
  • 7.1 LG.AD.US 01
  • 7.2 LG.AD.US 02
  • 7.3 LG.AD.US 03
  • 7.4 LG.AD.US 04
  • 7.5 RG.AD.US 01
  • 7.6 RG.AD.US 02
  • 7.7 RG.AD.US 03
  • 7.8 RG.AD.US 04
  • 7.9 AC.SYS 01
  • 7.10 AC.SYS 02
  • 7.11 AC.SYS 03
  • 7.12 AC.SYS 04
  • 7.13 AC.SYS 05
  • 7.14 AC.SYS 06

1. Introduction

1.1 Version Control

1.2 Overview

Interface accessibility, hardware usage, database connection will be tested

1.3 Scope

This document will include the scenarios about every possible bug that can occur and their testing phases.

1.4 Terminology

2. FEATURES TO BE TESTED

This section lists and gives a brief description of all the major features to be tested. For each major feature there will be a Test Design Specification added at the end of this document.

2.1 Login (LG)

All the users must login successfully to the system.

2.2 Register (RG)

All the users must register successfully to the system.

2.3 Accessibility (AC)

Home page, regions page, contact page, login page, register page, must be successfully accessible.

2.4 Hardware Usage (HU)

Hardware usage must be optimal.

3. FEATURES NOT TO BE TESTED

Real time process because we don’t have the necessary equipment.

4. ITEM PASS/FAIL CRITERIA

Login and register pass if the user logins or registers successfully. Accessibility passes if the pages are successfully accessed. Hardware usage passes if the hardware usage is optimal.

4.1 Exit Criteria:

• 100% of the test cases are executed • 100% of the test cases passed • All test cases passed

5. REFERENCES

• [1] Group2_SRS_100, January 16, 2022
• [2] Group2_SDD_100, January 16,2022

6. TEST DESIGN SPECIFICATIONS

6.1 Login (LG)

6.1.1 Sub features to be tested

6.1.1.1 Admin (LG.AD)

The admin can successfully login.

6.1.1.2 User (LG.US)

The user can successfully login.

6.1.2 Test Cases

Here list all the related test cases for this feature

6.2 Register (RG)

6.2.1 Sub features to be tested

6.2.1.1 Admin (RG.AD)

Admin can be registered successfully

6.2.1.2 User (RG.US)

User can be registered successfully

6.2.2 Test Cases

Here list all the related test cases for this feature

6.3 Accessibility (AC)

6.3.1 Subfeatures to be tested

6.3.1.1 System (Sys.AD)

• Ram mustn’t be used more than 60%
• CPU mustn’t be used more than 60%
• GPU mustn’t be used more than 40%

6.3.2 Test Cases

Here list all the related test cases for this feature

• Home page, regions page, contact page, login page, register page

6.4 Hardware Usage (HU)

6.4.1 Subfeatures to be tested

6.4.1.1 System(Sys.AD)

• Ram mustn’t be used more than 60%
• CPU mustn’t be used more than 60%
• GPU mustn’t be used more than 40%

6.4.2 Test Cases

Here list all the related test cases for this feature

7. Detailed Test Cases

7.1 LG.AD.US 01

7.2 LG.AD.US 02

7.3 LG.AD.US 03

7.4 LG.AD.US 04

7.5 RG.AD.US 01

7.6 RG.AD.US 02

7.7 RG.AD.US 03

7.8 RG.AD.US 04

7.9 AC.SYS 01

7.10 AC.SYS 02

7.11 AC.SYS 03

7.12 AC.SYS 04

7.13 AC.SYS 05

7.14 AC.SYS 06