tests: cy howto read flaky

[tuliobluz]

PR Checklist

• - Commit messages are descriptive, it will be used in our Release Notes
• - Unit and e2e tests for the changes that have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix (fixes an issue)
• Feature (adds functionality)
• Code style update
• Refactoring (no functional changes)
• Build related changes
• CI related changes
• Documentation changes
• Other... Please describe:

What is the current behavior?

Currently, the scenario [Read a How-to][By Everyone][See all info] has flaky steps when trying to assert the data on the how-to. The cause is a rerender from a cypress that loses track.

Example:

assert expected <div.howto-description-container.css-703r4> to contain product

cypress cloud with the issue

What is the new behavior?

To avoid the page being rerendered I used the aliases

Does this PR introduce a breaking change?

• Yes
• No

[cypress]

onearmy-community-platform    Run #6263

Run Properties:   Failed #6263  •  7f5c946b5a: Merge branch 'master' into 3475-cy-howto-read-flaky

Project	onearmy-community-platform
Branch Review	pull/3861
Run status	Failed #6263
Run duration	04m 26s
Commit	7f5c946b5a: Merge branch 'master' into 3475-cy-howto-read-flaky
Committer	benfurber
View all properties for this run ↗︎

---

Test results
Failures	1
Flaky	2
Pending	0
Skipped	0
Passing	59
View all changes introduced in this branch ↗︎

---

Tests for review

  src/integration/questions/discussions.spec.ts • 1 failed test • ci-chrome

View Output Video

Test		Artifacts
[Questions.Discussions] > allows authenticated users to contribute to discussions		Test Replay Screenshots Video

  map.spec.ts • 1 flaky test • ci-chrome

View Output Video

Test		Artifacts
[Map] > [Shows expected pins]		Test Replay Screenshots Video

  howto/read.spec.ts • 1 flaky test • ci-chrome

View Output Video

Test		Artifacts
... > [See all info]		Test Replay Screenshots Video

[tuliobluz]

Before merging this PR, can you retry the e2e jobs to see if the flaky is still happening?

[mariojsnunes]

we haven't had flaky tests for a while

[tuliobluz]

For the previous runs 9/15 happened this flaky as you can see here.

[mariojsnunes]

Ah you are right, I was thinking about failed runs

[tuliobluz]

The test is still flaky, I will continue to investigate it.

[benfurber]

I'd be very suprised if removing this helps. If anything it probably needs time added to it.

[benfurber]

Also looks like the question discussion spec is more of a pain atm. I wonder if it's because of changes I made to the discussion data mocks recently.

[tuliobluz]

If I remember correctly, this issue has been happening for several months. I tried to investigate before. I attempted different approaches with Cypress but had no success. It might be related to how howto populate the tags.