Predictive Test Selection
Time Savings
Every time you run only a subset of your test suite using Predictive Test Selection, you save time. This page shows how much test execution time you saved your team this month for this workspace. Learn more
| Month | PTS Test sessions | Total duration without Launchable | Total duration with Launchable | Time saved |
|---|---|---|---|---|
2022-09Not final yet | 342 | 84 hours | 22 hours | 62 hours (74%) |
2022-08Final | 867 | 237 hours | 95 hours | 143 hours (60%) |
2022-07Final | 937 | 358 hours | 215 hours | 143 hours (40%) |
2022-06Final | 1008 | 288 hours | 206 hours | 82 hours (29%) |
2022-05Final | 567 | 120 hours | 81 hours | 39 hours (33%) |
2022-04Final | 865 | 154 hours | 118 hours | 36 hours (23%) |
2022-03Final | 943 | 139 hours | 137 hours | 2 hours (2%) |
2022-02Final | 834 | 106 hours | 105 hours | 2 hours (2%) |
Useful info about this data
- A test session is not closed until 7 days after creation. Until then, you can record test results. Time Savings values are only official after that point. This means that it takes 7 days for last month’s values to finalize.
- In some cases, Total Duration With Launchable values may be different than total recorded test session duration values. Learn how these values are calculated
- In some cases, a test session may be excluded from the time savings calculation. Reasons for this include: 1) no tests were reported for the session, 2) too many recorded tests had no past history, and/or 3) the test session had too many subset requests.