Some other comments since this is my first week with Code Tester. (I
have a few months of experience with utPLSQL.):
The “… single-byte character set …” has already become a nag and it is desirable to turn it off. I trust this limitation lies in the same category as others such as timestamp with time zone, interval etc. I.e. I can work around it for the limited situations where it hurts.
From the dashboard I continually use “Append test case…” (or ctrl-B) even when I am “editing” not appending. Should it be “Edit…”?
Most of my test case names are mindless. A nice configurable feature would be for the and text to be instead, the subprogram name followed by an underscore <#>. E.g. DAY_IN_DST_<#>.
The user flow for "Content of " isn’t smooth for me. I would default to the “Single value …” rather than null. I would split “Single value or expression” into two items – the “Evaluate as an expression” check box is a nuisance.
With utPLSQL I frequently am using the technique of the following snippet to avoid teardown so that I may inspect the final state (My setup calls my teardown. Also I have to do a prior utPLSQL init and run test for this to work.):
Is there a means to turn off teardown with Code Tester?
Displaying the SID would be helpful (configured off by default).
In addition to unit tests of APIs I have been developing test cases in response to defects. Typically these test cases are not against an API but rather they are against a multi-step process. In such cases, using utPLSQL, I have been developing stub test target package specs and bodies with no methods. In order to get Code Tester to engage in such a scenario I had to create a stub subprogram – a no method package yields “The selected program has no executable subprograms …” Opportunity lies here somewhere!
I haven’t yet discovered what the test case “Set” column (following Status and Name) means.
In general, I see the opportunity to expand Code Tester beyond unit test and into the subsystem test (string test) and simulation realm. I have no desire for multiple frameworks when the repository, dashboard and standardized assertions are already extant in Code Tester.
break (8) by kdavis
Message was edited by: kdavis