-
Notifications
You must be signed in to change notification settings - Fork 1
End to end testing using Protractor! A Detailed Guide step by step including bugs
###Things before running tests:
1: All tests were performed using the Chrome browser. I cannot guarantee that they will work on other browsers.
2: The webpage MUST be in full screen mode, errors occur otherwise.
3: Please do not interact with the webpage launched by the tests.
4: Seemingly irrelevant details that may impact tests; tests were ran only on a 4k resolution.
###How to download, set up, and run the tests.
###Known (bugs?) oddities with testing:
Sometimes (random 50% chance) there will be an issue with the tests that raises the following message (or something quite similar).
- Search Test functioning input of ditype Message: UnknownError: unknown error: Element is not clickable at point (761, 578). Other element would receive the click:
or
- Search Test submitting a postdoc appointment Message: ElementNotVisibleError: element not visible
This is due to the fact that in the submit page there is a clickable dropdown box that must be clicked. Protractor seems to not click it at seemingly random times. However, the code is there and it does function the other 50% of the time without issue. Unsure how to resolve.
Overall when these elements have errors they cause errors throughout the entire submit page testing (Which yes, is very concerning), despite the tests having had previously worked during creation.