Urban Routes Web App

Role: QA Engineer & Tester
Timeline: 2 days
Product description: The Urban Routes app is a user interface that provides transportation route selection and information on travel time and cost. Users can input their departure and destination, choose from three modes, “optimal”, “fastest”, and “custom”, and select different types of transport. The application processes user input, displays routes on the map, and provides error handling for invalid inputs.
Number of Test Cases: 28

Functional Requirements of Urban Routes

FR1:
The interface should have two input fields, labeled “From” and “To,” and three mode options, labeled “Optimal,” “Fastest,” and “Custom,” as well as icons for going on foot and other types of transport (the user’s car, car-sharing, taxi, scooter, or bicycle).

FR3:
The initial state of the fields that require input from users (”From” and “To”) should be empty. None of the three modes shall be selected, and the transport panel should be inactive.

FR2:
The user will enter the departure point and destination into the appropriate fields. Spaces should be allowed at the beginning and the end of the addresses; however, the system should delete those spaces when the mentioned fields are not in focus.

FR4:
In address fields, the software should only allow the user to enter numbers, spaces, dashes, periods, commas, and Latin characters in these fields. The maximum length of each address is 50 characters. Spaces at the beginning and end of addresses will be trimmed when the fields are not in focus. If the user enters invalid data in either field, the software should display the error message “Incorrect address.”

Requirements Analysis

Requirements broken were broken down into atomic blocks to prepare for test case creation. A total of 45 atomic blocks were created from the four requirements.

View documentation here

FR-1: (11)
“The interface should have two input fields, labeled “From” and “To,” and three mode options, labeled “Optimal,” “Fastest,” and “Custom,” as well as icons for going on foot and other types of transport (the user’s car, car-sharing, taxi, scooter, or bicycle).”

  • Check the input fields are labeled in the interface:

    • "From" input field in the interface

    • "To" input field in the interface

  • Check the mode options are labeled in the interface:

    • “Optimal” mode option in the interface

    • “Fastest” mode option in the interface

    • “Custom” mode option in the interface

  • Check icons for type of transport in the interface:

    • On foot icon in the interface

    • User’s car icon in the interface

    • Car-sharing icon in the interface

    • Taxi icon in the interface

    • Scooter icon in the interface

    • Bicycle icon in the interface

FR-2: (8)

“The user will enter the departure point and destination into the appropriate fields. Spaces should be allowed at the beginning and the end of the addresses; however, the system should delete those spaces when the mentioned fields are not in focus.”

  • Check the “Departure Point” and “Destination” are entered into appropriate fields:

    • Departure point is entered in “From” field

    • Destination is entered in “To” field

  • Check that spaces are allowed at the beginning and end of addresses:

    • System shall allow space at the beginning of the “From” field

    • System shall allow space at the beginning of the “To” field

    • System shall allow space at the end of the “From” field

    • System shall allow space at the end of the “To” field

  • Check that the system deletes spaces when fields are not in focus:

    • System shall delete spaces in “From” field when not in focus

    • System shall delete spaces in “To” field when not in focus

FR-3: (6)

“The initial state of the fields that require input from users (“From” and “To”) shall be empty. None of the three modes shall be selected and the transport panel shall be inactive.”

  • Check that the initial states of required fields are empty:

    • “From” field shall be empty in initial state

    • “To” field shall be empty in initial state

  • Check that no modes are selected in the initial state:

    • “Optimal” mode option shall be unselected in initial state

    • “Fastest” mode option shall be unselected in initial state

    • “Custom” mode option shall be unselected in initial state

  • Check that transport panel is inactive in initial state

    • Transport panel shall be inactive in initial state

FR-4: (20)

“In address fields, the software shall only allow the user to enter numbers, spaces, dashes, periods, commas, and Latin characters in these fields. The maximum length of each address is 50 characters. Spaces at the beginning and end of addresses will be trimmed when the fields are not in focus. If the user enters invalid data in either field, the software shall display the error message “Incorrect Address”.”

  • Check that system allows only valid characters in the “From” field:

    • Numbers 

    • Spaces

    • Dashes

    • Periods

    • Commas

    • Latin letters

  • Check that system allows only valid characters in the “To” field:

    • Numbers 

    • Spaces

    • Dashes

    • Periods

    • Commas

    • Latin letters

  • Check address meets maximum number of characters in input in the fields:

    • “To” address has a maximum of 50 characters

    • “From” address has a maximum of 50 characters

  • Check that spaces are trimmed when fields are not in focus:

    • Space trimmed at beginning of “From” field when not in focus

    • Space trimmed at end of “From” field when not in focus

    • Space trimmed at beginning of “To” field when not in focus

    • Space trimmed at end of “To” field when not in focus

  • Check that error message “Incorrect Address” is displayed when invalid data is entered in fields: 

    • “Incorrect Address” error message is displayed when invalid data is entered in “From” field

    • “Incorrect Address” error message is displayed when invalid data is entered in “To” field

Test Case Creation

View documentation here

Test Execution