To test, install the latest ChromeDriver using brew install chromedriver --cask, which automatically adds it to your system's binary path. Run brew upgrade chromedriver each time you update your Google Chrome version to avoid compatibility issues between Selenium and ChromeDriver.
Next steps include writing tests for each module referenced in #361. Ensure that while running coldfront test, you have activated your virtual environment.
Update as of 1/5: Tests written for:
PI/manager role:
[X] Create a new allocation request
[X] Request change on an allocation
[X] Add/delete publication
[x] Add/delete research output
[X] Access project review
Incomplete PI tests due to Selenium quirks:
[ ] Add/delete grant (datepicker poses problem)
[ ] Add/remove user from project (checkbox is not clicking)
[ ] Add/remove user from allocation (checkbox is not clicking)
[ ] Renew allocation (need to figure out how to make allocation active but expiring in 60 days regardless of when tests are run)
Sys admin:
[X] Approve/deny allocation request
[X] Approve/deny allocation change request
[X] Remove 'allow changes' on allocation and verify PI can't request changes on it
To test, install the latest ChromeDriver using
brew install chromedriver --cask, which automatically adds it to your system's binary path. Runbrew upgrade chromedrivereach time you update your Google Chrome version to avoid compatibility issues between Selenium and ChromeDriver.Next steps include writing tests for each module referenced in #361. Ensure that while running
coldfront test, you have activated your virtual environment.Update as of 1/5: Tests written for:
PI/manager role:
Incomplete PI tests due to Selenium quirks:
Sys admin: