Skip to content

Customer Management Test Report Requirements

This document outlines the structure and key areas for the test report on the Customer 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.
  • 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 the customer list to a customer's details, then to their accounts).
  • Describe errors in the sequence of operations. For example, does creating a new customer lead to the correct subsequent view or action?
  • Workflow Consistency:
  • Identify any inconsistencies in the workflow that could confuse the user or lead to errors.

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 aligns with standard banking practices and user expectations.
  • For example, are customer verification processes logical and implemented in the correct order?
  • Feature Logic:
  • Highlight any feature logic that seems irrelevant or counter-intuitive to the user's goals.

4. Security Errors

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

  • Internal Security:
  • Analyze permissions and roles. Can a user access or modify data they shouldn't?
  • Identify potential security risks from internal users (e.g., data leakage, unauthorized transactions).
  • External Security:
  • Report any potential vulnerabilities that could be exploited by external attackers (e.g., SQL injection, XSS, insecure data handling).
  • Assess the security of data transmission and storage.

5. Design Errors

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

  • UI/UX Design:
  • Identify elements that are poorly designed, confusing, or inconsistent with the overall application design.
  • Report issues with layout, responsiveness, and visual clarity.
  • User Experience:
  • Point out any design choices that lead to a poor user experience, such as overly complex forms, unclear instructions, or inadequate feedback.
  • Accessibility:
  • Note any violations of accessibility standards (WCAG).