TEST TYPE: dashboard_functional

TC_FUNC_01_Verify_Annual_Invoices_Price_IDs
Scenario: To ensure all legacy annual invoices with 1 x quantity have their price IDs uploaded to the DB.
Steps to reproduce:
1. Access the dashboard and navigate to the legacy annual invoices section.
2. Identify invoices created with 1 x quantity.
3. Check if the price IDs are missing for these specific invoices.
Expected Result: Price IDs for legacy annual invoices with 1 x quantity are uploaded to the DB.
Actual Result: 
Priority: High

TC_FUNC_02_Ensure_Price_IDs_Upload_Operation
Scenario: Testing the functionality of uploading price IDs to the DB.
Steps to reproduce:
1. Access the dashboard and locate the option to upload price IDs.
2. Select a sample set of prices with IDs to upload.
3. Initiate the upload operation.
Expected Result: Price IDs are successfully uploaded to the DB without errors.
Actual Result: 
Priority: High

TC_FUNC_03_Verify_Price_IDs_Availability
Scenario: Confirming that all uploaded price IDs are available in the DB.
Steps to reproduce:
1. Navigate to the DB backend and search for the uploaded price IDs.
2. Verify that the uploaded price IDs are listed and accessible.
Expected Result: All uploaded price IDs are available and stored correctly in the DB.
Actual Result: 
Priority: High

TC_FUNC_04_Check_Price_IDs_Validation
Scenario: Testing the system's validation of price IDs during upload.
Steps to reproduce:
1. Attempt to upload price IDs with incorrect formats or missing information.
2. Observe the system's response to the invalid price IDs.
Expected Result: System should reject invalid price IDs and provide appropriate error messages.
Actual Result: 
Priority: Medium

TC_FUNC_05_Verify_Price_IDs_Mapping
Scenario: Ensuring that each price ID is correctly mapped to the corresponding invoice.
Steps to reproduce:
1. Review the mapping between price IDs and invoices in the DB.
2. Cross-reference the data to confirm accurate mapping.
Expected Result: Each price ID is correctly associated with the respective invoice in the DB.
Actual Result: 
Priority: High

TC_FUNC_06_Test_Price_IDs_Unique_Constraints
Scenario: Checking the enforcement of unique constraints on price IDs in the DB.
Steps to reproduce:
1. Attempt to upload duplicate price IDs for different invoices.
2. Verify the system's response to duplicate entries.
Expected Result: System should prevent the insertion of duplicate price IDs and maintain uniqueness.
Actual Result: 
Priority: High

TC_FUNC_07_Validate_Price_IDs_Display
Scenario: Verifying that uploaded price IDs are displayed correctly on the dashboard.
Steps to reproduce:
1. Navigate to the dashboard interface where price IDs are displayed.
2. Check for the presence and accuracy of the uploaded price IDs.
Expected Result: Uploaded price IDs are displayed accurately on the dashboard.
Actual Result: 
Priority: High

TC_FUNC_08_Test_Price_IDs_Retrieval
Scenario: Testing the retrieval of price IDs from the DB.
Steps to reproduce:
1. Query the DB to retrieve a specific price ID.
2. Verify that the retrieved price ID matches the expected value.
Expected Result: Price ID is successfully retrieved from the DB as per the query.
Actual Result: 
Priority: High

TC_FUNC_09_Check_Price_IDs_Deletion
Scenario: Validating the deletion of price IDs from the DB.
Steps to reproduce:
1. Select a price ID for deletion from the DB.
2. Initiate the deletion process.
Expected Result: Selected price ID is removed from the DB without affecting other data.
Actual Result: 
Priority: High

TC_FUNC_10_Test_Price_IDs_Update
Scenario: Testing the functionality to update existing price IDs in the DB.
Steps to reproduce:
1. Choose a price ID to update.
2. Modify the price ID value and save the changes.
Expected Result: Updated price ID is reflected in the DB.
Actual Result: 
Priority: High

TC_FUNC_11_Verify_Price_IDs_Audit_Trail
Scenario: Checking if changes to price IDs are logged in the audit trail.
Steps to reproduce:
1. Update a price ID in the DB.
2. Review the audit trail records for the change event.
Expected Result: Audit trail should document the modification of price IDs.
Actual Result: 
Priority: High

TC_FUNC_12_Test_Price_IDs_Range_Limit
Scenario: Testing the system's handling of a large number of price IDs.
Steps to reproduce:
1. Attempt to upload a significant quantity of price IDs at once.
2. Monitor system performance during the bulk upload operation.
Expected Result: System should handle a large volume of price IDs efficiently without errors.
Actual Result: 
Priority: Medium

