tree: 0d83a521f9dc5b1fa208d6d382801bb98d43fd77 [path history] [tgz]
  1. cacheGroups/
  2. CDNs/
  3. common/
  4. deliveryServiceRequests/
  5. deliveryServices/
  6. divisions/
  7. login/
  8. parameters/
  9. physLocations/
  10. profiles/
  11. regions/
  12. serverCapabilities/
  13. servers/
  14. types/
  15. conf-delivery-service-requests.js
  16. conf.js
  17. README.md
traffic_portal/test/end_to_end/README.md

UI Tests

The Traffic Portal UI tests use Protractor, which thus must be installed prior to their execution. To run them, follow these steps:

  1. Start up Selenium Server - typically done with webdriver-manager start
  2. Make sure Traffic Portal is running (see the official documentation)
  3. Edit conf.js if necessary to match the environment (most notably ensure the port numbers match those in (../conf/conf.js and that the login credentials are correct).
  4. Run the tests - typically done with protractor conf.js

Errors with webdriver

Most errors with webdriver can be remedied by running:

$ webdriver-manager clean
$ webdriver-manager update