Test Intelligence
From product knowledge to a reviewable test specification
The generation step. It reads one immutable snapshot and produces a risk-weighted strategy, scenarios and cases in the vendor-neutral SALC Test Specification Model.
Processing
Test strategy generated
Every model call routes through the AI Model Gateway and produces an audit record with cost, duration and prompt version.
SPEC #TS-0142 · v12
Reading knowledge snapshot
#KN-0842Weighting requirements by risk
37 requirementsResolving business rules
12 rulesMapping risk to coverage depth
8 risksPlanning scenarios
82 scenariosExpanding to test cases
147 casesAssessing automation suitability
86 candidatesBinding citations
214 relationships
0
Scenarios
0
Test cases
0
Negative cases
0
Boundary cases
0
High-risk requirements
0
Automation candidates
SALC Test Specification Model
Generated test cases
Every publishing adapter consumes this model rather than raw AI output — which is why a new destination is a new consumer, not a new integration with the generator.
147 / 147
| ID | Requirement | Scenario | Type | Priority | Expected result | Traceability | Status |
|---|---|---|---|---|---|---|---|
| TC-001 | REQ-1001 | Claimant registration against an active policy is satisfied on the primary pathPrimary path — claimant registration against an active policy | Functional | High | The system behaves as REQ-1001 states: A claimant must be able to register for the portal using a policy number and registered mobile number. | REQ-1001 | Validated |
| TC-002 | REQ-1001 | Claimant registration against an active policy using the agent-assisted registration deskPrimary path — claimant registration against an active policy | Functional | High | The outcome is identical to the primary path when the journey runs using the agent-assisted registration desk. | REQ-1001 | Validated |
| TC-003 | REQ-1001 | Policy number must match the format PX-00000000Validation refusals — claimant registration against an active policy | Negative | High | The action is refused and the message "Enter a valid policy number" is shown. No state is changed. | REQ-1001 | Validated |
| TC-004 | REQ-1001 | A lapsed or cancelled policy cannot be registeredValidation refusals — claimant registration against an active policy | Negative | High | The action is refused and the message "This policy is not active" is shown. No state is changed. | REQ-1001 | Validated |
| TC-005 | REQ-1002 | Step-up authentication before claim submission is satisfied on the primary pathPrimary path — step-up authentication before claim submission | Functional | High | The system behaves as REQ-1002 states: Submitting a claim must require a one-time passcode delivered to the registered mobile number, in addition to the active portal session. | REQ-1002 | Validated |
| TC-006 | REQ-1002 | Step-up authentication before claim submission with passcode delivered by SMS fallbackPrimary path — step-up authentication before claim submission | Functional | High | The outcome is identical to the primary path when the journey runs with passcode delivered by SMS fallback. | REQ-1002 | Validated |
| TC-007 | REQ-1002 | An expired passcode must not be acceptedValidation refusals — step-up authentication before claim submission | Negative | High | The action is refused and the message "This code has expired. Request a new one" is shown. No state is changed. | REQ-1002 | Validated |
| TC-008 | REQ-1002 | A passcode issued for a different claim must not be acceptedValidation refusals — step-up authentication before claim submission | Negative | High | The action is refused and the message "That code does not match this claim" is shown. No state is changed. | REQ-1002 | Validated |
| TC-009 | REQ-1003 | Idle session timeout is satisfied on the primary pathPrimary path — idle session timeout | Functional | Medium | The system behaves as REQ-1003 states: A portal session must end automatically after 15 minutes without user interaction, and any unsaved claim content must be preserved as a draft. | REQ-1003 | Validated |
| TC-010 | REQ-1003 | Idle duration before session expiry just below the limit (14 minutes 59 seconds)Boundary — idle duration before session expiry | Boundary | High | 14 minutes 59 seconds is accepted without warning. | REQ-1003 | Validated |
| TC-011 | REQ-1003 | Idle duration before session expiry exactly at the limit (15 minutes)Boundary — idle duration before session expiry | Boundary | High | 15 minutes is accepted, because the limit is inclusive. | REQ-1003 | Validated |
| TC-012 | REQ-1003 | Idle duration before session expiry just above the limit (15 minutes 1 second)Boundary — idle duration before session expiry | Boundary | High | 15 minutes 1 second is refused and the limit is stated in the message. | REQ-1003 | Validated |
| TC-013 | REQ-1004 | Passcode retry lockout is satisfied on the primary pathPrimary path — passcode retry lockout | Functional | High | The system behaves as REQ-1004 states: After 5 consecutive incorrect passcode entries the account must be locked for 30 minutes and the claimant notified. | REQ-1004 | Validated |
| TC-014 | REQ-1004 | Consecutive failed passcode attempts just below the limit (4 attempts)Boundary — consecutive failed passcode attempts | Boundary | High | 4 attempts is accepted without warning. | REQ-1004 | Validated |
| TC-015 | REQ-1004 | Consecutive failed passcode attempts exactly at the limit (5 attempts)Boundary — consecutive failed passcode attempts | Boundary | High | 5 attempts is accepted, because the limit is inclusive. | REQ-1004 | Validated |
| TC-016 | REQ-1004 | Consecutive failed passcode attempts just above the limit (6 attempts)Boundary — consecutive failed passcode attempts | Boundary | High | 6 attempts is refused and the limit is stated in the message. | REQ-1004 | Validated |
| TC-017 | REQ-1004 | A locked account must not accept a correct passcode until the lock expiresValidation refusals — passcode retry lockout | Negative | High | The action is refused and the message "Account temporarily locked" is shown. No state is changed. | REQ-1004 | Validated |
| TC-018 | REQ-1005 | Role-based access to claim records is satisfied on the primary pathPrimary path — role-based access to claim records | Functional | High | The system behaves as REQ-1005 states: Portal capabilities must be restricted by role. | REQ-1005 | Validated |
| TC-019 | REQ-1005 | A claimant must not retrieve a claim belonging to another policyValidation refusals — role-based access to claim records | Negative | High | The action is refused and the message "You do not have access to this claim" is shown. No state is changed. | REQ-1005 | Validated |
| TC-020 | REQ-1005 | Claimant access to REQ-1005 is exactly as specifiedRole boundaries — role-based access to claim records | Permission | High | The claimant can perform only the operations REQ-1005 grants that role; every other operation is refused. | REQ-1005 | Validated |
| TC-021 | REQ-1005 | Adjuster access to REQ-1005 is exactly as specifiedRole boundaries — role-based access to claim records | Permission | High | The adjuster can perform only the operations REQ-1005 grants that role; every other operation is refused. | REQ-1005 | Validated |
| TC-022 | REQ-1005 | Supervisor access to REQ-1005 is exactly as specifiedRole boundaries — role-based access to claim records | Permission | High | The supervisor can perform only the operations REQ-1005 grants that role; every other operation is refused. | REQ-1005 | Validated |
| TC-023 | REQ-1005 | Auditor access to REQ-1005 is exactly as specifiedRole boundaries — role-based access to claim records | Permission | High | The auditor can perform only the operations REQ-1005 grants that role; every other operation is refused. | REQ-1005 | Validated |
| TC-024 | REQ-1006 | First notification of loss is satisfied on the primary pathPrimary path — first notification of loss | Functional | High | The system behaves as REQ-1006 states: A claimant must be able to open a new claim by providing the incident date, incident type, a description and the loss location. | REQ-1006 | Validated |
| TC-025 | REQ-1006 | First notification of loss from the mobile web applicationAssisted intake channels | Functional | High | The outcome is identical to the primary path when the journey runs from the mobile web application. | REQ-1006 | Validated |
| TC-026 | REQ-1006 | First notification of loss through an agent-assisted intake sessionAssisted intake channels | Functional | High | The outcome is identical to the primary path when the journey runs through an agent-assisted intake session. | REQ-1006 | Validated |
| TC-027 | REQ-1006 | A description shorter than 20 characters must be rejectedValidation refusals — first notification of loss | Negative | High | The action is refused and the message "Describe what happened in at least 20 characters" is shown. No state is changed. | REQ-1006 | Validated |
| TC-028 | REQ-1006 | A claim must not be opened against a policy the claimant does not holdValidation refusals — first notification of loss | Negative | High | The action is refused and the message "No active policy matches this claimant" is shown. No state is changed. | REQ-1006 | Validated |
| TC-029 | REQ-1007 | Claim type selection drives the intake form is satisfied on the primary pathPrimary path — claim type selection drives the intake form | Functional | Medium | The system behaves as REQ-1007 states: Selecting a claim type of motor, health, property or travel must present only the fields and evidence prompts relevant to that type. | REQ-1007 | Validated |
| TC-030 | REQ-1007 | Claim type selection drives the intake form for a health claimPrimary path — claim type selection drives the intake form | Functional | Medium | The outcome is identical to the primary path when the journey runs for a health claim. | REQ-1007 | Validated |
| TC-031 | REQ-1007 | Claim type selection drives the intake form for a property claimPrimary path — claim type selection drives the intake form | Functional | Medium | The outcome is identical to the primary path when the journey runs for a property claim. | REQ-1007 | Validated |
| TC-032 | REQ-1008 | Incident reporting window is satisfied on the primary pathPrimary path — incident reporting window | Functional | High | The system behaves as REQ-1008 states: A claim must be reported within 30 days of the incident date. | REQ-1008 | Validated |
| TC-033 | REQ-1008 | Days between incident date and notification just below the limit (29 days)Boundary — days between incident date and notification | Boundary | High | 29 days is accepted without warning. | REQ-1008 | Validated |
| TC-034 | REQ-1008 | Days between incident date and notification exactly at the limit (30 days)Boundary — days between incident date and notification | Boundary | High | 30 days is accepted, because the limit is inclusive. | REQ-1008 | Validated |
| TC-035 | REQ-1008 | Days between incident date and notification just above the limit (31 days)Boundary — days between incident date and notification | Boundary | High | 31 days is refused and the limit is stated in the message. | REQ-1008 | Validated |
| TC-036 | REQ-1008 | An incident date in the future must be rejectedValidation refusals — incident reporting window | Negative | High | The action is refused and the message "The incident date cannot be in the future" is shown. No state is changed. | REQ-1008 | Validated |
| TC-037 | REQ-1008 | An exception request outside the window must not itself create a claimValidation refusals — incident reporting window | Negative | High | The action is refused and the message "Exception requested — no claim has been created yet" is shown. No state is changed. | REQ-1008 | Validated |
| TC-038 | REQ-1009 | Draft claim autosave is satisfied on the primary pathPrimary path — draft claim autosave | Functional | Medium | The system behaves as REQ-1009 states: Claim content must be saved as a draft every 30 seconds and on navigation away, so that an interrupted claimant resumes without re-entering data. | REQ-1009 | Validated |
| TC-039 | REQ-1009 | A draft must not be recoverable after the claim is submittedValidation refusals — draft claim autosave | Negative | Medium | The action is refused and the message "This claim has already been submitted" is shown. No state is changed. | REQ-1009 | Validated |
| TC-040 | REQ-1010 | Claim reference generation is satisfied on the primary pathPrimary path — claim reference generation | Functional | Medium | The system behaves as REQ-1010 states: Every submitted claim must receive a unique, non-sequential reference of the form CLM-YYYY-XXXXXX, shown on screen and included in every notification. | REQ-1010 | Validated |
| TC-041 | REQ-1011 | Duplicate claim detection is satisfied on the primary pathPrimary path — duplicate claim detection | Functional | High | The system behaves as REQ-1011 states: When a claimant submits a second claim for the same policy, incident date and incident type, the portal must flag it as a potential duplicate and require confirmation before it enters the assessment queue. | REQ-1011 | Validated |
| TC-042 | REQ-1011 | A confirmed duplicate must not create a second assessment taskValidation refusals — duplicate claim detection | Negative | High | The action is refused and the message "A claim already exists for this incident" is shown. No state is changed. | REQ-1011 | Validated |
| TC-043 | REQ-1012 | Claim withdrawal before assessment is satisfied on the primary pathPrimary path — claim withdrawal before assessment | Functional | Medium | The system behaves as REQ-1012 states: A claimant must be able to withdraw a submitted claim while its status is Received or Under Review. | REQ-1012 | Validated |
| TC-044 | REQ-1012 | Withdrawal must be refused once a decision existsValidation refusals — claim withdrawal before assessment | Negative | Medium | The action is refused and the message "This claim can no longer be withdrawn" is shown. No state is changed. | REQ-1012 | Validated |
| TC-045 | REQ-1012 | A withdrawn claim must not be re-opened by resubmitting the same formValidation refusals — claim withdrawal before assessment | Negative | Medium | The action is refused and the message "This claim was withdrawn. Start a new claim" is shown. No state is changed. | REQ-1012 | Validated |
| TC-046 | REQ-1012 | Claimant access to REQ-1012 is exactly as specifiedRole boundaries — claim withdrawal before assessment | Permission | High | The claimant can perform only the operations REQ-1012 grants that role; every other operation is refused. | REQ-1012 | Validated |
| TC-047 | REQ-1012 | Adjuster access to REQ-1012 is exactly as specifiedRole boundaries — claim withdrawal before assessment | Permission | High | The adjuster can perform only the operations REQ-1012 grants that role; every other operation is refused. | REQ-1012 | Validated |
| TC-048 | REQ-1020 | Accepted evidence file types is satisfied on the primary pathPrimary path — accepted evidence file types | Functional | High | The system behaves as REQ-1020 states: The portal must accept PDF, JPEG, PNG and MP4 evidence. | REQ-1020 | Validated |
| TC-049 | REQ-1020 | Accepted evidence file types for an MP4 dashcam recordingPrimary path — accepted evidence file types | Functional | High | The outcome is identical to the primary path when the journey runs for an MP4 dashcam recording. | REQ-1020 | Validated |
| TC-050 | REQ-1020 | An executable or archive file must be refusedValidation refusals — accepted evidence file types | Negative | High | The action is refused and the message "That file type cannot be uploaded" is shown. No state is changed. | REQ-1020 | Validated |
| TC-051 | REQ-1020 | A file whose extension and content type disagree must be refusedValidation refusals — accepted evidence file types | Negative | High | The action is refused and the message "That file could not be verified" is shown. No state is changed. | REQ-1020 | Validated |
| TC-052 | REQ-1021 | Per-file upload size limit is satisfied on the primary pathPrimary path — per-file upload size limit | Functional | High | The system behaves as REQ-1021 states: An individual evidence file must not exceed 10 MB. | REQ-1021 | Validated |
| TC-053 | REQ-1021 | Evidence file size just below the limit (9.9 MB)Boundary — evidence file size | Boundary | High | 9.9 MB is accepted without warning. | REQ-1021 | Validated |
| TC-054 | REQ-1021 | Evidence file size exactly at the limit (10 MB)Boundary — evidence file size | Boundary | High | 10 MB is accepted, because the limit is inclusive. | REQ-1021 | Validated |
| TC-055 | REQ-1021 | Evidence file size just above the limit (10.1 MB)Boundary — evidence file size | Boundary | High | 10.1 MB is refused and the limit is stated in the message. | REQ-1021 | Validated |
| TC-056 | REQ-1021 | A zero-byte file must be refusedValidation refusals — per-file upload size limit | Negative | High | The action is refused and the message "That file is empty" is shown. No state is changed. | REQ-1021 | Validated |
| TC-057 | REQ-1022 | Maximum evidence files per claim is satisfied on the primary pathPrimary path — maximum evidence files per claim | Functional | Medium | The system behaves as REQ-1022 states: A claim must hold no more than 20 evidence files. | REQ-1022 | Validated |
| TC-058 | REQ-1022 | Maximum evidence files per claim after removing a file to make roomPrimary path — maximum evidence files per claim | Functional | Medium | The outcome is identical to the primary path when the journey runs after removing a file to make room. | REQ-1022 | Validated |
| TC-059 | REQ-1022 | Evidence files attached to one claim just below the limit (19 files)Boundary — evidence files attached to one claim | Boundary | High | 19 files is accepted without warning. | REQ-1022 | Validated |
| TC-060 | REQ-1022 | Evidence files attached to one claim exactly at the limit (20 files)Boundary — evidence files attached to one claim | Boundary | High | 20 files is accepted, because the limit is inclusive. | REQ-1022 | Validated |
| TC-061 | REQ-1022 | Evidence files attached to one claim just above the limit (21 files)Boundary — evidence files attached to one claim | Boundary | High | 21 files is refused and the limit is stated in the message. | REQ-1022 | Validated |
| TC-062 | REQ-1023 | Malware scanning of uploaded evidence is satisfied on the primary pathPrimary path — malware scanning of uploaded evidence | Functional | High | The system behaves as REQ-1023 states: Every uploaded file must be scanned before it is attached to a claim. | REQ-1023 | Validated |
| TC-063 | REQ-1023 | A file failing the scan must not become retrievableValidation refusals — malware scanning of uploaded evidence | Negative | High | The action is refused and the message "That file could not be accepted" is shown. No state is changed. | REQ-1023 | Validated |
| TC-064 | REQ-1023 | A quarantined file must not count toward the evidence file limitValidation refusals — malware scanning of uploaded evidence | Negative | High | The action is refused and the message "Quarantined files are not attached to the claim" is shown. No state is changed. | REQ-1023 | Validated |
| TC-065 | REQ-1024 | Redaction of sensitive fields in shared evidence is satisfied on the primary pathPrimary path — redaction of sensitive fields in shared evidence | Functional | High | The system behaves as REQ-1024 states: When evidence is shared outside the assessing team, bank account numbers, government identifiers and contact details must be redacted in the shared copy. | REQ-1024 | Validated |
| TC-066 | REQ-1024 | The unredacted original must remain retrievable to the assessing team onlyValidation refusals — redaction of sensitive fields in shared evidence | Negative | High | The action is refused and the message "You do not have access to the original document" is shown. No state is changed. | REQ-1024 | Validated |
| TC-067 | REQ-1024 | Adjuster access to REQ-1024 is exactly as specifiedRole boundaries — redaction of sensitive fields in shared evidence | Permission | High | The adjuster can perform only the operations REQ-1024 grants that role; every other operation is refused. | REQ-1024 | Validated |
| TC-068 | REQ-1024 | Supervisor access to REQ-1024 is exactly as specifiedRole boundaries — redaction of sensitive fields in shared evidence | Permission | High | The supervisor can perform only the operations REQ-1024 grants that role; every other operation is refused. | REQ-1024 | Validated |
| TC-069 | REQ-1025 | Evidence photograph metadata capture is satisfied on the primary pathPrimary path — evidence photograph metadata capture | Functional | Medium | The system behaves as REQ-1025 states: Where a photograph carries capture time and location metadata, that metadata must be recorded against the evidence item and shown to the adjuster. | REQ-1025 | Validated |
| TC-070 | REQ-1025 | Evidence photograph metadata capture for a photograph carrying no capture metadataPrimary path — evidence photograph metadata capture | Functional | Medium | The outcome is identical to the primary path when the journey runs for a photograph carrying no capture metadata. | REQ-1025 | Validated |
| TC-071 | REQ-1026 | Evidence retention period is satisfied on the primary pathPrimary path — evidence retention period | Functional | High | The system behaves as REQ-1026 states: Evidence must be retained for 7 years from claim closure and then purged, with the purge recorded in the audit log. | REQ-1026 | Validated |
| TC-072 | REQ-1026 | Evidence retention period with the post-purge audit record verifiedPrimary path — evidence retention period | Functional | High | The outcome is identical to the primary path when the journey runs with the post-purge audit record verified. | REQ-1026 | Validated |
| TC-073 | REQ-1027 | Mandatory evidence checklist by claim type is satisfied on the primary pathPrimary path — mandatory evidence checklist by claim type | Functional | High | The system behaves as REQ-1027 states: Each claim type must define a mandatory evidence set. | REQ-1027 | Validated |
| TC-074 | REQ-1027 | Mandatory evidence checklist by claim type for a health claimPrimary path — mandatory evidence checklist by claim type | Functional | High | The outcome is identical to the primary path when the journey runs for a health claim. | REQ-1027 | Validated |
| TC-075 | REQ-1027 | A waiver without a reason must be refusedValidation refusals — mandatory evidence checklist by claim type | Negative | High | The action is refused and the message "Give a reason before marking this item unavailable" is shown. No state is changed. | REQ-1027 | Validated |
| TC-076 | REQ-1027 | A mandatory item must not be silently dropped when the claim type changesValidation refusals — mandatory evidence checklist by claim type | Negative | High | The action is refused and the message "Evidence requirements have changed for this claim type" is shown. No state is changed. | REQ-1027 | Validated |
| TC-077 | REQ-1028 | Upload resume after a network interruption is satisfied on the primary pathPrimary path — upload resume after a network interruption | Functional | Medium | The system behaves as REQ-1028 states: An interrupted evidence upload must resume from the last completed chunk rather than restarting, and must not produce a partial file on the claim. | REQ-1028 | Validated |
| TC-078 | REQ-1029 | Evidence version history is satisfied on the primary pathPrimary path — evidence version history | Functional | Medium | The system behaves as REQ-1029 states: Replacing an evidence item must preserve the previous version and record who replaced it and when. | REQ-1029 | Validated |
| TC-079 | REQ-1029 | Evidence version history where the replacement is made by a different adjusterPrimary path — evidence version history | Functional | Medium | The outcome is identical to the primary path when the journey runs where the replacement is made by a different adjuster. | REQ-1029 | Validated |
| TC-080 | REQ-1030 | Third-party evidence link expiry is satisfied on the primary pathPrimary path — third-party evidence link expiry | Functional | High | The system behaves as REQ-1030 states: A share link issued to a garage, hospital or surveyor must expire 72 hours after issue and must not be re-usable after expiry. | REQ-1030 | Validated |
| TC-081 | REQ-1030 | Age of a third-party share link just below the limit (71 hours 59 minutes)Boundary — age of a third-party share link | Boundary | High | 71 hours 59 minutes is accepted without warning. | REQ-1030 | Validated |
| TC-082 | REQ-1030 | Age of a third-party share link exactly at the limit (72 hours)Boundary — age of a third-party share link | Boundary | High | 72 hours is accepted, because the limit is inclusive. | REQ-1030 | Validated |
| TC-083 | REQ-1030 | Age of a third-party share link just above the limit (72 hours 1 minute)Boundary — age of a third-party share link | Boundary | High | 72 hours 1 minute is refused and the limit is stated in the message. | REQ-1030 | Validated |
| TC-084 | REQ-1030 | An expired link must not reveal claim detailsValidation refusals — third-party evidence link expiry | Negative | High | The action is refused and the message "This link is no longer valid" is shown. No state is changed. | REQ-1030 | Validated |
| TC-085 | REQ-1031 | Accessible evidence upload interface is satisfied on the primary pathPrimary path — accessible evidence upload interface | Functional | High | The system behaves as REQ-1031 states: The upload interface must be operable by keyboard alone and must announce upload progress and errors to assistive technology. | REQ-1031 | Validated |
| TC-086 | REQ-1031 | Accessible evidence upload interface using keyboard navigation onlyPrimary path — accessible evidence upload interface | Functional | High | The outcome is identical to the primary path when the journey runs using keyboard navigation only. | REQ-1031 | Validated |
| TC-087 | REQ-1040 | Policy coverage validation is satisfied on the primary pathPrimary path — policy coverage validation | Functional | High | The system behaves as REQ-1040 states: Before assessment begins, the claim must be validated against the policy in force on the incident date, including cover type, sum insured and any exclusions. | REQ-1040 | Validated |
| TC-088 | REQ-1040 | Policy coverage validation against a policy endorsed after the incident datePrimary path — policy coverage validation | Functional | High | The outcome is identical to the primary path when the journey runs against a policy endorsed after the incident date. | REQ-1040 | Validated |
| TC-089 | REQ-1040 | A claim against an excluded peril must be refused with the exclusion namedValidation refusals — policy coverage validation | Negative | High | The action is refused and the message "This peril is excluded under the policy" is shown. No state is changed. | REQ-1040 | Validated |
| TC-090 | REQ-1040 | Coverage must not be validated against a policy version newer than the incident dateValidation refusals — policy coverage validation | Negative | High | The action is refused and the message "Policy version mismatch" is shown. No state is changed. | REQ-1040 | Validated |
| TC-091 | REQ-1041 | Deductible calculation is satisfied on the primary pathPrimary path — deductible calculation | Functional | High | The system behaves as REQ-1041 states: The deductible stated on the policy must be applied to the assessed amount before any payout is proposed, and shown to the claimant as a separate line. | REQ-1041 | Validated |
| TC-092 | REQ-1041 | Deductible calculation where the policy states a percentage deductiblePrimary path — deductible calculation | Functional | High | The outcome is identical to the primary path when the journey runs where the policy states a percentage deductible. | REQ-1041 | Validated |
| TC-093 | REQ-1041 | A deductible larger than the assessed amount must produce a nil payout, never a negative oneValidation refusals — deductible calculation | Negative | High | The action is refused and the message "Assessed amount is below the deductible" is shown. No state is changed. | REQ-1041 | Validated |
| TC-094 | REQ-1042 | Daily transaction limit is satisfied on the primary pathPrimary path — daily transaction limit | Functional | High | The system behaves as REQ-1042 states: Users must not be able to transact more than ₹50,000 within a rolling 24-hour period. | REQ-1042 | Validated |
| TC-095 | REQ-1042 | Daily transaction limit with the amount split across two transactions inside the same windowPrimary path — daily transaction limit | Functional | High | The outcome is identical to the primary path when the journey runs with the amount split across two transactions inside the same window. | REQ-1042 | Validated |
| TC-096 | REQ-1042 | Daily transaction limit submitted through the claims API rather than the portalPrimary path — daily transaction limit | Functional | High | The outcome is identical to the primary path when the journey runs submitted through the claims API rather than the portal. | REQ-1042 | Validated |
| TC-097 | REQ-1042 | Rolling 24-hour transaction total exactly at the limit (₹50,000)Boundary — rolling 24-hour transaction total | Boundary | High | ₹50,000 is accepted, because the limit is inclusive. | REQ-1042 | Validated |
| TC-098 | REQ-1042 | Rolling 24-hour transaction total just above the limit (₹50,001)Boundary — rolling 24-hour transaction total | Boundary | High | ₹50,001 is refused and the limit is stated in the message. | REQ-1042 | Validated |
| TC-099 | REQ-1042 | A transaction taking the rolling total above the limit must be refusedValidation refusals — daily transaction limit | Negative | High | The action is refused and the message "Transaction limit exceeded" is shown. No state is changed. | REQ-1042 | Validated |
| TC-100 | REQ-1042 | The rolling window must expire contributions older than 24 hoursValidation refusals — daily transaction limit | Negative | High | The action is refused and the message "Daily limit refreshed" is shown. No state is changed. | REQ-1042 | Validated |
| TC-101 | REQ-1042 | The limit must be enforced server-side, not only by the on-screen headroom displayValidation refusals — daily transaction limit | Negative | High | The action is refused and the message "Transaction limit exceeded" is shown. No state is changed. | REQ-1042 | Validated |
| TC-102 | REQ-1043 | Per-claim payout ceiling is satisfied on the primary pathPrimary path — per-claim payout ceiling | Functional | High | The system behaves as REQ-1043 states: A single claim must not settle above ₹2,00,000 without supervisor authorisation. | REQ-1043 | Validated |
| TC-103 | REQ-1043 | Per-claim payout ceiling where supervisor authorisation is grantedPrimary path — per-claim payout ceiling | Functional | High | The outcome is identical to the primary path when the journey runs where supervisor authorisation is granted. | REQ-1043 | Validated |
| TC-104 | REQ-1043 | Settlement amount on a single claim just below the limit (₹1,99,999)Boundary — settlement amount on a single claim | Boundary | High | ₹1,99,999 is accepted without warning. | REQ-1043 | Validated |
| TC-105 | REQ-1043 | Settlement amount on a single claim exactly at the limit (₹2,00,000)Boundary — settlement amount on a single claim | Boundary | High | ₹2,00,000 is accepted, because the limit is inclusive. | REQ-1043 | Validated |
| TC-106 | REQ-1043 | Settlement amount on a single claim just above the limit (₹2,00,001)Boundary — settlement amount on a single claim | Boundary | High | ₹2,00,001 is refused and the limit is stated in the message. | REQ-1043 | Validated |
| TC-107 | REQ-1043 | An adjuster must not settle above the ceiling without authorisationValidation refusals — per-claim payout ceiling | Negative | High | The action is refused and the message "Supervisor authorisation required" is shown. No state is changed. | REQ-1043 | Validated |
| TC-108 | REQ-1044 | Partial settlement is satisfied on the primary pathPrimary path — partial settlement | Functional | Medium | The system behaves as REQ-1044 states: An adjuster must be able to settle a claim partially, stating the settled and withheld amounts and the reason for the withholding, leaving the claim open. | REQ-1044 | Validated |
| TC-109 | REQ-1044 | Partial settlement where the withheld balance is later releasedPrimary path — partial settlement | Functional | Medium | The outcome is identical to the primary path when the journey runs where the withheld balance is later released. | REQ-1044 | Validated |
| TC-110 | REQ-1044 | A partial settlement without a withholding reason must be refusedValidation refusals — partial settlement | Negative | Medium | The action is refused and the message "State why the balance is withheld" is shown. No state is changed. | REQ-1044 | Validated |
| TC-111 | REQ-1044 | Adjuster access to REQ-1044 is exactly as specifiedRole boundaries — partial settlement | Permission | High | The adjuster can perform only the operations REQ-1044 grants that role; every other operation is refused. | REQ-1044 | Validated |
| TC-112 | REQ-1044 | Supervisor access to REQ-1044 is exactly as specifiedRole boundaries — partial settlement | Permission | High | The supervisor can perform only the operations REQ-1044 grants that role; every other operation is refused. | REQ-1044 | Validated |
| TC-113 | REQ-1045 | Adjuster assignment by workload is satisfied on the primary pathPrimary path — adjuster assignment by workload | Functional | Medium | The system behaves as REQ-1045 states: A validated claim must be assigned to the available adjuster with the lowest open workload who holds the relevant claim-type competency. | REQ-1045 | Validated |
| TC-114 | REQ-1045 | A claim must not be assigned to an adjuster marked unavailableValidation refusals — adjuster assignment by workload | Negative | Medium | The action is refused and the message "No adjuster available in this competency pool" is shown. No state is changed. | REQ-1045 | Validated |
| TC-115 | REQ-1045 | A claim must not be assigned outside the competency pool for its claim typeValidation refusals — adjuster assignment by workload | Negative | Medium | The action is refused and the message "No competent adjuster is available" is shown. No state is changed. | REQ-1045 | Validated |
| TC-116 | REQ-1046 | Fraud risk scoring and escalation is satisfied on the primary pathPrimary path — fraud risk scoring and escalation | Functional | High | The system behaves as REQ-1046 states: Every validated claim must receive a fraud risk score from 0 to 100. | REQ-1046 | Validated |
| TC-117 | REQ-1046 | Fraud risk scoring and escalation for a claim already in the investigation queuePrimary path — fraud risk scoring and escalation | Functional | High | The outcome is identical to the primary path when the journey runs for a claim already in the investigation queue. | REQ-1046 | Validated |
| TC-118 | REQ-1046 | Fraud risk score just below the limit (a score of 69)Boundary — fraud risk score | Boundary | High | a score of 69 does not trigger the threshold behaviour. | REQ-1046 | Validated |
| TC-119 | REQ-1046 | Fraud risk score exactly at the limit (a score of 70)Boundary — fraud risk score | Boundary | High | a score of 70 triggers the threshold behaviour, because the limit is inclusive. | REQ-1046 | Validated |
| TC-120 | REQ-1046 | Fraud risk score just above the limit (a score of 71)Boundary — fraud risk score | Boundary | High | a score of 71 triggers the threshold behaviour and the claim leaves straight-through processing. | REQ-1046 | Validated |
| TC-121 | REQ-1046 | A claim in the investigation queue must not be auto-settledValidation refusals — fraud risk scoring and escalation | Negative | High | The action is refused and the message "Claim is under investigation" is shown. No state is changed. | REQ-1046 | Validated |
| TC-122 | REQ-1047 | Escalation to a supervisor is satisfied on the primary pathPrimary path — escalation to a supervisor | Functional | Medium | The system behaves as REQ-1047 states: An adjuster must be able to escalate a claim to a supervisor with a stated reason. | REQ-1047 | Validated |
| TC-123 | REQ-1047 | Adjuster access to REQ-1047 is exactly as specifiedRole boundaries — escalation to a supervisor | Permission | High | The adjuster can perform only the operations REQ-1047 grants that role; every other operation is refused. | REQ-1047 | Validated |
| TC-124 | REQ-1047 | Supervisor access to REQ-1047 is exactly as specifiedRole boundaries — escalation to a supervisor | Permission | High | The supervisor can perform only the operations REQ-1047 grants that role; every other operation is refused. | REQ-1047 | Validated |
| TC-125 | REQ-1048 | Claim status notifications is satisfied on the primary pathPrimary path — claim status notifications | Functional | Medium | The system behaves as REQ-1048 states: The claimant must be notified by email and SMS on every status change, within 5 minutes, with the claim reference and the next expected step. | REQ-1048 | Validated |
| TC-126 | REQ-1048 | Claim status notifications on the SMS channelPrimary path — claim status notifications | Functional | Medium | The outcome is identical to the primary path when the journey runs on the SMS channel. | REQ-1048 | Validated |
| TC-127 | REQ-1048 | A failed notification must be retried and surfaced, never silently droppedValidation refusals — claim status notifications | Negative | Medium | The action is refused and the message "Notification delivery failed — retrying" is shown. No state is changed. | REQ-1048 | Validated |
| TC-128 | REQ-1049 | Settlement payment instruction is satisfied on the primary pathPrimary path — settlement payment instruction | Functional | High | The system behaves as REQ-1049 states: An approved settlement must generate a payment instruction containing the claim reference, payee bank details and the settled amount, and must not be generated twice for the same settlement. | REQ-1049 | Validated |
| TC-129 | REQ-1049 | Settlement payment instruction for a partial settlement instructionPrimary path — settlement payment instruction | Functional | High | The outcome is identical to the primary path when the journey runs for a partial settlement instruction. | REQ-1049 | Validated |
| TC-130 | REQ-1049 | A repeated instruction with the same idempotency key must not create a second paymentValidation refusals — settlement payment instruction | Negative | High | The action is refused and the message "Payment instruction already issued" is shown. No state is changed. | REQ-1049 | Validated |
| TC-131 | REQ-1049 | An instruction must not be generated without verified payee detailsValidation refusals — settlement payment instruction | Negative | High | The action is refused and the message "Payee details are unverified" is shown. No state is changed. | REQ-1049 | Validated |
| TC-132 | REQ-1050 | Audit log of claim decisions is satisfied on the primary pathPrimary path — audit log of claim decisions | Functional | High | The system behaves as REQ-1050 states: Every decision on a claim must be written to an append-only audit log recording the actor, the decision, the reason and the timestamp. | REQ-1050 | Validated |
| TC-133 | REQ-1050 | Audit log of claim decisions for a decision recorded by a supervisorPrimary path — audit log of claim decisions | Functional | High | The outcome is identical to the primary path when the journey runs for a decision recorded by a supervisor. | REQ-1050 | Validated |
| TC-134 | REQ-1050 | No role may edit or delete an audit entryValidation refusals — audit log of claim decisions | Negative | High | The action is refused and the message "Audit entries cannot be modified" is shown. No state is changed. | REQ-1050 | Validated |
| TC-135 | REQ-1050 | Auditor access to REQ-1050 is exactly as specifiedRole boundaries — audit log of claim decisions | Permission | High | The auditor can perform only the operations REQ-1050 grants that role; every other operation is refused. | REQ-1050 | Validated |
| TC-136 | REQ-1050 | Supervisor access to REQ-1050 is exactly as specifiedRole boundaries — audit log of claim decisions | Permission | High | The supervisor can perform only the operations REQ-1050 grants that role; every other operation is refused. | REQ-1050 | Validated |
| TC-137 | REQ-1051 | Regulatory claims export is satisfied on the primary pathPrimary path — regulatory claims export | Functional | High | The system behaves as REQ-1051 states: An auditor must be able to export all claims decided in a period, with decisions and timestamps, in the regulator's prescribed layout, without personal contact details. | REQ-1051 | Validated |
| TC-138 | REQ-1051 | Regulatory claims export for a period containing no decided claimsPrimary path — regulatory claims export | Functional | High | The outcome is identical to the primary path when the journey runs for a period containing no decided claims. | REQ-1051 | Validated |
| TC-139 | REQ-1051 | The export must not contain claimant contact detailsValidation refusals — regulatory claims export | Negative | High | The action is refused and the message "Contact fields are excluded from regulatory exports" is shown. No state is changed. | REQ-1051 | Validated |
| TC-140 | REQ-1051 | Auditor access to REQ-1051 is exactly as specifiedRole boundaries — regulatory claims export | Permission | High | The auditor can perform only the operations REQ-1051 grants that role; every other operation is refused. | REQ-1051 | Validated |
| TC-141 | REQ-1051 | Supervisor access to REQ-1051 is exactly as specifiedRole boundaries — regulatory claims export | Permission | High | The supervisor can perform only the operations REQ-1051 grants that role; every other operation is refused. | REQ-1051 | Validated |
| TC-142 | REQ-1052 | First response service level is satisfied on the primary pathPrimary path — first response service level | Functional | High | The system behaves as REQ-1052 states: A submitted claim must receive its first adjuster response within 48 hours. | REQ-1052 | Validated |
| TC-143 | REQ-1052 | Hours from submission to first adjuster response just below the limit (47 hours)Boundary — hours from submission to first adjuster response | Boundary | High | 47 hours is accepted without warning. | REQ-1052 | Validated |
| TC-144 | REQ-1052 | Hours from submission to first adjuster response exactly at the limit (48 hours)Boundary — hours from submission to first adjuster response | Boundary | High | 48 hours is accepted, because the limit is inclusive. | REQ-1052 | Validated |
| TC-145 | REQ-1052 | Hours from submission to first adjuster response just above the limit (49 hours)Boundary — hours from submission to first adjuster response | Boundary | High | 49 hours is refused and the limit is stated in the message. | REQ-1052 | Validated |
| TC-146 | REQ-1052 | A breached claim must not silently leave the at-risk queueValidation refusals — first response service level | Negative | High | The action is refused and the message "Service level breached" is shown. No state is changed. | REQ-1052 | Validated |
| TC-147 | REQ-1052 | Reassigning a claim must not reset its service-level clockValidation refusals — first response service level | Negative | High | The action is refused and the message "Service-level clock continues from submission" is shown. No state is changed. | REQ-1052 | Validated |