TC_FUNC_13_Ensure_Price_IDs_Data_Integrity
Scenario: Verifying the integrity of price ID data stored in the DB.
Steps to reproduce:
1. Validate the consistency of price IDs with their corresponding invoices.
2. Check for any discrepancies or missing associations.
Expected Result: Price ID data in the DB maintains integrity with accurate associations.
Actual Result: 
Priority: High

TC_FUNC_14_Check_Price_IDs_Search_Functionality
Scenario: Testing the search feature for locating specific price IDs on the dashboard.
Steps to reproduce:
1. Utilize the search function to find a particular price ID.
2. Confirm that the search results display the relevant price ID.
Expected Result: Search function should accurately retrieve the specified price ID.
Actual Result: 
Priority: High

TC_FUNC_15_Verify_Price_IDs_Permissions
Scenario: Validating that only authorized users can access and modify price IDs.
Steps to reproduce:
1. Attempt to access price ID data with a non-privileged account.
2. Try to make changes to price IDs without proper permissions.
Expected Result: System should restrict unauthorized access and modifications to price IDs.
Actual Result: 
Priority: High

TC_FUNC_16_Test_Price_IDs_Data_Encryption
Scenario: Ensuring that price ID data is encrypted when stored in the DB.
Steps to reproduce:
1. Inspect the DB to confirm that price IDs are stored in encrypted form.
2. Verify the encryption mechanism used to protect sensitive data.
Expected Result: Price ID data should be securely encrypted in the DB.
Actual Result: 
Priority: High

TC_FUNC_17_Check_Price_IDs_Expiration
Scenario: Testing the expiration mechanism for outdated price IDs in the DB.
Steps to reproduce:
1. Identify expired price IDs based on a set expiration date.
2. Verify that expired price IDs are no longer valid or accessible.
Expected Result: Expired price IDs should be automatically deactivated or removed from the system.
Actual Result: 
Priority: High

TC_FUNC_18_Verify_Price_IDs_Retention_Policy
Scenario: Confirming the implementation of a retention policy for preserving price ID data.
Steps to reproduce:
1. Review the retention settings governing the storage duration of price IDs.
2. Ensure that data retention policies are enforced as per the configured rules.
Expected Result: Price ID data should adhere to the defined retention policy for proper data management.
Actual Result: 
Priority: High

TC_FUNC_19_Test_Price_IDs_Restore_Functionality
Scenario: Testing the capability to restore deleted price IDs from a backup.
Steps to reproduce:
1. Delete a price ID from the DB.
2. Attempt to restore the deleted price ID using the backup feature.
Expected Result: System should successfully restore the deleted price ID from the backup.
Actual Result: 
Priority: High

TC_FUNC_20_Ensure_Price_IDs_Backup_Process
Scenario: Validating the backup process for price ID data in the DB.
Steps to reproduce:
1. Trigger a backup of price ID data in the system.
2. Verify that the backup file contains the necessary information for recovery.
Expected Result: Backup process should create a complete and reliable copy of price ID data for restoration purposes.
Actual Result: 
Priority: High



TEST TYPE: dashboard_negative

Title: TC_NEG_01_Missing_Price_ID_Error_Message
Scenario: Verify that an error message is displayed when trying to access a dashboard with missing price IDs.
Steps to reproduce:
1. Navigate to the dashboard with missing price IDs.
2. Observe the error message displayed.
Expected Result: An error message should be shown indicating the issue with missing price IDs.
Actual Result: 
Priority: High

Title: TC_NEG_02_Invalid_Input_Price_ID
Scenario: Test entering an invalid price ID in the dashboard field.
Steps to reproduce:
1. Enter an invalid price ID in the dashboard field.
2. Attempt to save the changes.
Expected Result: The system should reject the invalid price ID and provide an error message.
Actual Result: 
Priority: High

Title: TC_NEG_03_Empty_Price_ID
Scenario: Validate behavior when leaving the price ID field empty.
Steps to reproduce:
1. Leave the price ID field empty.
2. Try to proceed with the operation.
Expected Result: The system should not allow leaving the price ID field empty and prompt for a valid input.
Actual Result: 
Priority: Medium

Title: TC_NEG_04_Nonexistent_Price_ID
Scenario: Check system response when entering a price ID that does not exist in the database.
Steps to reproduce:
1. Enter a non-existent price ID.
2. Submit the request.
Expected Result: The system should notify that the entered price ID does not exist.
Actual Result: 
Priority: High

Title: TC_NEG_05_Invalid_Quantity
Scenario: Test entering an invalid quantity for the price ID.
Steps to reproduce:
1. Enter a negative or zero quantity for the price ID.
2. Save the changes.
Expected Result: The system should reject the invalid quantity input and provide an error message.
Actual Result: 
Priority: High

Title: TC_NEG_06_Missing_Data_Connection
Scenario: Validate system behavior when there is a missing data connection for price IDs.
Steps to reproduce:
1. Disconnect the data connection for price IDs.
2. Access the dashboard.
Expected Result: The system should display an error message indicating the missing data connection.
Actual Result: 
Priority: High

