v2.0 #427
v2.0 #427
Conversation
- Deprecate legacy tests format - Stop supporting cypress lt 6.7.0
- use group progress in hooks - properly count retries - types cleanup
- remove lookup for runs
|
I'm planning to use sorry-cypress in my project. I'm wondering if there can be any syntactical change from previous version so I should wait v2.0 to be launched. I'll be using Cypress 8.0.0 or higher in the project. |
The older runs (created prior to 2.0.0) would be partially visible - that's the only visible change I am aware of today. See example at https://sorry-cypress-demo.herokuapp.com/sorry-cypress/runs You can start using 2.0.0-beta.5 today - it is available via dockerhub:
|
|
On the speed you're doing the changes, I believe you'll finish the changes soon. Let me wait for a few days. Otherwise I'll start with beta version. Thanks |
|
@agoldis FYI, I tried out beta 6 on AWS and was getting some errors in, I think, the director. Sorry I reverted the version change as to not disrupt others so I can't go back and check after I got the screenshot and when trying to actually run Cypress |
|
@KyleThenTR thanks for discovering that, issued a fix in |
|
@agoldis things seem to be working well. One question/comment: wondering if the tests that show as Flaky status should be hidden when you toggle the Hide successful specs. Typically when I toggle that, I'm just looking for ones that are in a Failed status |
Makes sense, will fix |
|
@agoldis one other thing kind of related to the Flaky toggle, even though this spec had failed tests, it shows Flaky as the status over Failed. Would think Failed would override Flaky? |
Good catch! It is indeed |
- Properly show flaky vs passed vs failed - Update results for tests with exception
|
@KyleThenTR I have published 2.0.0-beta.9
|
v2.0
Breaking changes
Deprecated support for cypress agents lt
6.7.0The internal representation of runs has changed. Runs created prior to v2.0 might be displayed partially or not displayed at all.
progressfield onrunwith the instances and tests progress state. We use this field to report run's progress in hooks / dashboard instead of invoking complex MongoDB queries. This should resolve Webhooks to Github (maybe other hooks) stops reporting back at around 2600 tests #417 because we won't use MongoDB aggregations that create gt 16MB documents.runs.specswill have a short version of "results" - that would allow more efficient data fetching for showing runs feeds and individual runs.Other changes
PAGE_ITEMS_LIMITenv variable for API service