Hi @stianst - thank for looking into this. The model tests cover both the old and the new store, so the flag ci-new-store to run the model tests is IMHO misleading.

So suggest: Either rename ci-new-store to ci-store, or remove the condition store-model-tests

Hi @stianst - thank for looking into this. The model tests cover both the old and the new store, so the flag ci-new-store to run the model tests is IMHO misleading.

So suggest: Either rename ci-new-store to ci-store, or remove the condition store-model-tests

Was half thinking to run all store testing conditionally. What do you think about that?

I can rename to ci-store regardless I'd say?

@stianst - running legacy-store-integration-tests on that condition would work for me as well. I assume the tests will run in the main CI on schedule still.

@stianst - running legacy-store-integration-tests on that condition would work for me as well. I assume the tests will run in the main CI on schedule still.

Yup, this only applies for pull requests events, everything run for all other events

2 flaky tests on run #8297 ↗︎

0

527

48

0

2

Details:

  authentication_test.spec.ts • 1 flaky test • chrome

View Output Video

Test		Artifacts
Authentication test > should add a condition		Output Screenshots

  realm_settings_events_test.spec.ts • 1 flaky test • chrome

View Output Video

Test		Artifacts
Realm settings events tab tests > Should remove event from event listener		Output Screenshots

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}