Skip to content

Version 1.0.0

  • New

    • #6 - Run utPLSQL tests in a dedicated utPLSQL view
      • Realtime reporter as dockable window
      • Green progress bar while all tests succeed
      • Red progress bar when one or more tests failed or errored
      • Asynchronous test execution
      • Continuously updated test results (in near realtime)
      • Browse through test overview (keys Up, Down, PgUp, PgDn, Home, End or scroll wheel)
      • Open test package in the PL/SQL editor on double-click
      • Sort tests by status, indicators, suitepath/description, execution time
      • Reset sort order (by test execution)
      • Show common suitepath prefix in column header
      • Hyperlinks for code references in test details tabs (failures, errors, warnings and info)
      • Report warning and info messages on suite level in last test of a suite
      • Synchronize test details tab based on selected test and its status
      • Enable/disable counters per run (disabled, warnings, info)
      • Enable/disable indicators per test (warnings, info)
      • Enable/disable test description in overview
      • Run tests in parallel (is useful for independent tests only)
      • Rerun all tests (in same window or in a new worksheet)
      • Rerun selected tests (in same window or in a new worksheet)
      • History of last test runs
      • Clear history of last test runs (except currently selected run)
      • Requires utPLSQL v3.1.4 or higher (otherwise tests run in a worksheet)
    • Preferences
      • Use realtime reporter?
      • Realtime reporter preferences
        • Number of runs in history
        • Show disabled counter?
        • Show warnings counter?
        • Show info counter?
        • Show warning indicator?
        • Show info indicator?
        • Show description (if present)?
        • Synchronize detail tab based on test status?
  • Improved

    • Updated utPLSQL logo in context menu
    • Preferences grouped in tabs
      • Run utPLSQL test
      • Realtime Reporter
      • Generate utPLSQL test
      • oddgen
  • Fixed

    • #59 - Always use the utPLSQL annotation API to identify a test based on the cursor position within a PL/SQL editor
Assets 5
You can’t perform that action at this time.