My company has bought 10 licenses for QCTO. But I have a feeling we will not be using it. Admittedly we are new to the product – but I have quite a bit of JUnit in Eclipse experience, and even I find the user interface baffling. I’m not asking people to “explain” it to me. Rather I thought I should say what I expect to find when I start it up.
Firstly, on start up, I expect it to display to me the tests that have been created in the schema I log in to. It does not; everything is focused on creating tests. That is important, sure, but by no means the most obvious bit. Indeed there is no menu option to do so. All that is displayed is a button to create new tests. I happen to know that all the tests address packages in another schema. I happen to know that in that schema, in pkg_common there are tests. But I cannot find this out unless I run a report or else try to create a new test for that package. And when I do the latter, it “helpfully” invites me to erase all the existing tests (which is horrifying, right there).
How do I suggest it should work?
Firstly, expect the install to be into a separate schema, in which the tests will live. No-one, no-one will want all the clutter in the same schema as the code, so this will be normal. If someone puts it in the same schema, fine, of course.
Secondly, on entry display the tests in the repository. Group them by package,function, etc, indicating the schema they are testing.
Thirdly, enough of the weird window processing. Do something like Eclipse/JUnit or Explorer.
Fourthly, consider how people might want to use this. They will probably want to run the tests against several different schemas. It should be simple to point the tests at schema1 on database 1, schema1 on database 2, etc. I couldn’t see how to do this.
Fifthly – if you’re interested in unit testing, you will want to run it in batch. I couldn’t work out how to do this. Get someone new to u/t to read the docs and comment on the WTF sections, because it doesn’t look nice at the moment.
Sixthly - think about source control for the tests. I presume one would do this on an xml export of the tests, but it is not clear that this is so.
I hope that helps. I really wanted to use this tool. But I just don’t see how I can recommend it. It’s good; just not mature enough.