Title: TC_NEG_07_Duplicate_Price_ID
Scenario: Test adding a duplicate price ID to the dashboard.
Steps to reproduce:
1. Add a price ID that already exists in the dashboard.
2. Save the changes.
Expected Result: The system should prevent adding duplicate price IDs and show an error message.
Actual Result: 
Priority: High

Title: TC_NEG_08_SQL_Injection_Price_ID
Scenario: Attempt to perform an SQL injection using the price ID field.
Steps to reproduce:
1. Enter a malicious SQL query into the price ID field.
2. Submit the input.
Expected Result: The system should detect and prevent SQL injection attempts.
Actual Result: 
Priority: High

Title: TC_NEG_09_Invalid_Character_Price_ID
Scenario: Test entering special characters in the price ID field.
Steps to reproduce:
1. Enter special characters like !@#$%^&*() into the price ID field.
2. Try to save the changes.
Expected Result: The system should reject special characters and display an error message.
Actual Result: 
Priority: High

Title: TC_NEG_10_Expired_Price_ID
Scenario: Verify system response when using an expired price ID.
Steps to reproduce:
1. Enter an expired price ID.
2. Try to access the corresponding data.
Expected Result: The system should indicate that the price ID has expired.
Actual Result: 
Priority: High

Title: TC_NEG_11_Price_ID_Format_Invalid
Scenario: Validate system behavior with an incorrectly formatted price ID.
Steps to reproduce:
1. Enter a price ID with an incorrect format (e.g., missing digits).
2. Attempt to save the changes.
Expected Result: The system should reject the incorrectly formatted price ID and notify the user.
Actual Result: 
Priority: Medium

Title: TC_NEG_12_Quantity_Overflow
Scenario: Test entering a quantity value that exceeds the system limit.
Steps to reproduce:
1. Enter a very large quantity value for the price ID.
2. Save the changes.
Expected Result: The system should handle the quantity overflow gracefully and provide an error message.
Actual Result: 
Priority: High

Title: TC_NEG_13_Unauthorized_Access_Price_ID
Scenario: Verify system behavior when trying to access a price ID without proper authorization.
Steps to reproduce:
1. Access a price ID without the necessary permissions.
2. Observe the system response.
Expected Result: The system should deny access and display an authorization error message.
Actual Result: 
Priority: High

Title: TC_NEG_14_Price_ID_Deleted
Scenario: Test accessing a dashboard with a price ID that has been deleted.
Steps to reproduce:
1. Use a deleted price ID to access the dashboard.
2. Check the system response.
Expected Result: The system should indicate that the price ID has been deleted.
Actual Result: 
Priority: High

Title: TC_NEG_15_Null_Price_ID
Scenario: Validate system behavior when entering a null value for the price ID.
Steps to reproduce:
1. Enter a null value in the price ID field.
2. Try to save the changes.
Expected Result: The system should not accept null values for the price ID field.
Actual Result: 
Priority: Medium

Title: TC_NEG_16_Incomplete_Price_ID
Scenario: Test entering an incomplete price ID (missing digits) in the field.
Steps to reproduce:
1. Enter a price ID with missing digits.
2. Save the changes.
Expected Result: The system should reject incomplete price IDs and prompt for a complete input.
Actual Result: 
Priority: High

Title: TC_NEG_17_Corrupted_Data_Price_ID
Scenario: Validate system response when encountering corrupted data for a price ID.
Steps to reproduce:
1. Introduce corrupted data for a price ID.
2. Access the dashboard.
Expected Result: The system should detect and handle corrupted data appropriately.
Actual Result: 
Priority: High

Title: TC_NEG_18_Maximum_Length_Exceeded_Price_ID
Scenario: Test entering a price ID that exceeds the maximum allowed length.
Steps to reproduce:
1. Enter a price ID with more characters than the allowed limit.
2. Try to save the changes.
Expected Result: The system should restrict the length of the price ID and notify the user.
Actual Result: 
Priority: High

Title: TC_NEG_19_Invalid_Price_ID_Type
Scenario: Verify system response when entering a price ID of an invalid data type.
Steps to reproduce:
1. Enter a price ID with an invalid data type (e.g., text instead of numeric).
2. Save the changes.
Expected Result: The system should reject price IDs with invalid data types and show an error message.
Actual Result: 
Priority: High

Title: TC_NEG_20_Price_ID_Correlation_Error
Scenario: Test the behavior when there is a correlation error between price IDs.
Steps to reproduce:
1. Introduce a correlation error between two price IDs.
2. Check the impact on the dashboard data.
Expected Result: The system should handle correlation errors between price IDs and provide appropriate feedback.
Actual Result: 
Priority: High