thanks for the quick answer. Overall, I quite like the tool - unit testing PL/SQL code could become much easier with it.
Responses to your responses below in blue.
- automatically select the correct schema when starting with /scommandline argument (if multiple schemata are referenced in thesuite: takethe first one)
When you say “select the correct schema”, I am not sure what you mean. The schema in which to connect to Oracle?
No. I have a separate schema MyTestSchema for my unit tests - the packages I want to test reside in our production schemata. But when I launch QuestCodeTester with /s MyTestSuite and MyTestSuite only contains tests for packages in MyProductionSchema, QuestCodeTester still shows MyTestSchema in the schema drop-down box in the Dashboard; I’d prefer it to select MyProduction schema automagically instead.
- make test-builder non-modal, so you don’t have to close test-builder when running your tests
Yes,this has been requested. It is on our list…and to be clear, are youmostly wanting to be able to run, see results, and go right back intoTB to do more changes?
Is there anything else you want to do while TB is still open? Iam not sure if we can/will do this soon, but we have made it easier togo immediately back into TB from the Viewer.
Yes, I normally run my test, check results and go immediately back to TB (usually because I managed to get my test definition wrong
Do you mean you want to be able to create suites within suites?
- stop test builder from automatically reformattingtheExpected/Got queries; I prefer having one field per line, and nolinebreaks in hard-coded string constants
You cannot do thisright now, it is true. So…can you tell me as specifically as possiblein which windows you want to disable formatting? Is it only query boxesor have you run across other places?
I didn’t realize you could customize the reformatting behaviour via Tools->Formatting preferences (thanks to Greg for pointing this out) - I’m absolutely content with this.
Thanks a lot & kind regards