Cresta / Cresta / Cresta e2e Cypress tests PublicBack to CI builds
You find here details about tests recorded for below git commit hash across 9 parallel CI nodes for Knapsack-Parallel-Test branch.
|Commit hash||Branch||Node total||Updated at||Created at|
|2c8c96e8bbff150da49418f56ba0d8504e4594d9||Knapsack-Parallel-Test||9||2020-08-11 17:15:28 UTC||2020-08-11 17:13:01 UTC|
Here you can check if all parallel CI nodes recorded tests timing data.
When you re-run CI build or run a new CI build for the same commit & branch & node total number, then the data below will be updated.
Collected Build Subsets 9 out of 9.
All CI nodes sent time execution data to Knapsack Pro API. Everything works!
When one of your CI nodes has a time execution of 0, it means that other CI nodes had already executed all tests so that CI node had no work to do. It could happen when you use the Queue Mode and one of the CI nodes started later - at a time when other CI nodes had already completed all of the work.
The first CI node finished its work at 2020-08-11 17:13:01 UTC. CI nodes that finished at least 60s later are highlighted.
The reason for slow CI nodes might be too large test files (you can see the slowest test files at the bottom of the page when all CI nodes collected time execution data). You may want to try Knapsack Pro Queue Mode (Ruby) to solve a problem with the random performance of test files or your CI nodes. Learn more about dynamic test suite split here.
Note: if you run CI build for the same commit again (for instance when you retry CI build), then you will see build subsets updated below. Until retried CI build finishes work you may see highlighted build subsets.
Average time execution per collected CI node is 1 minute 12.969 seconds.
The time gap between the finish times of the CI node that Finished First and the one which Finished Last is 2 minutes 35.535 seconds
|Node Index||Created At||Time execution|
|0||2020-08-11 17:13:29 UTC||1 minute 19.625 seconds|
|1||2020-08-11 17:14:40 UTC||1 minute 53.516 seconds|
|2||2020-08-11 17:14:45 UTC||2 minutes 4.716 seconds|
|3||2020-08-11 17:13:06 UTC||0 seconds|
|4||2020-08-11 17:14:36 UTC||1 minute 20.362 seconds|
|5||2020-08-11 17:15:28 UTC||1 minute 28.664 seconds|
|6||2020-08-11 17:13:03 UTC||0 seconds|
|7 Finished First||2020-08-11 17:13:01 UTC||33.86 seconds|
|8 Finished Last||2020-08-11 17:15:37 UTC||2 minutes 15.978 seconds|
Build Distribution ID is the ID for the test suite split. You can see this ID in knapsack_pro logs as a test suite split seed.
Total time execution is sum of tests' execution times recorded across all parallel CI nodes.
Node max time execution is an estimated average time of running tests per CI node.
Distance is a time gap between average CI node time execution and the slowest CI node. The lower the better.
|Build Distribution ID||Node total||Total time execution||Node max time execution||Distance|
|44c6438a-7b56-4ce0-b047-969d0f882ffb||9||10 minutes 56.721 seconds||1 minute 12.969 seconds||51.748 seconds|
The slow test files are highlighted in yellow below.
Test files with higher time execution than 1 minute 12.969 seconds are bottleneck because they take more time than expected execution time per parallel CI node.
Please check how to improve test suite split for the slowest test files.
|Test file path (9 files)||Time execution|
|cypress/integration/chat-with-messagingApi/login-and-send-message.test.ts||2 minutes 4.716 seconds|
|cypress/integration/Canned-Responses/Canned-Response.test.ts||1 minute 56.978 seconds|
|cypress/integration/SmartCompose/Smart-Compose.test.ts||1 minute 28.664 seconds|
|cypress/integration/login/login_to_hermes.test.ts||1 minute 22.666 seconds|
|cypress/integration/Suggestions/loginToHermes-Suggestions-test.ts||1 minute 20.362 seconds|
|cypress/integration/app-header/cresta_app_header.test.ts||1 minute 19.625 seconds|