INTEGRATION TESTING

[jonbrunt]

Feature: Integration Tests

Description

This PR introduces integration testing for the site, as well as separating the execution of unit and integration tests depending on circumstance (push, PR, merge).

Changes

Frontend:

• Added test and integration dirs, and unit test file (navbarInteraction.int.test.tsx)
• Added integration tests for the site
• Added scripts to package.json to separate testing (unit and integration)
• Modified YAML file to execute unit tests always, and integration tests on PR and as part of branch protection

Testing

• Manual testing was conducted in the dev server/browser, and extensively in the terminal (manually calling new scripts)
• Unit tests pass
• Integration tests all pass

Notes

• This was done as one PR because adding integration testing naturally dictated an establishment of the separation of concerns for testing, resulting in the changes made to package.json, and unit test file names. e2e and snapshots will be implemented when further detail is added to the frontend (link and button functionality, actual content, etc).

Checklist

• [x] Code compiles correctly
• [x] All tests passing
• [x] No merge conflicts

Reviewers

Requesting review from @jonbrunt

Tags

#enhancement

[jonbrunt]

The integration tests are passing, but an error is being thrown regarding the window.scrollTo not being available in the Jest environment. I noticed this when reviewing the Actions log. We'll cover this functionality in subsequent e2e testing with Cypress, but can we mock the function to avoid this issue? It will save a bit of computing overhead. It is a detail, but it is key that we always try to reduce technical debt when feasible.

[jonbrunt]

Commit 478b327 solved the problem.

Will merge and delete the feature branch.