(UPDATE)
The previous PR has been closed due to a lot of modifications to the branch "e2e-automated-testing_Jeremie" and confusion. This is still the same PR with just another clean branch and up to date code with the master.
Description
This PR covers the system testing (e2e automated testing) of all user stories that were done in Sprint 2. Important to know that some parts of the code in this PR is tackling some system testing of sprint 3. To differentiate it, the specific files and scenarios will be mentioned below
Files
ExplorationTest.Spec.js
Scenarios
Scenario: Explore different campuses (US-6)
Scenario: Navigate through different indoor floors (Hall) (US-37)
Scenario: Get more details about a building (Hall building) (US: 7, 8, 9)
Scenario: Select a building as a destination point by typing its name (Hall building) (US-13)
Scenario: Select a building as a destination point by clicking on it (Hall building) (US-12)
Scenario: Select a building as a starting point by typing its name (EV building) (US-11)
Scenario: Search for a department/faculty by name (School of Irish Studies) (US-38)
Scenario: Search for a service by name (Welcome Crew) (US-39)
TODOS
All the TODOs visible in those scenarios are meant for future real fixes instead of workarounds. Note that the workarounds do test the functionality of the app, but present poor maintainability since they are very sensitive to UI changes.
(UPDATE) The previous PR has been closed due to a lot of modifications to the branch "e2e-automated-testing_Jeremie" and confusion. This is still the same PR with just another clean branch and up to date code with the master.
Description
This PR covers the system testing (e2e automated testing) of all user stories that were done in Sprint 2. Important to know that some parts of the code in this PR is tackling some system testing of sprint 3. To differentiate it, the specific files and scenarios will be mentioned below
Files
Scenarios
TODOS
All the TODOs visible in those scenarios are meant for future real fixes instead of workarounds. Note that the workarounds do test the functionality of the app, but present poor maintainability since they are very sensitive to UI changes.