Cresta / Cresta / Cresta e2e Cypress tests PublicBack to CI builds
You find here details about tests recorded for below git commit hash across 4 parallel CI nodes for Knapsack-Parallel-Test branch.
|Commit hash||Branch||Node total||Updated at||Created at|
|432ba56b56aba7e73cfd2d1594ab168a75b509d3||Knapsack-Parallel-Test||4||2020-08-11 16:34:02 UTC||2020-08-11 16:32:08 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 4 out of 4.
All CI nodes sent time execution data to Knapsack Pro API. Everything works!
The first CI node finished its work at 2020-08-11 16:32:08 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 3 minutes 38.622 seconds.
The time gap between the finish times of the CI node that Finished First and the one which Finished Last is 2 minutes 38.45 seconds
|Node Index||Created At||Time execution|
|0||2020-08-11 16:34:02 UTC||4 minutes 43.346 seconds|
|1 Finished First||2020-08-11 16:32:08 UTC||2 minutes 31.633 seconds|
|2 Finished Last||2020-08-11 16:34:46 UTC||3 minutes 52.666 seconds|
|3||2020-08-11 16:33:58 UTC||3 minutes 26.842 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|
|3c4eeb6d-c275-4d78-bc62-647012ef00d4||4||14 minutes 34.486 seconds||3 minutes 38.622 seconds||28.942 seconds|
|Test file path (10 files)||Time execution|
|cypress/integration/chat-header/messaging-chat-header.test.ts||2 minutes 33.206 seconds|
|cypress/integration/chat-with-messagingApi/login-and-send-message.test.ts||2 minutes 10.14 seconds|
|cypress/integration/SmartCompose/Smart-Compose.test.ts||1 minute 57.113 seconds|
|cypress/integration/Canned-Responses/Canned-Response.test.ts||1 minute 55.243 seconds|
|cypress/integration/login/login_to_hermes.test.ts||1 minute 38.845 seconds|
|cypress/integration/Suggestions/loginToHermes-Suggestions-test.ts||1 minute 37.846 seconds|
|cypress/integration/app-header/cresta_app_header.test.ts||1 minute 29.729 seconds|