In this post we will see some high level Test cases for Products. When we write test cases for a product, we have certain requirements for hat product. A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements and works correctly.
Test cases help guide the tester through a sequence of steps to validate whether a software application is free of bugs, and working as required by the end user. A well-written test case should allow any tester to understand and execute the test.
Test cases for Products
Add products:
Serial No. | Condition To be Tested | Test Data | Expected Output | Remarks |
1 | If any field in the form is empty. | Value of form fields. | Alert the user to enter all the fields and then proceed. | SUCCESSFUL |
2 | If product name is emoty . | Prodname | Alert the user to enter the fields by displaying “Product Name should not be empty” | SUCCESSFUL |
3 | If category name fIeld is empty . | Cat_id | Alert the user to enter the fields by displaying “Category Name should not be empty” | SUCCESSFUL |
4 | If sub category is empty | Subcat_id | Alert the user to enter the fields by displaying “Sub Category Name should not be empty” | SUCCESSFUL |
5 | If Shop name is empty | Shop_id | Alert the user to enter the fields by displaying “Shop owner Name should not be empty” | SUCCESSFUL |
6 | If quantity contains only numeric values | qty | Alert user to enter only numeric values | SUCCESSFUL |
7 | If price contains only numeric values | Price | Alert user to enter only numeric values | SUCCESSFUL |
8 | If price contains only numeric values | Discount | Alert user to enter only numeric values | SUCCESSFUL |
9 | If warranty is empty | Warranty | Alert the user to enter the fields by displaying “Warranty should not be empty” | SUCCESSFUL |
10 | If stock status is empty | Stockstatus | Alert the user to enter the fields by displaying “Select stock status” | SUCCESSFUL |
11 | If Delivered In is empty | Deliveredin | Alert the user to enter the fields by displaying “delivered In should not be empty” | SUCCESSFUL |
12 | If Status is empty | Status | Alert the user to enter the fields by displaying “Select Status” | SUCCESSFUL |
category
Serial No. | Condition To be Tested | Test Data | Expected Output | Remarks |
1 | If any field in the form is empty. | Value of form fields. | Alert the user to enter all the fields and then proceed. | SUCCESSFUL |
2 | If category name fIeld is empty . | Cat_name | Alert the user to enter the fields by displaying “Category Name should not be empty” | SUCCESSFUL |
3 | If category description fIeld is empty . | Cat_des | Alert the user to enter the fields by displaying “Category description should not be empty” | SUCCESSFUL |
Sub category
Serial No. | Condition To be Tested | Test Data | Expected Output | Remarks |
1 | If any field in the form is empty. | Value of form fields. | Alert the user to enter all the fields and then proceed. | SUCCESSFUL |
2 | If main category is empty | Cat_name | Alert the user to enter the fields by displaying “Category Name should not be empty” | SUCCESSFUL |
3 | If sub category is empty | subcategory | Alert the user to enter the fields by displaying “Sub Category Name should not be empty” | SUCCESSFUL |
4 | If sub category description is empty | Description | Alert the user to enter the fields by displaying “Sub Category description should not be empty” | SUCCESSFUL |