This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 107738

Summary:	autotest integration enhancements
Product:	ruby	Reporter:	dinsley <dinsley>
Component:	Testing	Assignee:	issues@ruby <issues>
Status:	REOPENED ---
Severity:	blocker	CC:	developster
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description dinsley 2007-06-21 23:18:46 UTC

Feedback when the tests are passing would be good as well, I would suggest a green bar in the status bar but then the
status bar would become kind of useless for anything else as it would constantly be updating with the failure/success
messages.

Something in the toolbar, or below the status bar like red/green 'orbs' with the project name to indicate the autotest
or test/unit status would be absolutely awesome. (something like the Continuous Integration plugin that works with
CruiseControl and the one you guys use for the ruby builds!)

Comment 1 Jiri Kovalsky 2007-07-03 14:06:15 UTC

Reassigning this issue to newly created 'ruby' component.

Comment 2 Erno Mononen 2009-03-11 14:01:19 UTC

Autotest is now run through the UI test runner, which should fix this issue -- please reopen if that is not what you're
looking after. Thanks.

Comment 3 developster 2009-03-16 21:10:40 UTC

Autotest in UI Test runner looks really nice but I miss the ability of autotest to show difference between expected and
actual results. Now it just shows expected and actual on the same line.

Also couldn't be the progress indicator disabled just for autotest? Because this progress bar is stealing your attention
from real thing.

Comment 4 Erno Mononen 2009-03-17 15:07:35 UTC

There is a diff viewer for comparison failures in 6.7 builds (see the last paragraph at http://blogs.sun.com/emononen/
entry/new_features), is that what you're looking for?

Comment 5 developster 2009-03-17 23:36:58 UTC

That dialog does the diff, but you know, you have to click (I mean to take hands off the keyboard) and see what is
different. The dialog is useful, but I thought of a simpler diff like does ZenTest (my version is 3.11.1).

An example how does ZenTest:
10) Failure:
test_script_valid(TestAlterColumnType) [./test/test_pg_diff.rb:27]:
--- /tmp/expect.5384.9	2009-03-18 00:26:54.000000000 +0200
+++ /tmp/butwas.5384.9	2009-03-18 00:26:54.000000000 +0200
@@ -1,3 +1,3 @@
 ALTER TABLE testtable
-  ALTER COLUMN field1 TYPE INTEGER,
-  ALTER COLUMN field3 TYPE CHARACTER VARYING(150);
+  ;
+  ;

An example how does autotest in nb:
10) Failure:
test_script_valid(TestAlterColumnType):
<"ALTER TABLE testtable\n  ALTER COLUMN field1 TYPE INTEGER,\n  ALTER COLUMN field3 TYPE CHARACTER VARYING(150);">
expected but was <"ALTER TABLE testtable\n  ;\n  ;">.
./test/test_pg_diff.rb:27:in `test_script_valid'

Comment 6 developster 2009-03-18 22:24:44 UTC

I see that ZenTest achieves this diff using unit_diff. When it launches test script '| unit_diff -u' is appended to the
end of command.