Tests run in NB are not transactional!!!

[Chris Nelson]

Ok, found something very scary just now. Running my unit test in
NetBeans resulted in data being left around in my test db, where as
running from the command line resulted in the correct transactional
behaviour. The earlier bug I saw was bad enough, but this one is
much, much worse. Please, is there a way to get rid of the new test
runner entirely? It seems like it is not ready for alpha (or even to
be checked into source control at all) let alone beta. Is there an
easy way to just run my test case (as before) without the new and
decidedly unimproved test runner deciding to kick in and mess
everything up?

Thanks in advance,

Chris

[Erno Mononen]

Chris,

Sorry to hear you're having problems with the test runner. You can
disable it by:

1. delete <netbeans install
dir>/ruby2/modules/org-netbeans-modules-ruby-testrunner.jar
2. restart the IDE
3. click OK in the dialog that warns you about the testrunner module not
being found

This will cause the IDE to run tests as it did in 6.1.

If you want to help, please file an issue at
http://www.netbeans.org/issues/enter_bug.cgi against the ruby/testing
component with enough information to reproduce:

- how did you run the test in the IDE
- how did you run the from test the command line (the exact command)
- Rails version
- Ruby version
- Operating system

Best would be if you can create a simple project where you see the
problem, or at least an example of a test case that fails for you.
Likely I will need the IDE log too
(http://wiki.netbeans.org/FaqRubyNBLogging).

Also, make sure you are using a recent build instead of Beta. Since we
don't have 6.5 RC1 builds available yet,
http://bits.netbeans.org/dev/nightly/2008-10-14_14-01-18/ is probably
the best bet at the moment (later builds contain new features for 7.0).

I'd very much appreciate if you file the issue so that we can track down
the problem.

TIA,
Erno

Chris Nelson wrote:

[Chris Nelson]

Oops, I replied to the wrong message. Please see my other post for
details and a solution.

--Chris

On Sat, Oct 18, 2008 at 4:12 PM, Erno Mononen <address-removed> wrote:

[Chris Nelson]

Also, created an issue(150626) and attached code to fix there.

On Sat, Oct 18, 2008 at 11:08 PM, Chris Nelson
<address-removed> wrote:

[Erno Mononen]

Thanks a lot both for finding the culprit and for the fix! That's really
helpful. Can you please attach the patch once more to the issue
(apparently you attached some other file by accident).

Thanks again,
Erno


Chris Nelson wrote:

[Chris Nelson]

Don't know what happened the first attempt, but I attached my fixed
version to the issue again and it appeared to work this time. Was too
lazy to patch so it's just a complete copy of nb_test_mediator.rb with
fix applied. Shoud be easy enough to diff though.

--Chris

On Mon, Oct 20, 2008 at 2:56 AM, Erno Mononen <address-removed> wrote: