diff --git a/functional_tests/README.md b/functional_tests/README.md new file mode 100644 index 00000000..a437e38f --- /dev/null +++ b/functional_tests/README.md @@ -0,0 +1,23 @@ +# Roost Generated Functional Test + +**Execution Date:** 1/11/2026, 1:54:12 PM + +**Test Unique Identifier:** "TCSBaNCS_functional-after-fix" + +**Input(s):** + 1. bankspromot.txt + Path: /var/tmp/Roost/RoostGPT/TCSBaNCS_functional-after-fix/d942e3e8-b2d8-4cf9-b7fc-6c51b6d530de/bankspromot.txt + 2. TCSBaNCS_ST_BSSB_FSD_CallCenterOperator_v14.2.docx + Path: /var/tmp/Roost/RoostGPT/TCSBaNCS_functional-after-fix/d942e3e8-b2d8-4cf9-b7fc-6c51b6d530de/TCSBaNCS_ST_BSSB_FSD_CallCenterOperator_v14.2.docx + 3. TCS BaNCS-Functional Specifications-Securities Back Office Processing-v1.8.1.docx + Path: /var/tmp/Roost/RoostGPT/TCSBaNCS_functional-after-fix/d942e3e8-b2d8-4cf9-b7fc-6c51b6d530de/TCS BaNCS-Functional Specifications-Securities Back Office Processing-v1.8.1.docx + +**Test Output Folder:** + 1. [TCSBaNCS_functional-after-fix.json](TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.json) + 2. [TCSBaNCS_functional-after-fix.feature](TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.feature) + 3. [TCSBaNCS_functional-after-fix.csv](TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.csv) + 4. [TCSBaNCS_functional-after-fix.xlsx](TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.xlsx) + 5. [TCSBaNCS_functional-after-fix.docx](TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.docx) + +--- + diff --git a/functional_tests/TCSBaNCS_functional-after-fix/.roost/roost_metadata.json b/functional_tests/TCSBaNCS_functional-after-fix/.roost/roost_metadata.json new file mode 100644 index 00000000..e289219f --- /dev/null +++ b/functional_tests/TCSBaNCS_functional-after-fix/.roost/roost_metadata.json @@ -0,0 +1,34 @@ +{ + "project": { + "name": "TCSBaNCS_functional-after-fix", + "created_at": "2026-01-11T13:54:12.963Z", + "updated_at": "2026-01-11T13:54:12.963Z" + }, + "files": { + "input_files": [ + { + "fileName": "TCSBaNCS_functional-after-fix.txt", + "fileURI": "/var/tmp/Roost/RoostGPT/TCSBaNCS_functional-after-fix/d942e3e8-b2d8-4cf9-b7fc-6c51b6d530de/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.txt", + "fileSha": "cf83e1357e" + }, + { + "fileName": "bankspromot.txt", + "fileURI": "/var/tmp/Roost/RoostGPT/TCSBaNCS_functional-after-fix/d942e3e8-b2d8-4cf9-b7fc-6c51b6d530de/functional_tests/TCSBaNCS_functional-after-fix/bankspromot.txt", + "fileSha": "0664b099ba" + }, + { + "fileName": "TCSBaNCS_ST_BSSB_FSD_CallCenterOperator_v14.2.docx", + "fileURI": "/var/tmp/Roost/RoostGPT/TCSBaNCS_functional-after-fix/d942e3e8-b2d8-4cf9-b7fc-6c51b6d530de/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_ST_BSSB_FSD_CallCenterOperator_v14.2.docx", + "fileSha": "55a242034e" + }, + { + "fileName": "TCS BaNCS-Functional Specifications-Securities Back Office Processing-v1.8.1.docx", + "fileURI": "/var/tmp/Roost/RoostGPT/TCSBaNCS_functional-after-fix/d942e3e8-b2d8-4cf9-b7fc-6c51b6d530de/functional_tests/TCSBaNCS_functional-after-fix/TCS BaNCS-Functional Specifications-Securities Back Office Processing-v1.8.1.docx", + "fileSha": "2cd5271236" + } + ] + }, + "api_files": { + "input_files": [] + } +} \ No newline at end of file diff --git a/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.csv b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.csv new file mode 100644 index 00000000..ffd99d5b --- /dev/null +++ b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.csv @@ -0,0 +1,9 @@ +Agent Login with MFA and Handling Lockout Scenarios +Customer Verification via KBA/OTP +Session Timeout and Auto-Logout +Audit Trail and Logging for Sensitive Actions +Error Handling for Data Integration with External Systems +Verify Order Placement and Execution for Equity Buy Orders +Real-Time Market Data Accuracy +Comprehensive Audit Trail for Transactions +Error Handling and Exception Management for Trading Operations \ No newline at end of file diff --git a/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.docx b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.docx new file mode 100644 index 00000000..75764589 Binary files /dev/null and b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.docx differ diff --git a/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.feature b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.feature new file mode 100644 index 00000000..4305cc28 --- /dev/null +++ b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.feature @@ -0,0 +1,103 @@ +Feature: Comprehensive System Testing for Trading and Security Operations + + # UI Test Scenarios + @ui + Scenario Outline: Agent Login with MFA and Handling Lockout Scenarios + Given I am on the login page + When I enter '' and '' + And I input the MFA code from the agent's MFA device + And I submit the login form + Then I should be directed to the dashboard + And I should see a message '' + + Examples: + | username | password | expected_message | + | agent1 | pass123 | "Successfully logged in" | + | agent2 | pass456 | "Account locked after multiple failed attempts" | + + @ui + Scenario Outline: Customer Verification via KBA/OTP + Given I am on the customer verification page + When I select the customer verification option + And the system sends '' to the customer + And the customer provides correct '' + Then the system should verify the customer and allow progression to sensitive account actions + + Examples: + | method | response | + | KBA | correct | + | OTP | correct | + + @ui + Scenario: Session Timeout and Auto-Logout + Given an agent is logged in and remains inactive + When the session timeout period elapses + Then the system should automatically log the agent out + And require re-authentication + + # API Test Scenarios + @api + Scenario Outline: Audit Trail and Logging for Sensitive Actions + Given the agent is authenticated and authorized to perform sensitive actions + When the agent performs a '' transaction + Then the system should log the action with details including agent ID, timestamp, and transaction type + + Examples: + | transaction_type | + | modifying customer info | + | deleting customer info | + + @api + Scenario: Error Handling for Data Integration with External Systems + Given external systems are configured to send data + When the system receives incorrect data formats + Then the system should log the error + And not process the incorrect data + + @api + Scenario Outline: Verify Order Placement and Execution for Equity Buy Orders + Given a user is authenticated and has sufficient balance + When the user places an order for '' with quantity '' and price '' + Then the order should be validated and executed + And the user should receive confirmation with order details + + Examples: + | equity | quantity | price | + | Equity A | 10 | 100 | + | Equity B | 5 | 200 | + + @api + Scenario Outline: Real-Time Market Data Accuracy + Given market data feeds from TASE and Bloomberg are active + When the user accesses the market data section + Then the displayed data for '' should be accurate and match the data from external sources + + Examples: + | security | + | Security X | + | Security Y | + + @api + Scenario Outline: Comprehensive Audit Trail for Transactions + Given a user performs various transactions on the platform + When the system logs each transaction + Then the audit logs should contain detailed information about each '' + + Examples: + | transaction_type | + | trade | + | transfer | + + @api + Scenario Outline: Error Handling and Exception Management for Trading Operations + Given the trading platform is operational + When various trading errors such as '' occur + Then the system should handle the errors gracefully + And provide clear error messages + And log the incidents appropriately + And ensure data integrity post-error + + Examples: + | error_type | + | network failure | + | data format error| diff --git a/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.json b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.json new file mode 100644 index 00000000..719e7629 --- /dev/null +++ b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.json @@ -0,0 +1 @@ +[{"type":"functional","title":"Agent Login and MFA Verification","description":"Test the agent's ability to log in with MFA and handle lockout scenarios.","testId":"TC-001","testDescription":"Agent attempts to log in to the Call Center system using multi-factor authentication.","prerequisites":"Agent has valid login credentials and access to MFA device.","stepsToPerform":"1. Navigate to the login page.\n2. Enter valid agent username and password.\n3. Input MFA code from the agent's MFA device.\n4. Submit the login form.","expectedResult":"Agent is successfully logged in and directed to the dashboard."},{"type":"functional","title":"Customer Verification via KBA/OTP","description":"Verify the system's ability to authenticate a customer using Knowledge-Based Authentication (KBA) or One-Time Password (OTP).","testId":"TC-002","testDescription":"Customer calls and requests access to sensitive account actions, triggering KBA/OTP.","prerequisites":"Customer account is set up for KBA/OTP.","stepsToPerform":"1. Agent selects customer verification option.\n2. System sends KBA questions or OTP to customer.\n3. Customer provides correct responses.\n4. Agent enters responses into the system.","expectedResult":"System successfully verifies customer and allows progression to sensitive account actions."},{"type":"functional","title":"Session Timeout and Auto-Logout","description":"Ensure the system properly logs out users after a period of inactivity.","testId":"TC-003","testDescription":"Agent logs in and remains inactive to test session timeout.","prerequisites":"Agent is logged into the system.","stepsToPerform":"1. Agent logs in and does not interact with the system for the duration of the session timeout period.\n2. Observe system behavior post-timeout.","expectedResult":"System automatically logs the agent out and requires re-authentication."},{"type":"functional","title":"Audit Trail and Logging for Sensitive Actions","description":"Validate that all sensitive actions are logged and an audit trail is maintained.","testId":"TC-004","testDescription":"Agent performs a sensitive action, and the system logs the event.","prerequisites":"Agent is authenticated and authorized to perform sensitive actions.","stepsToPerform":"1. Agent performs a sensitive transaction (e.g., modifying customer contact information).\n2. Check the system logs and audit trails for the record of this transaction.","expectedResult":"System logs the action with sufficient details including agent ID, timestamp, and nature of the transaction."},{"type":"functional","title":"Error Handling for Data Integration with External Systems","description":"Test how the system handles errors during data exchange with external systems like TASE and Bloomberg.","testId":"TC-005","testDescription":"Simulate an error scenario where the system receives incorrect data formats from an external system.","prerequisites":"External systems are configured to send data to the test environment.","stepsToPerform":"1. Trigger a data fetch from an external system with known incorrect data formats.\n2. Monitor system response and error logging.","expectedResult":"System identifies the error, logs it appropriately, and does not process the incorrect data."},{"type":"functional","title":"Verify Order Placement and Execution for Equity Buy Orders","description":"Test the complete lifecycle of an equity buy order from placement to execution including all validations and error handling.","testId":"TC-006","testDescription":"A user places a buy order for equities and the system processes this order through various validation checks before executing it on the trading platform.","prerequisites":"User is authenticated and has sufficient balance in their account. Market data is up-to-date.","stepsToPerform":"1. User logs into the trading platform.\n2. User navigates to the equity trading section.\n3. User selects an equity and enters the quantity and price.\n4. User submits the order.\n5. System validates the order against user balance and market conditions.\n6. Order is executed on the trading platform.","expectedResult":"Order is successfully placed, validated, and executed. User receives confirmation with order details."},{"type":"functional","title":"Validate Real-Time Data Accuracy for Market Watch","description":"Ensure the market watch feature displays real-time data accurately from TASE and Bloomberg.","testId":"TC-007","testDescription":"Verify that the market watch feature updates and displays real-time price and trade volume accurately.","prerequisites":"Market data feeds from TASE and Bloomberg are active.","stepsToPerform":"1. Open the market watch feature on the trading platform.\n2. Select multiple securities to monitor.\n3. Observe the data updates for each selected security over a period.\n4. Compare the displayed data with actual data from TASE and Bloomberg.","expectedResult":"All selected securities in the market watch should display real-time data accurately matching the data from TASE and Bloomberg."},{"type":"functional","title":"Test Security Transfer Between Accounts Within the Same Bank","description":"Verify the process of transferring securities between customer accounts within the same bank.","testId":"TC-008","testDescription":"A user initiates a transfer of securities to another account within the same bank and the system processes this transfer correctly.","prerequisites":"Both sender and receiver accounts are active and have the necessary securities for the transfer.","stepsToPerform":"1. User logs into their account.\n2. Navigates to the security transfer section.\n3. Enters the details of the receiving account and the securities to transfer.\n4. Submits the transfer request.\n5. System validates the transfer details and processes the transfer.","expectedResult":"Securities are transferred successfully from one account to another within the same bank without any errors."},{"type":"functional","title":"Comprehensive Testing of Error Handling During Order Placement","description":"Test the system's response to various error conditions during order placement.","testId":"TC-009","testDescription":"Simulate different error scenarios during the order placement process and verify that the system handles these appropriately.","prerequisites":"User is logged into the trading platform.","stepsToPerform":"1. Attempt to place an order with insufficient funds.\n2. Try placing an order for a halted security.\n3. Place an order outside of trading hours.\n4. Submit an order with incomplete details.\n5. Enter an order that exceeds the daily trading limit.","expectedResult":"For each scenario, the system should prevent the order from being placed, display an appropriate error message, and log the incident."},{"type":"functional","title":"Validate Compliance with Financial Regulations During Trades","description":"Ensure all trades comply with financial regulations such as TASE directives and BOI guidelines.","testId":"TC-010","testDescription":"Conduct a series of trades and verify that all regulatory requirements are met.","prerequisites":"User is authenticated and trading platform is connected to regulatory systems for compliance checks.","stepsToPerform":"1. User places multiple trades involving different types of securities.\n2. System checks each trade against regulatory requirements.\n3. Trades are executed if compliant.\n4. System blocks non-compliant trades and notifies the user.","expectedResult":"All trades either comply with the regulations and are executed, or are blocked with a clear explanation provided to the user."},{"type":"functional","title":"Verify Order Execution and Settlement","description":"Test the end-to-end process of order execution and settlement for equity buy orders, ensuring all financial and regulatory requirements are met.","testId":"TC-011","testDescription":"A user places an equity buy order, which is executed and settled correctly, with all financial calculations and regulatory compliance checks performed accurately.","prerequisites":"User is authenticated, has sufficient funds, and the market is open.","stepsToPerform":"1. User logs into the trading platform.\n2. User navigates to the equity trading section.\n3. User selects an equity and enters the quantity and price.\n4. User submits the order for execution.\n5. System processes the order, performs necessary validations, and executes it.\n6. System settles the order post-execution and updates user's portfolio and transaction history.","expectedResult":"Order is executed and settled without errors, user's portfolio and transaction history are updated correctly, and all compliance checks are passed."},{"type":"functional","title":"Security Transfer Authorization and Execution","description":"Ensure that security transfers both within and outside the bank are authorized and executed correctly, adhering to regulatory standards.","testId":"TC-012","testDescription":"A user initiates a security transfer, which requires authorization and should be executed correctly with proper logging and compliance.","prerequisites":"User has securities in their account, recipient details are correct, and transfer limits are set.","stepsToPerform":"1. User requests a security transfer.\n2. System checks for authorization requirements.\n3. Authorized personnel reviews and approves the transfer.\n4. System executes the transfer.\n5. System logs the transaction and checks for compliance with financial regulations.","expectedResult":"Security transfer is authorized, executed, and logged correctly, with all regulatory requirements satisfied."},{"type":"functional","title":"Real-Time Market Data Accuracy","description":"Verify that the trading platform displays real-time market data accurately and updates dynamically.","testId":"TC-013","testDescription":"The system should fetch and display real-time data from TASE and Bloomberg accurately, reflecting current market conditions.","prerequisites":"Market data feeds from TASE and Bloomberg are active and accessible by the system.","stepsToPerform":"1. Log into the trading platform.\n2. Access the market data section.\n3. Observe the real-time data feeds for accuracy and timeliness.\n4. Compare the displayed data against actual data from TASE and Bloomberg.","expectedResult":"Market data displayed is up-to-date, accurate, and reflects real-time changes from TASE and Bloomberg."},{"type":"functional","title":"Comprehensive Audit Trail for Transactions","description":"Test the system's ability to log and maintain a detailed audit trail for all user transactions for compliance and monitoring purposes.","testId":"TC-014","testDescription":"Every transaction made by a user should be logged with detailed information for audit purposes.","prerequisites":"User performs various transactions on the platform.","stepsToPerform":"1. User performs multiple transactions (e.g., trades, transfers).\n2. System logs each transaction with detailed information.\n3. Access the audit logs and verify the details recorded against actual transactions performed.","expectedResult":"All transactions are logged accurately in the audit trail with complete details, enabling compliance and monitoring."},{"type":"functional","title":"Error Handling and Exception Management for Trading Operations","description":"Ensure the system robustly handles errors and exceptions during trading operations without compromising data integrity or user experience.","testId":"TC-015","testDescription":"Simulate various trading errors and verify the system's response and recovery mechanisms.","prerequisites":"Trading platform is operational, and error simulation parameters are set.","stepsToPerform":"1. Simulate various trading errors (e.g., network failure, data format errors).\n2. Observe how the system handles these errors.\n3. Check system logs and error messages for appropriateness and clarity.\n4. Verify system recovery and data integrity post-error.","expectedResult":"System handles errors gracefully, provides clear error messages, logs incidents appropriately, and recovers without data loss."}] \ No newline at end of file diff --git a/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.xlsx b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.xlsx new file mode 100644 index 00000000..25bc7f10 Binary files /dev/null and b/functional_tests/TCSBaNCS_functional-after-fix/TCSBaNCS_functional-after-fix.xlsx differ