I have developed an algorithm that aims to produce some scientific results. These calculcations use a lot of computing time, so most runs use a much faster, stripped-down version of the algorithm. At some point, real runs are necessary for which a lot of time will be commited.

What would you call these runs that are not test runs? Live runs maybe?

  • 1
    "Crash" is what I usually encounter. But "live run" fits, more or less. – Hot Licks May 24 '15 at 17:14
  • 1
    Since they're probably all "tests", perhaps you should just differentiate them as stripped-down (or preliminary) tests and full tests. – FumbleFingers May 24 '15 at 17:48
  • Could you clarify? Which one are you calling the test run? The longer one or the shorter one? – Tushar Raj May 24 '15 at 17:48
  • I'm calling the shorter runs test, i.e. those where I don't expect useful results. – helm May 24 '15 at 23:02

In many environments a run that actually produces results is a production run. Working run, or some variant of Live run, real run or actual run might also work.


If the Final run is called Test,
my scanner labels something similar a preview. Or perhaps,


.3. to move or pass quickly, forcefully, or smoothly

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.