End to end testing of display of events using Selenium

[roslynwythe]

Overview

We need to explore the use of automated browser testing tools for ensuring end to end functionality of the website in order to verify the display of meetings on Project pages.

Details

In this issue, a test will be developed in JavaScript using Selenium browser automation and the Mocha testing frameworks.

Action Items

• Read Getting "Started with Selenium"¹ and "Mocha (Getting Started)"²
• If not already installed, install node.js and npm https://docs.npmjs.com/downloading-and-installing-node-js-and-npm
• In the test folder, create a folder e2e, then from test/e2e, run npm init -y to create a new package
• Install Selenium and configure dependencies as described in Install a Selenium Library¹
• Install Mocha as described in Mocha Installation²
• Run docker-compose up to start the jekyll server.
• In test/e2e, create a JavaScript file meetings-on-project-pages.js, using Selenium WebDriver and Mocha to load each project page and verify display of meeting information. See Selenium example³
  • The list of project page URLs to test should be generated dynamically from the jekyll _projects collection using liquid. For sample code see the function retrieveProjectDataFromCollection() in assets\js\current-projects.js
  • During test, the website will be served from http://localhost:4000 so create urls appropriately
• Run the script using Mocha. Optionally, define an npm script alias
  • Verify that the script reports a passing test on pages in which meetings are displayed, and a failing test on pages in which meetings are not displayed
• Add/Commit all 3 files in test/e2e: meetings-on-project-pages.js, package.json and package-lock.json
• Proceed with creating a pull request. In the pull request, provide instructions for reviewers to install and run the tests

Footnotes

1. https://www.selenium.dev/documentation/webdriver/getting_started/install_library/ ↩ ↩²

2. https://mochajs.org/#installation ↩ ↩²

3. Organizing and Executing Selenium Code - Test Runner Examples: JavaScript ↩

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels