Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1764

Rewrite stress.multi as a JUnit test

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 10.5.1.1
    • Test
    • None

    Description

      Currently, stress.multi consists of a number of sql scripts that are run in ij. It often fails with cryptic error messages, and since it uses ij, there is often no stack trace. It would be very useful to rewrite the test in JUnit so that we can get better error messages and stack traces when it fails.

      Attachments

        1. DERBY-1764_4.diff
          9 kB
          Erlend Birkenes
        2. DERBY-1764_5.diff
          10 kB
          Erlend Birkenes
        3. DERBY-1764_6.diff
          0.9 kB
          Erlend Birkenes
        4. DERBY-1764_8_Use_DatabasePropertiesTestSetup.diff
          3 kB
          Erlend Birkenes
        5. DERBY-1764_sysprops_diff.txt
          8 kB
          Katherine Marsden
        6. derby-1764_use_System_PropertySetup_diff.txt
          2 kB
          Katherine Marsden
        7. derby-1764-3a-whitespace_changes.diff
          31 kB
          Kristian Waagan
        8. derby-1764-derby.log
          3.45 MB
          Bryan Pendleton
        9. DERBY-1764-Review.diff
          17 kB
          Erlend Birkenes
        10. DERBY-1764-V1.diff
          22 kB
          Erlend Birkenes
        11. DERBY-1764-V2.diff
          68 kB
          Erlend Birkenes

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ebirkenes Erlend Birkenes
            knutanders Knut Anders Hatlen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment