Skip to content

Accounts V2.1 Test Report Requirements

This document outlines the structure and key areas for the test report on the Accounts V2.1 features of the UBU Finance System Platform (https://system.ubu-economy.com). The report should focus on the following five categories:

1. System Errors

This section should identify which features are working correctly and which are not.

  • Working Features: List all features and components that are functioning as per the requirements (e.g., hierarchical account management, joint ownership, card management, balance indexing accounts).
  • Non-Working/Partially-Working Features:
  • Detail any feature that is not working or is only partially working.
  • Provide steps to reproduce the issue.
  • Clearly state the expected behavior versus the actual result.

Specific Areas to Test:

  • Bank account creation and management
  • Currency account creation and management within bank accounts
  • Balance indexing account creation and management within currency accounts
  • Joint ownership addition, editing, and removal
  • Card type creation and management
  • Card assignment to balance indexing accounts
  • Account type configuration and currency settings
  • Internet banking activation process

2. Flow Errors

This section should focus on how different features interact and the navigational flow between them.

  • Navigation and Interactivity:
  • Report any issues in navigating between hierarchical account levels (bank account → currency account → balance indexing account).
  • Describe errors in the sequence of operations. For example, does creating a bank account correctly lead to currency account creation options?
  • Test flow from joint ownership management to account access permissions.
  • Verify card assignment flow from card types to balance indexing accounts.
  • Workflow Consistency:
  • Identify any inconsistencies in the workflow that could confuse the user or lead to errors, especially in processes involving multiple steps like account creation, joint ownership setup, and card assignment.
  • Test the complete flow from account type configuration to account creation to joint ownership management.

3. Logical Errors

This section is for reporting features that may be technically functional but are not logically sound from a user experience or banking system perspective.

  • Business Logic:
  • Assess if the implemented logic for hierarchical account structure aligns with banking industry standards.
  • Verify that joint ownership permissions are logically implemented and enforced.
  • Check if card assignment logic follows proper banking practices.
  • Validate account type configuration logic and currency settings.
  • Feature Logic:
  • Highlight any feature logic that seems irrelevant or counter-intuitive, such as illogical constraints on joint ownership or card assignment.
  • Verify that KYC verification requirements for joint owners are properly enforced.
  • Check if account type joint ownership settings are correctly applied during account creation.

4. Security Errors

This section is dedicated to identifying potential internal and external security vulnerabilities.

  • Internal Security:
  • Analyze permissions related to hierarchical account management. Can a user with limited permissions perform sensitive actions like modifying joint ownership or assigning cards?
  • Identify potential security risks from internal users regarding account access and transaction capabilities.
  • Test permission escalation vulnerabilities in joint ownership management.
  • Verify that account type configuration changes are properly restricted.
  • External Security:
  • Report any potential vulnerabilities that could be exploited by external attackers to gain unauthorized access to account information or perform fraudulent activities.
  • Assess the security of financial data handling across the hierarchical structure.
  • Test for vulnerabilities in card management and assignment processes.
  • Verify that joint ownership information is properly secured.

5. Design Errors

This section should cover any issues related to user interface (UI) and user experience (UX) design in the accounts V2.1 section.

  • UI/UX Design:
  • Identify elements that are poorly designed, especially in complex hierarchical data displays like account trees and joint ownership tables.
  • Report issues with layout, data visualization, and visual clarity in multi-level account management.
  • Test the design of card management interfaces and assignment workflows.
  • User Experience:
  • Point out any design choices that lead to a poor user experience, such as complex forms for joint ownership setup or unclear presentation of hierarchical account relationships.
  • Assess the usability of account type configuration interfaces.
  • Test the user experience of card assignment and management processes.
  • Accessibility:
  • Note any violations of accessibility standards (WCAG), particularly in complex hierarchical interfaces and joint ownership management forms.

Specific Test Scenarios

Account Hierarchy Management

  1. Bank Account Creation Flow:

  2. Create a new bank account with account type selection

  3. Verify currency account creation options
  4. Test account number generation and uniqueness

  5. Validate account type configuration application

  6. Currency Account Management:

  7. Add new currency to existing bank account

  8. Edit currency account settings
  9. Delete currency account (with proper validation)

  10. Test currency-specific configurations

  11. Balance Indexing Account Management:

  12. Create balance indexing accounts within currency accounts
  13. Activate/deactivate balance indexing accounts
  14. Close balance indexing accounts
  15. Verify card assignment capabilities

Joint Ownership Management

  1. Joint Owner Addition:

  2. Add joint owner to account with joint ownership support

  3. Verify KYC verification requirement enforcement
  4. Test maximum joint owner limit validation

  5. Validate permission assignment and configuration

  6. Joint Owner Management:

  7. Edit joint owner permissions

  8. Deactivate/reactivate joint owners
  9. Transfer primary ownership

  10. Delete joint owners with proper validation

  11. Joint Ownership Types:

  12. Test primary joint owner functionality
  13. Test secondary joint owner functionality
  14. Verify permission enforcement for different joint types

Card Management

  1. Card Type Management:

  2. Create new card types

  3. Edit card type configurations
  4. Delete card types (with proper validation)

  5. Test card type assignment to balance indexing accounts

  6. Card Assignment:

  7. Assign cards to balance indexing accounts
  8. Test card status management (active, inactive, locked, expired)
  9. Verify card limit configurations
  10. Test card renewal processes

Account Type Configuration

  1. Account Type Management:

  2. Create account types with joint ownership settings

  3. Configure maximum joint owner limits
  4. Test account type currency configurations

  5. Validate account type deletion restrictions

  6. Currency Configuration:

  7. Add currency configurations to account types
  8. Edit currency-specific settings
  9. Delete currency configurations
  10. Test configuration application to new accounts

Internet Banking Activation

  1. Activation Process:
  2. Test internet banking activation for customers
  3. Verify credential generation and email delivery
  4. Test activation permission requirements
  5. Validate activation status tracking

Performance Testing

  • Test system performance with large numbers of hierarchical accounts
  • Verify joint ownership management performance with multiple joint owners
  • Test card management performance with numerous card assignments
  • Assess account type configuration performance

Integration Testing

  • Test integration between account hierarchy levels
  • Verify joint ownership integration with customer management
  • Test card management integration with balance indexing accounts
  • Validate account type configuration integration with account creation

Data Validation Testing

  • Verify data integrity across hierarchical account structure
  • Test joint ownership data consistency
  • Validate card assignment data accuracy
  • Test account type configuration data persistence