Test Plan Results for MOBILE SCHOOL MANAGEMENT SYSTEM (MSMS)

You can access the PDF file through this link : MSMS-Test-Plan-Results

Table of Contents

• 1.INTRODUCTION
• 1.1 Version Control
• 1.2 Overview
• 1.3 Scope
• 1.4 Terminology
• 2.FEATURES TO BE TESTED
• 2.1 User Type (UT)
• 2.2 Login (LG)
• 2.3 User Function(UF) 2
• 3.FEATURES NOT TO BE TESTED
• 4.ITEM PASS/FAIL CRITERIA
• 4.1 Exit Criteria
• 5.REFERENCES
• 6.TEST DESIGN SPECIFICATIONS
• 6.1 User Type (UT)
• 6.1.1 Subfeatures to be tested
• 6.1.2 Test Cases
• 6.2 Login Page (LP)
• 6.2.1 Subfeatures to be tested
• 6.2.2 Test Cases
• 6.3 User Function(UF)
• 6.3.1 Subfeatures to be tested
• 6.3.2 Test Cases
• 6.4.1 Message Page(UF.SM)
• 6.4.1.1 Subfeatures to be tested
• 6.4.2 Test Cases
• 6.5.1 Send Message Page(UF.SM)
• 6.5.1 Subfeatures to be tested
• 6.5.2 Test Cases
• 6.6.1 List Message (UF.SM)
• 6.6.2 Test Cases
• 6.7.1 Send Feedback Message (UF.SFB)
• 6.7.2 Test Cases
• 6.8.1 List Feedback Message (UF.LFB)
• 6.8.2 Test Cases
• 6.9.1 List News Page (UF.LN)
• 6.9.2 Test Cases
• 7.Detailed Test Cases
• 7.1UT.US.01
• 7.2UT.US.02
• 7.3LP.LG.01
• 7.4LP.LG.02
• 7.5 LP.LG.03
• 7.6 UF.UFP.01
• 7.7 UF.SM.01
• 7.8UF.LM.01
• 7.9 UF.SFB.01
• 7.10UF.LFB.01
• 7.11 UF.LN.01

1.INTRODUCTION

1.1 Version Control

1.2 Overview

In this document, the purpose is to test the functions of the Mobile School Management System according to the SRS and SDD files that were uploaded in the past.

1.3 Scope

This test document has cases for User Type Choice, Login, User Home Functions Page. Each of these functions will be tested in this document.

1.4 Terminology

2.FEATURES TO BE TESTED

2.1 User Type (UT)

This feature allows you to select the user type before logging in to the system.

2.2 Login (LG)

This feature is used by the “admin” or “user” types of users in order to enter the platform to use further features of the system.

2.3 User Functions (UF)

In this feature, the functions that the user types have will be tested.

3. FEATURES NOT TO BE TESTED

The inputs and outputs of data such as grade, absenteeism and period of users in the system will not be tested because these data will be taken directly from the system of the school affiliated to the ministry.

4.ITEM PASS/FAIL CRITERIA

If an item is functioning the way it is described in SRS and SDD, then the item passes the test case; else the item fails. There might be some further time or performance constraints for certain items which are going to be explained further.

4.1 Exit Criteria

If all the High and Medium priority cases are passed the product is considered to be successful.

5. References

1. SRS
2. SDD

6.TEST DESIGN SPECIFICATIONS

6.1 User Type (UT)

6.1.1 Subfeatures to be tested

6.1.1.1 User(UT.US)

The user selects the user type from the application.

6.1.2 Test Cases

6.2 Login Page (LP)

6.2.1 Subfeatures to be tested

6.2.1.1 Login(LP.LG)

This page has email and password testing and then next to the user function the main page.

6.2.2 Test Cases

6.3 User Function (UF)

6.3.1 Subfeatures to be tested

6.3.1.1 User Functions Page(UF.UFP)

This page has a user’s function and every function is a specific function of the user’s type.

6.3.2 Test Cases

6.4.1 Message Page(UF.SM)

6.4.1.1 Subfeatures to be tested

This page is for sending and listing messages

6.4.2 Test Cases

6.5.1 SendMessage Page(UF.SM)

6.5.1.1 Subfeatures to be tested

This page sends a message to the user-selected receiver

6.5.2 Test Cases

6.6.1 ListMessage Page(UF.SM)

This page lists the users own messages

6.6.2 Test Cases

6.7.1 SendFeedBackPage(UF.SFB)

This page is for sending feedback to the selected user

6.7.2 Test Cases

6.8.1 ListFeedBack Page(UF.LFB)

This page lists the users own feedbacks

6.8.2 Test Cases

6.9.1 ListNews Page(UF.LN)

This page is for all users. It lists all of the school's news

6.9.2 Test Cases

7. Detailed Test Cases

7.1 UT.US.01

7.2 UT.US.02

7.3 LP.LG.01

7.4 LP.LG.02

7.5 LP.LG.03

7.6 UF.UFP.01

7.7 UF.SM.01

7.8 UF.LM.01

7.9 UF.SFB.01

7.10 UF.LFB.01

7.11 UF.LN.01