1. OpenJPA
  2. OPENJPA-1071 Derby test suit speed-up
  3. OPENJPA-1194

LockManager tests call platformSpeedTest() for every test method


    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-M2
    • Fix Version/s: 2.0.0-M3
    • Component/s: None
    • Labels:


      The platformSpeedTest method is used to get a rough estimate of how fast the system is and from that determine how long we need to wait when running lock manager tests. It seems unlikely that this will change dramatically between test methods within a single class so it'd be better to find a way to cache the value without re-running the test.

      The test appears to be quick, but it's still largely wasted cycles.

      Unfortunately this is one of the areas where junit3 is limited - it's very tricky to initialize once per class (junit4 and testNG appear to be better at this), but we should be able to execute it only once per class.


        Michael Dick created issue -
        Michael Dick made changes -
        Field Original Value New Value
        Original Estimate 0h [ 0 ]
        Remaining Estimate 0h [ 0 ]
        Assignee Michael Dick [ mikedd ]
        Affects Version/s 2.0.0 [ 12314019 ]
        Michael Dick made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Donald Woods made changes -
        Fix Version/s 2.0.0-M3 [ 12314148 ]
        Affects Version/s 2.0.0-M2 [ 12313483 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        11d 1h 11m 1 Michael Dick 03/Aug/09 17:02


          • Assignee:
            Michael Dick
            Michael Dick
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: