Create an optimal launch schedule for your regression test suites that allows you to detect bugs faster using fewer computer resources.
Start by filling in the form and then click 'Calculate'.

Time period SINGLE SITE: If the project is on a single site and bugs only appear daytime, then select "12h". If you have two test suites then run the long test suite during the night when nobody works (requires no optimization) and only enter information about the shorter test suite here, leaving Test Suite 2 blank. Optimization should only take into account the daytime runs.

MULTI-SITE: If the project is a multi-site project with bugs appearing 24/7 then select "24h", "5 days" or "7 days". If you have two test suites enter information about both test suites below. The optimization process should take into account all test suites that are running within the specified time-period. However, if you have a test suite that only runs during weekends and people don't work during weekends then choose "5 days" and enter information about the other test suites that run during the week. Because there are no commits during weekends this run does not need to be optimized.

Test Suite 1

Test Suite 2

Test Suite Name Can be set to anything, e.g. "sanity".
(leave Test Suite 2 blank if you only have one test suite)

Test Suite Length (h) E.g "3" if it takes 3h for the test suite to complete
(leave Test Suite 2 blank if you only have one test suite)

Average Parallel CPU utilization E.g "100" if the test suite uses on average 100 CPU's in parallel. The default value is 1.

Functional Coverage (%) E.g. "40" if the coverage is 40%. The higher the coverage the better chance of detecting a bug.
(leave Test Suite 2 blank if you only have one test suite)

The Regression Test Scheduler is based on the paper "Optimal Usage of the Computer Farm" which was presented at DVCon US, San Jose, 2016. It was further enhanced for DAC 2016 where it was presented as a poster in the Design/IP Track.
Free to use, no warranties.

NEW! PinDown 4.2 is out now. PinDown can now automatically debug down to the line within a commit!