Here are some test cases based on the provided documentation:
Test Case 1: Document Upload and Storage
1. Preconditions:
- A user uploads a document in DealPro or Netbanking system.
2. Steps:
- Verify if the document is stored in Hitachi.
- Check if the document can be retrieved from Hitachi.
3. Expected Results:
- The document is stored in Hitachi.
- The document can be retrieved from Hitachi.
Test Case 2: Document Viewing
1. Preconditions:
- A document is uploaded and stored in Hitachi.
- A user with authorized access (Branch authorizer or CPUT authorizer) attempts
to view the document.
2. Steps:
- Verify if the user can view the document.
- Check if the document is displayed correctly.
3. Expected Results:
- The user can view the document.
- The document is displayed correctly.
Test Case 3: Document Viewing via Transaction Grid
1. Preconditions:
- A document is uploaded and stored in Hitachi.
- A user with authorized access (Branch authorizer or CPUT authorizer) attempts
to view the document via the transaction grid (Inward and Retail FX (Broker firm
transactions) page).
2. Steps:
- Verify if the user can view the document via the transaction grid.
- Check if the document is displayed correctly.
3. Expected Results:
- The user can view the document via the transaction grid.
- The document is displayed correctly.
Test Case 4: Document ID and Code Validation
1. Preconditions:
- A user attempts to view a document without providing the correct document ID
and code.
2. Steps:
- Verify if the system prevents the user from viewing the document.
- Check if an error message is displayed.
3. Expected Results:
- The system prevents the user from viewing the document.
- An error message is displayed indicating that the document ID and code are
invalid.
Test Case 5: Web Service Integration
1. Preconditions:
- The new web service is integrated with Hitachi.
2. Steps:
- Verify if the web service can send and retrieve documents from Hitachi.
- Check if the web service is functioning correctly.
3. Expected Results:
- The web service can send and retrieve documents from Hitachi.
- The web service is functioning correctly.
Test Case 6: Error Handling
1. Preconditions:
- An error occurs during the document upload, storage, or viewing process.
2. Steps:
- Verify if the error is handled correctly.
- Check if an error message is displayed.
3. Expected Results:
- The error is handled correctly.
- An error message is displayed indicating the cause of the error.
Test Case 7: Security and Access Control
1. Preconditions:
- A user without authorized access attempts to view a document.
2. Steps:
- Verify if the system prevents the user from viewing the document.
- Check if an error message is displayed.
3. Expected Results:
- The system prevents the user from viewing the document.
- An error message is displayed indicating that the user does not have
authorized access.
On Fri, 21 Mar, 2025, 11:33 Vaibhav Shinde, <[email protected]> wrote:
Here are some test cases based on the provided documentation:
Test Case 1: TCS Applicability Threshold
1. Preconditions:
- A numeric value is maintained in the parameter for TCS applicability.
2. Steps:
- Verify if the TCS applicability threshold is correctly set based on the
maintained value.
- Check if TCS charges are applicable when the summation of total foreign
outward remittances exceeds the threshold amount.
3. Expected Results:
- The TCS applicability threshold is correctly set based on the maintained
value.
- TCS charges are applicable when the summation of total foreign outward
remittances exceeds the threshold amount.
Test Case 2: TCS Rate for Education Loans
1. Preconditions:
- A new parameter is created to maintain the TCS rate for Education purpose
code where Source of funds is Loan from registered financial institutions.
2. Steps:
- Verify if the TCS rate is correctly maintained in the parameter.
- Check if the TCS rate is applied correctly for Education Loans from
registered financial institutions.
3. Expected Results:
- The TCS rate is correctly maintained in the parameter.
- The TCS rate is applied correctly for Education Loans from registered
financial institutions.
Test Case 3: Navigation to Transaction Parameter
1. Preconditions:
- The user navigates to General Master → Parameter → Transaction Parameter.
2. Steps:
- Verify if the user can access the Transaction Parameter screen.
- Check if the TCS applicability threshold and TCS rate for Education Loans are
correctly displayed.
3. Expected Results:
- The user can access the Transaction Parameter screen.
- The TCS applicability threshold and TCS rate for Education Loans are
correctly displayed.
Test Case 4: Invalid TCS Applicability Threshold
1. Preconditions:
- An invalid value (e.g. non-numeric, negative) is maintained in the parameter
for TCS applicability.
2. Steps:
- Verify if the system prevents the invalid value from being saved.
- Check if an error message is displayed.
3. Expected Results:
- The system prevents the invalid value from being saved.
- An error message is displayed indicating that the value is invalid.
Test Case 5: TCS Rate Not Maintained
1. Preconditions:
- The TCS rate for Education Loans is not maintained in the parameter.
2. Steps:
- Verify if the system applies a default TCS rate or prevents the transaction
from being processed.
- Check if an error message is displayed.
3. Expected Results:
- The system applies a default TCS rate or prevents the transaction from being
processed.
- An error message is displayed indicating that the TCS rate is not maintained.
Test Case 6: Multiple TCS Rates
1. Preconditions:
- Multiple TCS rates are maintained in the parameter for different Education
purpose codes.
2. Steps:
- Verify if the system applies the correct TCS rate for each Education purpose
code.
- Check if the TCS rates are correctly displayed.
3. Expected Results:
- The system applies the correct TCS rate for each Education purpose code.
- The TCS rates are correctly displayed.
