Skip to content

Account Management Test Report Requirements

This document outlines the structure and key areas for the test report on the Account Management features of the UBU Finance Frontend application. 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., account creation, currency management, account type configuration).
  • 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.

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 related features (e.g., from accounts list to account details, or from account types to associated accounts).
    • Describe errors in the sequence of operations. For example, does creating an account type correctly reflect in the account creation form?
  • 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 and currency setup.

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 features like interest calculation, fee application, and account restrictions aligns with standard banking practices.
  • Feature Logic:
    • Highlight any feature logic that seems irrelevant or counter-intuitive, such as illogical constraints on account types or currencies.

4. Security Errors

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

  • Internal Security:
    • Analyze permissions related to account management. Can a user with limited permissions perform sensitive actions like modifying interest rates or deleting account types?
    • Identify potential security risks from internal users regarding account access and transaction capabilities.
  • 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.

5. Design Errors

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

  • UI/UX Design:
    • Identify elements that are poorly designed, especially in data-heavy components like account tables and forms for creating account types.
    • Report issues with layout, data visualization, and visual clarity.
  • User Experience:
    • Point out any design choices that lead to a poor user experience, such as complex forms for account setup or unclear presentation of account details.
  • Accessibility:
    • Note any violations of accessibility standards (WCAG), particularly in forms and data tables.