Test various front-end components

[nandhinibsn]

Resolve #

Description:

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• FRONTEND TYPES. Regenerate the front-ent types if you played with types and routes.
  Run cd webapp && yarn types while the back-end is running.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[gabegma]

Is this PR still relevant @nandhinibsn@JosephMarinier? It's been open for 4 months. Maybe we could prioritize it if we have some slack this sprint?

[JosephMarinier]

I renamed the PR to take testing the performance analysis table out of its scope. This PR has waited long enough now and those tests will be beneficial.

[JosephMarinier]

I think you mean

Suggested change

	it("should not display the Footer component if the number of rows are lesser than initial number", async () => {
	it("should not display the Footer component if the number of rows is less than initial number", async () => {

but I'm not following. What initial number? The test doesn't manipulate anything, so I guess this is the initial number of rows, not less. Can you help me understand?

[nandhinibsn]

I meant the same "INITIAL_NUMBER_VISIBLE = 5", as we mentioned in our logic. This test case will check if there should be no footer component displayed. The mock response that was added is at most four rows.

[JosephMarinier]

Got it, thanks!

[JosephMarinier]

Cool! Thanks for doing that!