- these are manually synced to/from the Louis
sftp://lalutest.ent.sirsi.net:822/web.Enterprise doesn't do version control, so this is a hack to accomplish version control. I literally sftp the contents of this folder back and forth from the Enterprise server, and git commit them in this repo.
- a screenshot of specific Enterprise pages as they appear without custom.js running. Annotation of function names from custom.js pointing to page locations they affect. (Expect this document to be inaccurate after custom.js is modified; but maybe it's somewhat helpful nonetheless.)
Functional Tests -- a suite of selenium-powered tests, to prevent regressions as we improve our SirsiDynex Enterprise view.
- in a python3 environment with selenium, pytest, and geckodriver:
cd ./FunctionalTestspytest- this will open a long sequence of browser windows (each without cache). I figure the benefit is worth the cost. Although it takes forever, you get the assurance that your browser cache isn't affecting any of the results.
- the only things tested are javascript or searchboxes that we at LSU coded. Anything coming from LOUIS or Sirsi is assumed to be perfect.
- you can test the production site (or the staging site) by changing the url in the ./FunctionalTests/test*.py files
- the tests will break occasionally due to the search index changing (this is ugly), but we need to test that the searchboxes work. Some tests send in a search query & test whether the results page contains a particular item. I don't know a better way to test a searchbox at the moment. We'll have to update the tests whenever they break due to a solr index change.