QA Test Plan & Prioritization Report
Feature: Automated Lead Scoring
Source Document: PRD_ConnectSphere_Automated_Lead_Scoring
Analysis Date: 2023-10-26

1. Summary
This report outlines the automatically generated test cases and risk-based execution plan for the 'Automated Lead Scoring' feature. A total of 12 test cases have been generated based on the provided requirements, covering functional, UI, and performance aspects. The test plan is prioritized to focus on high-risk areas, such as the core scoring logic and data handling, to ensure maximum defect detection efficiency.
2. Generated Test Cases
The following test cases have been generated from the requirements document:



Test Case ID
Description
Linked Requirement
Test Type




TC-FUNC-001
Verify that a new lead with no interactions is assigned a default score of 1.
FR-202, AC-101.2
Functional


TC-FUNC-002
Verify that submitting a lead with interactions (1 Email Open, 1 Form Submit) calculates the correct score based on default point values.
FR-201
Functional


TC-FUNC-003
Verify that scores are correctly recalculated within 30 seconds after a new interaction is logged for an existing lead.
FR-205
Functional


TC-FUNC-004
Verify that the calculated LEAD_SCORE cannot exceed 100, even if interaction points sum to a higher value.
FR-202
Edge Case


TC-FUNC-005
Verify that the calculated LEAD_SCORE cannot be less than 1.
FR-202
Edge Case


TC-FUNC-006
Verify an admin user can successfully update point values in the configuration interface.
FR-204, AC-204.1
Functional


TC-FUNC-007
Verify that after changing point values, new score calculations use the updated values.
FR-204, AC-204.1
Functional


TC-UI-001
Confirm the LEAD_SCORE integer is displayed correctly next to the lead name in the 'Lead View' list.
FR-203, AC-101.1
UI/Visual


TC-UI-002
Confirm the score display is properly aligned and readable on different screen resolutions (1080p, 1440p).
FR-203
UI/Visual


TC-PERF-001
Measure API response time for the scoring service endpoint under an average load of 100 events/minute.
NFR-301, AC-301.1
Performance


TC-PERF-002
Load test the scoring service with a sustained 1,000 events/minute for 15 minutes to check for performance degradation.
NFR-302
Performance


TC-PERF-003
Verify score calculation latency remains below 500ms during the peak load test.
NFR-301, NFR-302
Performance



3. Risk-Based Test Execution Plan
Tests are prioritized based on a risk analysis considering impact (business function criticality) and likelihood (component complexity, history of defects).



Execution Order
Test Case ID
Priority
Risk Score
Rationale




1
TC-FUNC-002
Critical
95
Core functionality validation. Failure here renders the feature unusable.


2
TC-FUNC-004
Critical
92
Validates critical boundary condition of the scoring logic. High impact if broken.


3
TC-FUNC-007
High
88
Ensures the system is configurable as required; key value proposition for admins.


4
TC-FUNC-003
High
85
Validates the near real-time update requirement, which is critical for user trust.


5
TC-PERF-003
High
80
Confirms system performance under load; failure could impact the entire CRM.


6
TC-FUNC-001
Medium
70
Validates default state handling. Moderate impact.


7
TC-FUNC-006
Medium
68
Confirms admin UI interactions work as expected.


8
TC-UI-001
Medium
65
Core visual confirmation that the feature is accessible to the end-user.


9
TC-PERF-001
Medium
60
Baseline performance check under normal conditions.


10
TC-FUNC-005
Low
50
Lower impact edge case compared to the upper boundary.


11
TC-PERF-002
Low
45
Stress testing is important but secondary to core function and average load performance.


12
TC-UI-002
Low
40
Responsive design validation; lower priority than basic visibility.