Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-3002

Add tests.iter.min to improve controlling tests.iter's behavior

    XMLWordPrintableJSON

Details

    • Test
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 3.2, 4.0-ALPHA
    • general/test
    • None
    • New, Patch Available

    Description

      As discussed here: http://lucene.472066.n3.nabble.com/Stop-iterating-if-testsFailed-td2747426.html, this issue proposes to add tests.iter.min in order to allow one better control over how many iterations are run:

      • Keep tests.iter as it is today
      • Add tests.iter.min (default to tests.iter) to denote that at least N instances of the test should run until there's either a failure or tests.iter is reached.

      If one wants to run until the first failure, he can set tests.iter.min=1 and tests.iter=X – up to X instances of the test will run, until the first failure.

      Similarly, one can set tests.iter=N to denote that at least N instances should run, regardless if there were failures, but if after N runs a failure occurred, the test should stop.

      Note: unlike what's proposed on the thread, tests.iter.max is dropped from this proposal as it's exactly like tests.iter, so no point in having two similar parameters.

      I will work on a patch tomorrow.

      Attachments

        1. LUCENE-3002.patch
          4 kB
          Shai Erera

        Activity

          People

            shaie Shai Erera
            shaie Shai Erera
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: