Knapsack Pro

DEV Community (dev.to) / dev.to / Cypress tests / Build ID ed51604a-4598-4cc6-a344-4bc0bfeed17c

Build Details

Back to CI builds

Public
Commit hash Branch Nodes Tests execution time Created at
618dc07 refs/pull/20862/merge 8 18 minutes 25.3 seconds   3% 2024-04-15 14:17:56 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 18 minutes 25.64 seconds. The shorter this time is, the better.

Loading...

Parallel CI nodes

The first CI node finished its work at 2024-04-15 14:21:45 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 18.17 seconds.

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

Node index Finish time Tests execution time (18 minutes 25.3 seconds)
0 2024-04-15 14:21:46 UTC 2 minutes 38.25 seconds
1 2024-04-15 14:21:54 UTC 2 minutes 31.53 seconds
2 Finished First 2024-04-15 14:21:45 UTC 2 minutes 33.68 seconds
3 2024-04-15 14:21:51 UTC 2 minutes 22.83 seconds
4 2024-04-15 14:21:46 UTC 2 minutes 33.92 seconds
5 2024-04-15 14:21:56 UTC 2 minutes 31.9 seconds
6 Finished Last 2024-04-15 14:40:11 UTC 1 minute 10.39 seconds
7 2024-04-15 14:21:47 UTC 2 minutes 2.82 seconds

Test Files recorded on parallel CI nodes

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

Running 10 parallel nodes should result in an optimal build time (~1.84 minutes)


Test file path (Displaying entries 101 - 121 of 121 in total files) Execution time
cypress/e2e/seededFlows/listingFlows/viewListing.spec.js 3.55 seconds 12% Trend
cypress/e2e/seededFlows/settingsFlows/updateProfileSettings.spec.js 3.54 seconds 9% Trend
cypress/e2e/seededFlows/dashboardFlows/managePost.spec.js 3.49 seconds 6% Trend
cypress/e2e/seededFlows/profileFlows/organisationStats.spec.js 3.48 seconds 3% Trend
cypress/e2e/seededFlows/adminFlows/config/userExperienceSection.spec.js 3.46 seconds 13% Trend
cypress/e2e/seededFlows/adminFlows/apps/editListingCategory.spec.js 3.19 seconds 1% Trend
cypress/e2e/seededFlows/notificationsFlows/followUserFromNotifications.spec.js 3.18 seconds 6% Trend
cypress/e2e/seededFlows/adminFlows/navigationLinks/navigationLinks.spec.js 3.13 seconds 12% Trend
cypress/e2e/seededFlows/adminFlows/users/gdprDeleteRequests.spec.js 3.07 seconds 25% Trend
cypress/e2e/seededFlows/podcastFlows/followPodcast.spec.js 3.03 seconds 18% Trend
cypress/e2e/seededFlows/tagsFlows/editTag.spec.js 2.62 seconds 23% Trend
cypress/e2e/seededFlows/registrationFlows/emailRegistration.spec.js 2.54 seconds 5% Trend
cypress/e2e/seededFlows/loggedOutFlows/homeFeed.spec.js 2.16 seconds 17% Trend
cypress/e2e/seededFlows/loggedOutFlows/tagIndex.spec.js 2.08 seconds 14% Trend
cypress/e2e/seededFlows/searchFlows/searchForm.spec.js 1.92 seconds 23% Trend
cypress/e2e/seededFlows/adminFlows/organizations/manageOrganizations.spec.js 1.9 seconds 45% Trend
cypress/e2e/seededFlows/toggleFeatureFlags.spec.js 366 miliseconds 11% Trend
cypress/e2e/seededFlows/homeFeedFlows/events.spec.js 155 miliseconds 13% Trend
cypress/e2e/seededFlows/dashboardFlows/dashboardNavigation.spec.js 131 miliseconds 9% Trend
cypress/e2e/seededFlows/podcastFlows/togglePodcastPlayback.spec.js 110 miliseconds 5% Trend
cypress/e2e/seededFlows/homeFeedFlows/profilePreviewCards.spec.js 109 miliseconds 1% Trend

Start using Knapsack Pro

Sign up and speed up your tests.