-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathExploratoryTestingNotes.txt
More file actions
30 lines (26 loc) · 1.64 KB
/
ExploratoryTestingNotes.txt
File metadata and controls
30 lines (26 loc) · 1.64 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Creating new bookings
---------------------
Bookings can be created successfully.
All fields are mandatory, a booking cannot be created without First Name, Surname, Price, Deposit, Check-in, Check-out.
The date picker UI allows manual entry of a valid date.
Most invalid manually entered dates will not result in successful booking creation. One exception, see leap-year defect below.
A duplicate booking can be created successfully.
Possible Defects
A booking can be created with a negative price.
A booking can be created with an earlier check-out date than check-in date.
A booking can be created for a past period.
A booking can be created with a price to more than 2 decimal places.
A booking can be created with an invalid leap-year date, e.g. 2022-02-29, which results in a date of 2022-03-01 being used.
UX issues
Overall lack of styling and finish.
There is a noticeable delay between creating a booking and the booking appearing in the list of bookings, without any transient animated spinner.
The Deposit dropdown remains on the last option the user made when creating a booking, rather than returning to the first option.
The Check-out date picker does not limit choice to, nor default to, the Check-in date which would be convenient.
Cancelling bookings
-------------------
An existing booking can be successfully deleted.
Application architecture
------------------------
The application is quite 'chatty', making a REST call for existing booking IDs, followed by a subsequent call for details of each individual booking. A single call would seem appropriate.
The application is not secured by HTTPS.
The application is not secured by authentication.