Test Case Generation of E-Utility Service Provider Project
Test Case Generation of E-Utility Service Provider Project
Let us see the Test Case Generation of the E-Utility Service Provider Project. If you are interested to read the full SRS and documentation of the project, then click here.
Signup Test Case
The test case of signup as shown below. It refers to Use case 1 in the use cases. In this test case, successful registration of the user is being checked. This functionality is used to make registration to use this application.
Sign Up Test Case
| Test Engineer: | Name of the testing person |
| Test Case ID: | TC1 |
| Related UC/FR/NFR | UC1/FR1/NFR1 |
| Date: | 20 June 2013 |
| Purpose: | To check the successful signup. |
| Pre-Req: | The user has to start the application. |
| Assumptions: | User fills the forms successfully and data is stored in a database. |
| Steps:
Procedure Result:
| Steps to carry out the test. See step formatting rules below.
Application enables the user to fill all data and save in database |
| Status: | Pass |
Login Test Case
When the user wants to use this system, then he must log in first. This test case describes the process in which the user can use the application after login.
Login in the account is used for security purposes so that only authentic users can use this account and any unauthorized person cannot access someone’s account. If the user enters the correct details he/she successfully login or if he/she enters incorrect details then the user cannot continue.
Login Test Case
| Test Engineer: | Name of the testing person |
| Test Case ID: | TC2 |
| Related UC/FR/NFR | UC2/FR2/NFR2 |
| Date: | 20 June 2013 |
| Purpose: | To check that login is successful or not. The server is working properly or not. |
| Pre-Req: | The user has to start the application. |
| Assumptions: | Users will log in easily. |
| Steps:
Procedure Result: | Steps to carry out the test. See the step formatting rules below. The application should be in running condition. The system opens the user’s account. |
| Status: | Pass |
Checking Location Test Case
When the worker successfully received the request from the customer and the worker is going to complete the task then he can find the location of the customer through Google map. It can give location from the worker place to the customer place.
Checking Location Test case
| Test Engineer: | Name of the testing person |
| Test Case ID: | TC3 |
| Related UC/FR/NFR | UC3/FR3/NFR3 |
| Date: | 20 June 2017 |
| Purpose: | To Check that worker can get the customers location or not. |
| Pre-Req: | The user has to start the application. |
| Steps:
Procedure Result: | Steps to carry out the test. See the step formatting rules below.
The application should be in running condition. The worker must search for the location of customer The worker can get the customer’s location through Google map. |
| Status: | Pass |
Visitor Test Case
This test case is to check that when visitors come on the main page of the application this page is working properly and the services are shown to the visitor.
Visitor Test case
| Test Engineer: | Name of the testing person |
| Test Case ID: | TC4 |
| Related UC/FR/NFR | UC4/FR4/NFR4 |
| Date: | 15 June 2013 |
| Purpose: | Check that visitors can view the services or not. |
| Pre-Req: | The user has to start the application. |
| Steps:
Procedure Result: | Steps to carry out the test. See the step formatting rules below. The application should be in running condition. Services are shown to the visitor. |
| Status: | Pass |
Service Provider login case
This case is to check that the service provider/worker is successfully login in or not and view the requests of the customer or not.
Service Provider Login Case
| Test Engineer: | Name of testing person |
| Test Case ID: | TC5 |
| Related UC/FR/NFR | UC5/FR5/NFR5 |
| Date: | 30 June 2013 |
| Purpose: | To Check that the worker can successfully login and view requests or not. |
| Pre-Req: | Worker must have signed up to login. |
| Steps:
Procedure Result: | Steps to carry out the test. See step formatting rules below. The application should be in running condition. Worker click the login button. Worker can select the view requests to see the requests of customers. Worker successfully log in and see the requests of customers. |
| Status: | Pass |
If you are interested to read the full SRS and documentation of the project, then click here.