QA Clarifications and Recommendations for a Broadband Company

At JW Infotech, we take pride in offering world-class Quality Assurance (QA) services tailored to meet the diverse needs of our global clientele. Recently, we were approached by a UK-based broadband company seeking our expertise to ensure the seamless functionality and robustness of their platform. As part of our engagement, we conducted an initial discovery phase, thoroughly analyzing the Software Requirements Specification (SRS) document provided by the client.

This comprehensive report captures our findings and clarifications during the discovery phase, highlighting essential inputs to streamline the QA process. With a commitment to precision and excellence, JW Infotech aims to empower businesses by delivering high-quality solutions that drive efficiency and enhance user satisfaction. This blog offers a glimpse into how we partner with clients to uphold their technological ambitions.

1. Overview

This report consolidates clarifications and recommendations for the QA process after reviewing the SRS (Software Requirement Specification). The goal is to ensure that the testing process is aligned with functional requirements, usability expectations, and technical constraints.

---

2. Clarifications from SRS

2.1 Browsers and Devices

• Primary Browsers:
  • Chrome
  • Safari
  • Edge
• Primary Devices:
  • Laptop/Desktop
  • iPhone
  • Android phones
  • iPad
  • Android tablets

2.2 Localization and Language

• Content Language: English.
• Currency Switcher: Testing based on geolocation, requiring manual checks by the customer.

2.3 Navigation

• Menu Bar Items: Open in the same tab.
• Footer Items: Open in the same tab.
• Post Sign-Up Navigation: Redirects to the homepage.
• Login/Logout Button: Requires confirmation from design documentation.

2.4 Testing Scope

• Functional Testing.
• UI Testing.
• Localization Testing (on the agreed scope).

2.5 User Input and Validation

• Mandatory Fields:
  • Super Admin can edit redeemable text and terms and conditions.
  • Network operators cannot be added or deleted.
• Validation Rules:
  • Operator Name: Controlled via an external API; no validation needed.
  • Email: Cannot be reused across the system. Deactivated emails remain in the system.
  • Mobile Number: Validated as per country standards (e.g., Sri Lanka: 94XXXXXXXXX).
  • Name Fields: Allow hyphen, apostrophe, and dots.
  • Search Bar: Minimum of 2 characters, “contains” condition (not “starts with”); supports simultaneous searches for provider and promotion names.
• Password Rules: Previously used passwords can be reused.

2.6 Admin and Super Admin Permissions

• Admins:
  • Cannot delete Super Admins.
  • Cannot use email addresses already registered by customers.
• Customers:
  • Cannot use admin email addresses.

2.7 System Limitations

• Unique Fields: Email addresses are unique across admins and customers.
• Network Operator Records: Controlled via an external API; deletion is not permitted.
• Pending Invitations: No clarification on validity duration.

2.8 Additional Suggestions

• Security Messaging: Neutral message for valid email input to prevent email guessing (e.g., “Please check your inbox for the provided email”).
• Search Bar: Improve flexibility by supporting partial string matches.
• Login Restrictions: Requires pattern confirmation post-development.

2.9 UI and UX

• Date Display Format: dd/MMM/YYYY (e.g., 21 May 2024).
• Hover States: No confirmation of mouse pointer state changes; needs clarification.

---

3. Recommendations for Testing

3.1 Functional Testing

• Verify all navigation flows, especially for:
  • Menu bar items.
  • Footer items.
  • Login/logout button behavior.
• Test post sign-up redirection to the homepage.

3.2 Validation Testing

• Ensure all mandatory fields function as intended.
• Validate email reuse restrictions across admins and customers.
• Test mobile number formats as per country standards.
• Test search bar functionalities for the “contains” condition.

3.3 Security Testing

• Test password reuse policies.
• Verify neutral security messaging for email validation.

3.4 UI/UX Testing

• Confirm hover states for clickable elements (e.g., mouse pointer change).
• Ensure date formats are displayed consistently as dd/MMM/YYYY.
• Test currency switcher functionality based on geolocation.

3.5 Admin-Specific Testing

• Test permissions for admins and Super Admins:
  • Admins cannot delete Super Admins.
  • Admins cannot use customer email addresses, and vice versa.

3.6 Localization Testing

• Verify language consistency across the application (English).
• Ensure currency switcher adapts correctly to geolocations.

---

4. Actionable Suggestions

4.1 Enhance Search Functionality

• Improve search bar to handle both “contains” and “starts with” conditions.

4.2 Strengthen Security Measures

• Disallow password reuse to improve security.
• Add neutral messaging for valid email inputs to reduce guessing attacks.

4.3 UI Improvements

• Add hover state visual feedback for clickable elements like links, buttons, and icons.
• Verify consistent navigation behaviors (e.g., opening links in same or new tabs).

4.4 Clarify Pending Features

• Confirm pending invitation validity duration.
• Finalize login restrictions and test for compliance.

---

5. Summary

This QA clarification report highlights the key areas requiring focus during the testing process. It outlines the functional, security, and usability aspects to ensure the system operates as expected. Additionally, it provides actionable recommendations to address gaps and enhance user experience.

For detailed test strategies or further clarifications, a follow-up Was conducted which we will post in an upcoming blog.

---