From d16f847d9643474d0c8e1db686cecf30963398a2 Mon Sep 17 00:00:00 2001 From: ZB-io Date: Tue, 19 Mar 2024 06:37:19 +0000 Subject: [PATCH] Functional test generated by RoostGPT Using AI Model gpt-4 --- functional_tests/ZBIO-5139.feature | 18 ++++++++ functional_tests/ZBIO-5139.txt | 67 ++++++++++++++++++++++++++++++ 2 files changed, 85 insertions(+) create mode 100644 functional_tests/ZBIO-5139.feature create mode 100644 functional_tests/ZBIO-5139.txt diff --git a/functional_tests/ZBIO-5139.feature b/functional_tests/ZBIO-5139.feature new file mode 100644 index 0000000..fea3daf --- /dev/null +++ b/functional_tests/ZBIO-5139.feature @@ -0,0 +1,18 @@ +Feature: Credit Card Application API Interaction + Scenario: Submitting a valid credit card application + Given the API base URL 'http://localhost:3000' + When I send a POST request to '/credit-card-application' with valid identification, income details, and contact information + Then the response status should be 200 + And the response should contain 'The application is successfully submitted.' + + Scenario: Attempting to submit an invalid credit card application + Given the API base URL 'http://localhost:3000' + When I send a POST request to '/credit-card-application' with invalid or incomplete information + Then the response status should be 400 + And the response should contain 'Appropriate error message' + + Scenario: Receiving a confirmation message after successful application + Given the API base URL 'http://localhost:3000' + When I send a GET request to '/credit-card-application/confirmation' + Then the response status should be 200 + And the response should contain 'Confirmation message' diff --git a/functional_tests/ZBIO-5139.txt b/functional_tests/ZBIO-5139.txt new file mode 100644 index 0000000..2eaa2c9 --- /dev/null +++ b/functional_tests/ZBIO-5139.txt @@ -0,0 +1,67 @@ +FUNCTIONAL TEST CASE: +Functional Test cases: + +1. Credit Card Application: + - A customer should be able to access the credit card application online or at a bank branch. + Input: Enter valid identification, income details, and contact information + Expected Output: The application is successfully submitted. + Edge Case: When invalid or incomplete information is entered, an appropriate error message is displayed. + + - Verify that the customer receives a confirmation message after successfully submitting the application. + Input: A completed credit card application. + Expected Output: Confirmation message is presented to the customer. + +2. Waiving Off Charges: + - The customer should be able to report an unexpected fee via their online account or over the phone. + Input: Customer reports an unexpected fee. + Expected Output: Fee report is successfully submitted. + Edge Case: If customer attempts to submit a duplicate fee report, an appropriate error message should occur. + + - Verify the bank is able to review the customer's history and consider waiving off the charges. + Input: Bank reviews customer history. + Expected Output: Decision to waive off charges is made based on review. + +3. Redeeming Points: + - The customer should be able to redeem their reward points for various benefits. + Input: Customer selects reward of choice to redeem. + Expected Output: Reward is successfully redeemed. + Edge Case: If points are insufficient for reward, an error message is displayed. + +4. Credit Limit Extension: + - The customer receives a notification once their credit limit has been increased. + Input: Bank decides to increase customer's credit limit. + Expected Output: Customer receives notification of credit limit increase. + +5. Credit Limit Reduction: + - The customer receives a notification once their credit limit has been decreased. + Input: Bank decides to decrease customer's credit limit. + Expected Output: Customer receives notification of credit limit decrease. + +6. Promotional Balance Transfers: + - The customer should be able to transfer high-interest balances from other credit cards. + Input: Customer initiates a balance transfer. + Expected Output: Balance transfer is successful. + + +Non-Functional Test cases: + +1. Usability: + - The credit card application form should be user-friendly with clear instructions. + +2. Performance: + - The customer's online account should load within an acceptable timeframe. + +3. Security: + - The customer's sensitive information should be encrypted and secure from unauthorized access. + +4. Compatibility: + - The online banking portal should be compatible across different browsers and mobile devices. + +5. Availability: + - The online banking portal should be available 24/7 for customers. + +6. Scalability: + - The system should be able to handle an increase in the number of credit card applications or customer accounts. + +7. Fault tolerance: + - The system should provide an error message and guide the user to recover and continue instead of crash abruptly when incorrect inputs are made.