[#1220] Cypress: test ramp chart in zoom view

[ckcherry23]

Fixes #1220

Proposed commit message

Currently, there are very few tests for the ramp chart component of 
RepoSense. One aspect that is not tested is whether the ramps shown in 
the ramp chart are correct for the timeframe provided.

Let us make our front-end tests more robust by adding cypress tests to 
check whether the ramps shown in the ramp chart of the zoom view 
correspond with the commits from the selected time period. Let us also
test other aspects of the ramp chart like ramp properties, relative 
distances between ramps and links.

Other information

For this PR, I check whether the ramp chart corresponds with the selected timeframe by checking if the number of ramps is equal to the number of commit messages. Therefore the confidence level of these tests depends on the correctness of the filtering of commit messages.

For the other tests, one downside is that a lot of them are hardcoded or skipped as the values cannot be correctly estimated using conventional Cypress test methods. I will be exploring the use of jQuery methods to make these test cases more robust.

[ckcherry23]

The frontend tests are failing due to the new merge commits made and can be fixed by merging #1882.

[vvidday]

LGTM! I think that it would be important to add tests to test for the correctness of the filtering of commit messages, as these tests rely on the correctness of those (as you mentioned) e.g. setting date/zoom range in summary panel correctly filters commits in zoom panel.

I'll open a separate issue/PR for that!

[zhoukerrr]

@ckcherry23 More test cases are always welcomed and the test cases added are certainly useful. However, I think other test cases could be added to make this test file more powerful. I am not too sure if it is possible to cover cases regarding the width, start/end date, link to the commit, relative distance between each ramp. Would you mind exploring if any of those are possible?

If there are other areas of testing that you think we can add, feel free to add on. If the ones that I mentioned above are not possible to do/not worth the effort, do share below and feel free to discuss!

[ckcherry23]

I am not too sure if it is possible to cover cases regarding the width, start/end date, link to the commit, relative distance between each ramp. Would you mind exploring if any of those are possible?

Though the initial purpose of this PR was just to test if the ramp chart matches the selected timeframe, I agree that more tests need to be added for the ramp charts. However, many of these properties are difficult to test and some values like ramp width and distance may even change between platforms, even if the viewport size is the same.

While I have added a few test cases with hardcoded expected values, I will explore if there are ways to test these in a more robust manner.

[zhoukerrr]

LGTM! I do agree with your point. But I think these hardcoded test cases do add value as a sanity check for future updates.

[github-actions]

The following links are for previewing this pull request:

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