Comments on: Qute – new Unit Testing Engine for PL/SQL (successor for utPLSQL) https://technology.amis.nl/2006/02/06/qute-new-unit-testing-engine-for-plsql-successor-for-utplsql/ Friends of Oracle and Java Mon, 27 Apr 2015 11:47:05 +0000 hourly 1 http://wordpress.org/?v=4.2 By: jabbinho https://technology.amis.nl/2006/02/06/qute-new-unit-testing-engine-for-plsql-successor-for-utplsql/#comment-2880 Tue, 11 Jan 2011 11:11:09 +0000 http://technology.amis.nl/blog/?p=1041#comment-2880 Has QUTE been discontinued?  The URLs to UNIT-TEST.COM don’t work.

]]>
By: Lucas Jellema https://technology.amis.nl/2006/02/06/qute-new-unit-testing-engine-for-plsql-successor-for-utplsql/#comment-2879 Thu, 02 Mar 2006 09:35:55 +0000 http://technology.amis.nl/blog/?p=1041#comment-2879 On 1st March, the 1.0.4 release of Qute was made available from http://www.unit-test.com/download.php.

New/fixed in Qute 1.0.4

An attempt to import a test definition from a file will verify that you have execute authority on the object tested by that harness.

You can now ask Qute to recompile an invalid program unit or test package from within the test harness properties form.

“Hash mismatch” errors have been fixed by improving the hashing algorithm for GUIDs.

You can now tell Qute to avoid calling the Java classes to parse PL/SQL code, by checking the appropriate box in Preferences. This is necessary in some operating systems, where the lack of a Java runtime environment causes an un-trappable ORA-00600 error.

Examples are no longer installed with Qute. We are revamping the approach taken with examples.

You can now choose to continue the installation of Qute even if we detect that you may not have sufficient privileges.

Press Cancel or Escape on login form will no longer close Qute.

Default directory and other Preference settings are now saved between Qute sessions.

Run Test logic to determine when to recommend generation of test package code has now been improved.

Error handling in test packages has now been improved to display that error information in the Results tab. You can also copy the error text into the clipboard.

Assertion code for string-indexed collections now works properly.

Next up for Qute: easier outcome definitions

We [the Qute team] are now focusing our attention on making it much easier to define outcomes for your tests. The current approach (selecting from assertion types like “EQ” and “EQTABLE”) grew out of my experience with utPLSQL, and I have found it to be too limiting.

In our next iteration, you will be able to: construct your outcome in a more intuitive, flexible, powerful way; and review/modify the customization and assertion code that Qute will generate for that outcome.

]]>
By: Steven Feuerstein https://technology.amis.nl/2006/02/06/qute-new-unit-testing-engine-for-plsql-successor-for-utplsql/#comment-2878 Wed, 15 Feb 2006 16:03:17 +0000 http://technology.amis.nl/blog/?p=1041#comment-2878 Keith,

First, generally, I encourage you to post issues, bugs, ideas about Qute at the following URL:

http://www.unit-test.com/contact.php

so we can address them. Please remember: this is a pre-production product. There are still lots of bugs and if you report them, we can fix them!

And now some questions and comments:

* Have you downloaded the latest version, 1.0.3? That should fix the problem of importing utPLSQL scripts.

* What have you been using to “generate test cases using utpLsql”?

* You can certainly define test cases even if you don’t have return values, but you will need to then drill down to individual test cases to finish the test definition.

* What do you mean by “delete more than one item”? We are, by the way, revamping the Add Test Harness interface to make it much easier to use.

* The “No arguments with interesting values…” should only appear when you select Generate Test Cases, which works with interesting values supplied in the test elements for a unit. It should not appear when you try to run a test definition.

I look forward to hearing from you through the contact page or by emailing me at steven@stevenfeuerstein.com.

Thanks, SF

]]>
By: Keith Novak https://technology.amis.nl/2006/02/06/qute-new-unit-testing-engine-for-plsql-successor-for-utplsql/#comment-2877 Thu, 09 Feb 2006 17:37:56 +0000 http://technology.amis.nl/blog/?p=1041#comment-2877 I just spent the last two weeks generating test cases using utplsql. It has worked rather well although I agree you do generate a lot of code. Using QUTE I tried importing utplsql but nothing is showing up – bummer. The “add test harness” screen only allows you to set up initial return values -if what you are testing has return values. Otherwise I have to go into the individual test cases to set it up – which isn’t convenient.
Also it would be nice to delete more than one item from the “add test harness” screen.
I also haven’t been able to get a test to run successfully – I keep getting “No arguments with interesting values defined”. I not sure what i’m doing wrong…

]]>
By: Steven Feuerstein https://technology.amis.nl/2006/02/06/qute-new-unit-testing-engine-for-plsql-successor-for-utplsql/#comment-2876 Mon, 06 Feb 2006 13:05:11 +0000 http://technology.amis.nl/blog/?p=1041#comment-2876 Lucas,

Thanks very much for letting people know about Qute! Perhaps I will direct people here to get a little tutorial/intro on using the tool!

Also, I would like to let readers know that they can watch presentations by following these instructions:

You will need to play these webinars from Internet Explorer; you can verify that your browser and computer are compatible for these recordings by visiting this URL:

http://giles.bcimeeting.com/imtapp/system_check/SystemChecker.exe

Introduction to Qute
http://giles.bcimeeting.com/imtapp/app/arc_pb_hub.uix?mID=370868&src=app/arc_pub&action=pb

Using Qute to test PL/SQL collections
http://giles.bcimeeting.com/imtapp/app/arc_pb_hub.uix?mID=370887&src=app/arc_pub&action=pb

Using Qute to test cursor variables
http://giles.bcimeeting.com/imtapp/app/arc_pb_hub.uix?mID=370938&src=app/arc_pub&action=pb
These presentations will soon be available from the website.

]]>