Welcome to the Carnesia Manual Testing repository. This document outlines the manual testing procedures, test cases, and guidelines for testing the Carnesia project. Manual testing plays a crucial role in ensuring the quality, functionality, and usability of the application.
Before you begin manual testing for Carnesia, make sure you have the following prerequisites in place:
- Access to the Carnesia application in the testing environment (either staging or development).
- Familiarity with the application's features and functionalities.
- Test data, including valid user accounts, products, and necessary test scenarios.
The test cases are organized into categories based on the application's functionalities. Each test case should include the following details:
- Test ID: A unique identifier for the test case.
- Test Name: A brief, descriptive name of the test case.
- Test Description: A detailed description of the test scenario.
- Steps to Reproduce: Step-by-step instructions to execute the test.
- Expected Results: The expected outcome or behavior of the application.
- Actual Results: The actual outcome or behavior observed during testing.
- Status: The status of the test case (e.g., Pass/Fail).
For your convenience, we have provided a sample structure for test cases in the test cases tab.
To execute the manual test cases for Carnesia, follow these general steps:
- Log in to the testing environment using valid test user credentials.
- Navigate to the specific feature or functionality you intend to test.
- Follow the steps outlined in the test case to reproduce the scenario.
- Observe and record the actual results.
- Compare the actual results with the expected results.
- Update the status of the test case in the test case document.
If you encounter any issues or defects during testing, please report them promptly. To report a bug, follow these steps:
- Provide a detailed description of the issue, including steps to reproduce.
- Attach relevant screenshots or additional documentation, if applicable.
- Assign the issue to the responsible team member.
- Use appropriate labels and priorities to categorize the issue.
To provide a clear overview of the testing progress, we maintain a test matrix that displays the status of test cases across various categories and functionalities. The test matrix is regularly updated to ensure transparency in our testing efforts.
The test case report should be regularly updated in the test case report tab, which should indicate the status of each test case. Any failed test cases should be documented with detailed information about the failure.
