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 191788 - Rails 3 Projects: test summary and test navigation tree not seeing tests
Summary: Rails 3 Projects: test summary and test navigation tree not seeing tests
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Testing (show other bugs)
Version: 7.0
Hardware: PC Windows 7 x64
: P3 normal with 2 votes (vote)
Assignee: issues@ruby
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2010-11-10 11:57 UTC by RobNichols
Modified: 2011-01-28 20:14 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The attached screen shot shows both testing problems (16.75 KB, image/png)
2010-11-10 11:57 UTC, RobNichols
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RobNichols 2010-11-10 11:57:38 UTC
Created attachment 102878 [details]
The attached screen shot shows both testing problems

When running tests of Rails 3 applications, the Test Results panel is not detected the tests. There are two outcomes to this:

1. The summary of the test is incorrect. It always shows that the test finished in 0.0 Seconds and that there were no tests.

2. The left navigation pane of the test results window does not display any of the tests. Instead it just shows "No tests executed. (0.0 s).

This problem only affects Rails 3 applications. Rails 2 application still test normally. This bug is also present in Netbeans 6.9.1

The attached screen shot shows both problems. As you can see, immediately above the test summary, the rake test output clearly shows that 56 test have been run. In fact, this is just the output from the functional tests. Further up in the test output the output from the unit test stage of the output shows that an additional 116 unit tests were completed as part of this test.

Running the test outside NetBeans via rake at the command prompt behaves normally
Comment 1 jours 2010-12-01 22:15:58 UTC
Priority of this should be increased - this bug causes the code coverage report to fail as well when running All Tests.