Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 0.1.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Currently, a hard-wired timeout is used for all tests. However, some tests need more time than others. For example, the large content tests need many minutes per test to complete, but other tests only need several seconds. When these shorter tests fail or get stuck, it is not helpful to wait for a ridiculously long time because one test needs it.

      It might be helpful to provide each test with a command-line parameter to set the timeout for that test. If not specified on the command-line, each test should provide a reasonable default for that test based on the time required for slower machines.

        Attachments

          Activity

            People

            • Assignee:
              kpvdr Kim van der Riet
              Reporter:
              kpvdr Kim van der Riet
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: