I agree that the requirements for the realtime reporter should be visible somewhere. I suggest to include it in the preferences dialog. As a hint for the Use realtime reporter? option. Here's the preview:

This way it becomes clear, why a worksheet (instead of the fancy realtime reporter) is opened when running a test with utPLSQL v3.1.2. The user needs to open the preferences dialog, of course. But when the extension does not behave as expected, this is most probably something the user will do anyway.

Actually, I do not want to "pollute" the code put into the worksheet with warning messages. For several reasons.

• It uses more space.
  Currently the worksheet is automatically resized. 15% for the code (which usually needs 2-4 lines depending on the configuration) and 85% for the script output pane. This works quite well for most screen sizes, even if a reasonable sized log pane is visible at the bottom. Adding 3 additional lines will require a change of that logic as well.

• The worksheet does not know, if was called as a "second option"
  Even if you configure to use the realtime reporter, you can run tests in a worksheet. Using the worksheet to run tests is not deprecated. For the worksheet it is irrelevant which version of utPLSQL is used. In fact, it's currently even running when no utPLSQL is installed (see #64). To make the worksheet report warnings regarding the utPLSQL version it needs an additional call parameter. Something like calledByIntention. While this is possible, I do not like it. It feels wrong. It's not a feature a worksheet should provide.

• This would become a precedent
  There are other areas where we could but we do not provide warnings, regarding the utPLSQL version used. For example, the warnings within the realtime reporter. When you use a utPLSQL version 3.1.4 or 3.1.6 then no warning will be displayed. Never. In such a case we could populate a warning within the warning. But this will have an impact on the behavior of the realtime reporter. A no-go IMHO.

• The extensions works with utPLSQL v3.0.0 and higher
  This extension was designed to work with any utPLSQL 3 version providing a ut.version (see also #46). From a maintenance point of view I'd like to minimize the effort to achieve that. One action is to suppress warnings and informational message regarding how the extension could behave when another utPLSQL version would have been used.