[#1931] Update frontend integration tests for summary and zoom view

[germainelee02]

Fixes #1931

On the frontend, changes in the summary panel affect the zoom 
panel. However, this functionality is not well tested in our current 
Cypress tests.

Let's add additional Cypress tests for the changing of zoom and date 
range.

[github-actions]

The following links are for previewing this pull request:

• Dashboard Preview: https://dashboard-2015-pr-reposense-reposense.surge.sh
• Docs Preview: https://docs-2015-pr-reposense-reposense.surge.sh

[vvidday]

Thanks for taking this up @germainelee02 and apologies for the late response.

I understand that the nature of these tests might make it necessary to make certain assumptions about the data in the report which might result in some hardcoding of the test actions/values.

Would it be possible to indicate whenever there's an assumption regarding the data in the comments like this? Since the tests that rely on assumptions/hardcoded data might fail in the future if the test repo gets more commits, and it would be easier for future maintainers to know exactly what assumptions are being made in the tests.

[vvidday]

LGTM

[ckcherry23]

Nice work on abstracting out common functionalities and the test coverage is also good.

Would it be possible to add test cases for some more functionalities?

• setting the 'granularity' changes the zoom view
• setting the 'granularity' again results in a different zoom view
• filtering by a certain file type changes the zoom view
• filtering by a different file type results in a different zoom view

Possible suggestions

[germainelee02]

Nice work on abstracting out common functionalities and the test coverage is also good.

Would it be possible to add test cases for some more functionalities?

• setting the 'granularity' changes the zoom view
• setting the 'granularity' again results in a different zoom view
• filtering by a certain file type changes the zoom view
• filtering by a different file type results in a different zoom view

Should I make a separate PR for that then? @ckcherry23

[ckcherry23]

Should I make a separate PR for that then? @ckcherry23

@nseah21 I think this can be done in the same PR, as they have the same purpose of testing whether changes in the summary panel are reflected in the zoom panel.

[github-actions]

Hi,
We are going to mark this PR as stale because it has been inactive for the past 30 days.
If no further activity occurs within the following 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 7 days and leave a comment to remove the stale label.
Do let us know if you are stuck so that we can help you!'

[ckcherry23]

@germainelee02 I will approve this for now, and add a new issue for the suggested test cases.
Please take up that issue if you would like.

[github-actions]

The following links are for previewing this pull request:

• Dashboard Preview: https://dashboard-2015-pr-reposense-reposense.surge.sh
• Docs Preview: https://docs-2015-pr-reposense-reposense.surge.sh