Delivery Challan Wizard — Testing and Issue Reporting Story¶

1. User Story¶

As a tester / business analyst,
I want to validate the Delivery Challan Wizard's user guidance, workflow, PDF output, and field validations,
So that usability gaps and functional defects are documented clearly and can be addressed by the developer before the wizard is considered ready for use.

2. Work Completed¶

The Delivery Challan Wizard was tested from a functional and user-interface perspective. Eight issues were identified, documented in the Delivery Challan Wizard — Issue List, and forwarded to the developer for review and resolution.

Scope of the reported findings: user guidance, PDF download, PDF alignment, terminology, and field/date validation.

Status note: The source issue list records the defects identified and states that they were forwarded to the developer. It does not confirm that the fixes have been implemented or retested.

3. Issues Identified¶

4. Testing Workflow¶

flowchart TD
    A[Open Delivery Challan Wizard] --> B[Review step instructions and procedure]
    B --> C[Continue an existing Delivery Challan]
    C --> D[Check Sub Type validation]
    D --> E[Validate Estimated Return Date and DC Date]
    E --> F[Approve Delivery Challan]
    F --> G[Test PDF download]
    G --> H[Review PDF alignment for Dispatched & Awaiting Return]
    H --> I[Record and consolidate issues]
    I --> J[Forward issue list to developer]
    J --> K[Developer fixes and retesting]

The final step, developer fixes and retesting, is the expected follow-up workflow; the provided issue list does not establish that this step has already occurred.

5. Functional Areas Covered¶

5.1 User guidance and usability¶

• Checked whether the wizard explains the action required at each step.
• Identified the absence of an overall procedure explanation and descriptions of the available options.

5.2 Approval and PDF output¶

• Tested PDF download after Delivery Challan approval.
• Identified a PDF alignment issue that occurs in some cases for the “Dispatched & Awaiting Return” status.

5.3 Field and date validation¶

• Identified validation being applied to the non-mandatory Sub Type field when continuing an existing Delivery Challan.
• Identified that Estimated Return Date accepts both past and future dates, despite the need for a defined business-rule restriction.
• Identified that DC Date accepts future dates.

5.4 UI terminology¶

• Identified a terminology/spelling correction in Step 4, “Movement Details”: change “Dispatch” to “Despatch,” as recorded in the issue list.

6. Acceptance Criteria for Developer Resolution¶

The following criteria translate the reported issues into verifiable outcomes. Date rules should be confirmed with the business owner where the source issue list does not specify the exact rule.

• Each wizard step explains the user action required.
• The wizard explains the overall Delivery Challan process and the meaning of its options.
• An approved Delivery Challan PDF can be downloaded successfully.
• PDF alignment is correct for the “Dispatched & Awaiting Return” status, including cases where the issue was observed.
• Step 4 uses “Despatch” instead of “Dispatch.”
• A blank, non-mandatory Sub Type does not incorrectly block continuation of an existing Delivery Challan.
• Estimated Return Date follows the confirmed business rule for permitted dates.
• DC Date rejects future dates.
• Each reported issue is retested after the developer's changes, and the result is recorded.

7. Developer Handoff¶

The eight findings were consolidated in the source document Delivery_Challan_Wizard_Issue_List (1).docx and forwarded to the developer.

Recommended handoff details for each defect:

1. Issue number and title.
2. Steps to reproduce.
3. Actual behavior.
4. Expected behavior.
5. Screenshot or sample record/PDF, where applicable.
6. Developer resolution status.
7. Retest result and evidence.

The supplied issue list does not include reproduction steps, screenshots, developer responses, severity, or resolution status. These details should be added during defect triage or retesting rather than assumed.

8. Definition of Done¶

This testing task can be considered complete when:

• All eight reported issues have been reviewed by the developer.
• Fixes or intended behavior have been confirmed for each issue.
• The relevant scenarios have been retested.
• Any unresolved defects are documented with their current status.
• The final test outcome is recorded.

9. Summary of Contribution¶

Tested the Delivery Challan Wizard for functional behavior and user-interface usability, identified and documented eight issues spanning guidance, PDF download and alignment, terminology, and field/date validation, and forwarded the consolidated issue list to the developer for resolution.

Evidence reviewed: Delivery Challan Wizard — Issue List: Functional and UI Validation Issues (one-page document).