ABCDEFGHIJKLMNOPQRSTUVWXY
1
Checklist and test results for the Random Date Generator app
2
3
#DescriptionStatusLink to bug report/
4
Functional Testing
5
Date Generation
6
1Verify the app generates random dates by clicking "Generate Random Date" without modifying any input fields.PASSED
7
2Confirm that generated dates are displayed in the default format.PASSED
8
Custom Date Count "How many dates to generate?)
9
3Enter a specific number of dates in "How many dates to generate?" and verify that the app generates exactly that number.PASSED
10
4 Test with valid boundary values (1- 999999) to ensure the app can handle edge cases.PASSED
11
5Test with invalid boundary values (-1, 0, 1000000) to ensure the app displays a clear error message (e.g., 'Please enter a valid number') and prevents date generation for invalid inputsFAILEDBug ID# RDG-1 on the bug report: https://docs.google.com/spreadsheets/d/1jieIuvsAFWA88TQ9Sp9N5J2lt6lwbmyga0p4_ZU844g/edit?gid=0#gid=0
12
13
Date Output Format
14
6Verify that each format in the "Date output format" dropdown generates dates in the selected format.FAILEDBug ID# RDG-2 on the bug report: https://docs.google.com/spreadsheets/d/1jieIuvsAFWA88TQ9Sp9N5J2lt6lwbmyga0p4_ZU844g/edit?gid=0#gid=0
15
7Test custom date format by entering values in "Custom date format" (e.g., YYYY-MM-DD) and check if dates are generated as specified.PASSED
16
Date Range (Start-End Date)
17
8Confirm user can enter start and end date with MM-DD-YYYY format ( 01-29-2000 to 01-31-2000)PASSED
18
9Confirm user can enter start and end date with YYYY-MM-DD format ( 01-29-2000 to 01-31-2000) PASSED
19
10Confirm user can enter start and end date with YYYY-DD-MM format ( 01-29-2000 to 01-31-2000) **FAILED** This is not a bug but need improvement. See more in this link: https://docs.google.com/document/d/13G4DOVbPlG6iGIeBCK476YrXlEDFKL24T3Dx5CgF_6c/edit?usp=sharing
20
11Confirm when enter the right format ( 01-29-2000 to 01-31-2000), it generates in the right range PASSED
21
12Test date boundary value for YYYY (999999,1000000,0000,0001)**FAILED** This is not a bug but need improvement. See more in this link: https://docs.google.com/document/d/13G4DOVbPlG6iGIeBCK476YrXlEDFKL24T3Dx5CgF_6c/edit?usp=sharing
22
13Test date boundary value for MM (-1, 0,1,12,13)PASSED
23
14Test date boundary value for DD (-1,0,1,30,31,32) matching with 30 days month and 31 day month and generate the right rangeFAILEDBug ID# RDG-3 on the bug report: https://docs.google.com/spreadsheets/d/1jieIuvsAFWA88TQ9Sp9N5J2lt6lwbmyga0p4_ZU844g/edit?gid=0#gid=0
24
15Verify leap year handling by setting the start date to 02-27-2000 and the end date to 02-30-2000, ensuring the app correctly generates February 29th for the leap year. **FAILED** This is not a bug but need improvement. See more in this link: https://docs.google.com/document/d/13G4DOVbPlG6iGIeBCK476YrXlEDFKL24T3Dx5CgF_6c/edit?usp=sharing
25
16Verify the behavior when the start date is later than the end date (e.g., 12-31-2025 to 01-01-2020). The application should display an error message and prevent date generation when the start date is later than the end date.FAILEDBug ID# RDG-4 on the bug report: https://docs.google.com/spreadsheets/d/1jieIuvsAFWA88TQ9Sp9N5J2lt6lwbmyga0p4_ZU844g/edit?gid=0#gid=0
26
17Test with non-date values in the start and end date fields to confirm the app rejects invalid inputs.**FAILED** This is not a bug but need improvement. See more in this link: https://docs.google.com/document/d/13G4DOVbPlG6iGIeBCK476YrXlEDFKL24T3Dx5CgF_6c/edit?usp=sharing
27
Copy Functionality
28
19Click the copy button after generating dates and paste the copied content to verify that it matches the generated dates.PASSED
29
Download Functionality
30
20Click the download button to save generated dates and verify the file downloads correctly.PASSED
31
21Open the downloaded file and confirm that it contains the generated dates in the correct format.PASSED
32
Non-Functional Testing
33
Performance
34
22Measure response time for generating dates (e.g., 10, 100, 1000 dates) to check if it's within acceptable limits.PASSED
35
23Test with a high date count (e.g., 1000) and verify the app remains responsive.PASSED
36
Accessibility Testing
37
Keyboard Navigation
38
24Ensure all fields and buttons are accessible and operable using only the keyboard (e.g., using the "Tab" key).PASSED
39
25Verify each button and field is focusable and can be activated via keyboard input.PASSED
40
Screen Reader Compatibility
41
26Test with a screen reader to confirm that all UI elements (buttons, input fields, labels) are announced clearly.PASSED
42
27Ensure each field has a meaningful label or description for screen reader users.PASSED
43
Contrast and Visibility
44
28Check that the text and background colors meet contrast ratio standards for accessibility (e.g., WCAG standards).FAILEDBug ID# RDG-5 on the bug report: https://docs.google.com/spreadsheets/d/1jieIuvsAFWA88TQ9Sp9N5J2lt6lwbmyga0p4_ZU844g/edit?gid=0#gid=0
45
29Verify that generated dates are easy to read without visual strain.PASSED
46
Usability Testing
47
User Guidance
48
30Check if each input field has an intuitive label, tooltip, or instruction for users unfamiliar with date formats.PASSED
49
31Verify that error messages (if any) are clear and helpful, guiding users to correct any input issues.FAILEDBug ID# RDG-6 on the bug report: https://docs.google.com/spreadsheets/d/1jieIuvsAFWA88TQ9Sp9N5J2lt6lwbmyga0p4_ZU844g/edit?gid=0#gid=0
50
Overall Layout
51
32Ensure the app layout is logical and user-friendly, with input fields and buttons easy to locate and understand.PASSED
52
33Confirm that buttons (e.g., "Generate Random Date," "Copy," "Download") are clearly labeled and distinguishable.PASSED
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100