Test Cases of Store Management System Project (Testing)
The test case generation of Store Management System Project is today’s topic of discussion in this post.
If you want to read the SRS and full documentation of this project, then
click here.
Login
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
1 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
02-01-2014 |
| Purpose: |
The purpose of this test insure that the user can log in with his id to use this app. |
| Pre-Req: |
The user enters his correct name and password for a successful login page. |
| Test Data: |
sname, sid, spassword |
| Steps: |
The steps are below.
- visit Login Page
- enter UserId
- enter password
- click login
- recovery password
- change password
- keep login
|
| Status: |
Pass |
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
2 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
03-01-2014 |
| Purpose: |
The purpose of this test is to make sure that the design of the front page of the app is consistent and readable. |
| Pre-Req: |
The main activity of the app should be up and running. |
| Test Data: |
none (test is just visual test) |
| Steps: |
Following steps will take place in the test
- Latest orders
- Top customers
- Recent products
- Recent customers
- Graph by amount and order
- Graph by day/month/year
|
| Status: |
Pass |
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
3 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
03-01-2014 |
| Purpose: |
The purpose of this test for registered employ by his name, password, email, and mobile number for use this app and work on the app. |
| Pre-Req: |
Employ sure that login with his name and id to use this app. |
| Test Data: |
none (test is just visual test) |
| Steps: |
Step formatting rules below.
- enter employ name
- enter employ password
- enter employ email
- enter employ a mobile number
|
| Status: |
Pass |
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
4 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
04-01-2014 |
| Purpose: |
The purpose of this testing to insert, update, delete and view category. |
| Pre-Req: |
The user enter category by its correct name. |
| Test Data: |
Txtcatogaryname |
| Steps: |
Step formatting rules below.
- open the category form
- insert the category name of items
- update the category name of items
- delete the category name of items
- insert the category name of items
- view the category names
- Export the category records to MS Excel.
|
| Status: |
Pass |
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
5 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
05-01-2014 |
| Purpose: |
The purpose of this testing to registered the new customer by his name, address, id number and phone number for sales items. |
| Pre-Req: |
The user can easily search customer by name with all data. |
| Test Data: |
Scustmrname, scsutmradress, scustmrmblnumer, scustmremail |
| Steps: |
Step formatting rules below.
1. automatically generate customer-id
2. enter the customer name
3. enter customer address
4. enter customer id number
5. enter customer city
6. enter customer mobile number
7. enter customer email |
| Status: |
Pass |
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
6 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
05-01-2014 |
| Purpose: |
The purpose of this testing to enter item code, name and price and also can modify name and price of items. |
| Pre-Req: |
Employ can search items by name and code. |
| Test Data: |
none (test is just visual test) |
| Steps: |
Step formatting rules below.
- insert items code
- insert items name with price
- update items name or price
- delete items name
|
| Status: |
Pass |
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
7 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
05-01-2014 |
| Purpose: |
The purpose of this testing to sales items with discount and print invoice of sales. |
| Pre-Req: |
The user can check records for recent or old sales by report or data. |
| Test Data: |
none (test is just visual test)
|
| Steps: |
Step formatting rules below.
- sales items with quantity
- discount to customer
- payment due
- print crystal report of sales
- print excel report of sales
|
| Status: |
Pass |
| Test Engineer: |
Here, you can mention the Name of the test engineer |
| Test Case ID: |
8 |
| Related UC/FR/NFR |
UC/FR/NFR |
| Date: |
05-09-2014 |
| Purpose: |
The purpose of this test for check quantities of items in which user can modify items day by day. |
| Pre-Req: |
The user can see the quantities are below in the range or above in the range. |
| Test Data: |
None |
| Steps: |
Step formatting rules below.
- set the quantities of items
- update the quantities of items
- delete the quantities of items
- if quantities less than 200 than message show with yellow color
- if quantities equal to zero than message show with red color
|
| Status: |
Pass |
If you want to read the SRS and full documentation of this project, then
click here.
