Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-3215

Use RetryRule in integration tests to avoid timing-related issues

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Won't Fix
    • None
    • None
    • Testing
    • None

    Description

      We should use the SLING-3212 retry rule in integration tests that assume things happen instantly, as this is not always the case.

      Tests need to be converted to JUnit4 style for that, SLING-3214 will help make that transition.

      Attachments

        Issue Links

          blocks

          Wish - General wishlist item. SLING-2788 Optionally run Sling on Apache OAK

          • Major - Major loss of function.
          • Resolved
          relates to

          New Feature - A new feature of the product, which has yet to be developed. SLING-3212 JUnit retry Rule, for integration tests mostly

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Unassigned Unassigned
              bdelacretaz Bertrand Delacretaz
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: