Knapsack Pro

DEV Community (dev.to) / dev.to / Cypress tests / Build ID d991361a-f5d2-4517-b685-5e2e61408787

Build Details

Back to CI builds

Public
Commit hash Branch Nodes Tests execution time Created at
6c03cfd refs/pull/20761/merge 8 17 minutes 55.74 seconds   2024-03-11 21:04:33 UTC

Parallel CI nodes

All parallel CI nodes finished their work.

The time span between the finish times of the CI node that Finished First and the one which Finished Last is 30 minutes 57.89 seconds. The shorter this time is, the better.

Loading...

Parallel CI nodes

The first CI node finished its work at 2024-03-11 21:08:01 UTC. CI nodes that finished at least 60s later are highlighted.

The reason for slow CI nodes might be too large test files (see the Test Files tab). You may want to try the Knapsack Pro Queue Mode (Ruby) to improve the distribution of your tests. Learn more about dynamic test suite split here.

Note: if you run a CI build for the same commit again (for instance when you retry a CI build), then you will see the data updated below. Some of the nodes might be highlighted until the whole CI build is complete.

The average test execution time per CI node is 2 minutes 14.47 seconds.

The time span between the finish times of the CI node that Finished First and the one which Finished Last is 30 minutes 57.89 seconds. The shorter this time is, the better.

Node index Finish time Tests execution time (17 minutes 55.74 seconds)
0 2024-03-11 21:08:10 UTC 2 minutes 21.78 seconds
1 2024-03-11 21:08:02 UTC 2 minutes 8.43 seconds
2 2024-03-11 21:08:05 UTC 2 minutes 31.81 seconds
3 Finished First 2024-03-11 21:08:01 UTC 2 minutes 13.12 seconds
4 Finished Last 2024-03-11 21:38:58 UTC 2 minutes 20.24 seconds
5 2024-03-11 21:08:12 UTC 1 minute 55.66 seconds
6 2024-03-11 21:08:09 UTC 2 minutes 18.01 seconds
7 2024-03-11 21:08:05 UTC 2 minutes 6.72 seconds

Test Files recorded on parallel CI nodes

You can likely decrease your CI build time by around 15 seconds by running more parallel CI nodes.

Running 9 parallel nodes should result in an optimal build time (~1.99 minutes)


Test file path (Displaying entries 101 - 121 of 121 in total files) Execution time
cypress/e2e/seededFlows/adminFlows/apps/editListingCategory.spec.js 3.19 seconds 1% Trend
cypress/e2e/seededFlows/homeFeedFlows/timeFixer.spec.js 3.18 seconds 3% Trend
cypress/e2e/seededFlows/adminFlows/users/gdprDeleteRequests.spec.js 3.09 seconds 24% Trend
cypress/e2e/seededFlows/profileFlows/followOrganisation.spec.js 3.08 seconds 75% Trend
cypress/e2e/seededFlows/notificationsFlows/followUserFromNotifications.spec.js 3.05 seconds 2% Trend
cypress/e2e/seededFlows/adminFlows/navigationLinks/navigationLinks.spec.js 2.96 seconds 6% Trend
cypress/e2e/seededFlows/adminFlows/config/emailServerSettingsSection.spec.js 2.96 seconds 20% Trend
cypress/e2e/seededFlows/adminFlows/users/navigateTabs.spec.js 2.9 seconds 24% Trend
cypress/e2e/seededFlows/adminFlows/consumerApps/createConsumerApp.spec.js 2.6 seconds 30% Trend
cypress/e2e/seededFlows/registrationFlows/emailRegistration.spec.js 2.4 seconds Trend
cypress/e2e/seededFlows/settingsFlows/updateProfileSettings.spec.js 2.28 seconds 29% Trend
cypress/e2e/seededFlows/loggedOutFlows/homeFeed.spec.js 2.23 seconds 21% Trend
cypress/e2e/seededFlows/adminFlows/config/ahoySection.spec.js 2.18 seconds 35% Trend
cypress/e2e/seededFlows/loggedOutFlows/tagIndex.spec.js 2.04 seconds 12% Trend
cypress/e2e/seededFlows/articleFlows/seriesFlows/previewProfileFromSeries.spec.js 1.94 seconds 44% Trend
cypress/e2e/seededFlows/searchFlows/searchForm.spec.js 1.79 seconds 14% Trend
cypress/e2e/seededFlows/toggleFeatureFlags.spec.js 332 miliseconds Trend
cypress/e2e/seededFlows/homeFeedFlows/events.spec.js 152 miliseconds 10% Trend
cypress/e2e/seededFlows/dashboardFlows/dashboardNavigation.spec.js 128 miliseconds 6% Trend
cypress/e2e/seededFlows/podcastFlows/togglePodcastPlayback.spec.js 111 miliseconds 6% Trend
cypress/e2e/seededFlows/homeFeedFlows/profilePreviewCards.spec.js 107 miliseconds Trend

Start using Knapsack Pro

Sign up and speed up your tests.