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.
Summary: | "Test Results"-Window: double click on a failed test should focus the file ("Expected exception [...]") | ||
---|---|---|---|
Product: | php | Reporter: | daniela.waranie |
Component: | PHPUnit | Assignee: | issues@php <issues> |
Status: | NEW --- | ||
Severity: | normal | CC: | tmysik |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
daniela.waranie
2010-07-29 09:27:04 UTC
I now realized that on "Expected exception [...]" do not "jump to the file" AND do not "jump to the line" at all. I think it is because of the missing stack trace (line number). So it is no longer a bug. Now it is a feature request. On "Expected exception [...]" failures netbeans should jump to the line, where setExpectedException is defined within the failing test method. If this is not possible a jump to the line "[...] function <function name of the test>[...]" should happen. Would be nice to see this feature in the next release. Can you please verify how it works with Java project? Thanks. No, sorry. I am not a Java developer - i am a PHP developer. I am not sure, but i think the current behavior is the same for PHP and Java unit tests. For PHP a "jump to the setExpectedException method" would be best for me. On Java projects may be the above method have another name (depending on the unit test framework). So the general way is "to jump to the failing test methods first line", but in case of PHP i would like to see netbeans jump to the setExpectedException method line. Right click on the "Expected exception [...]" message (in the Test Results Window) showes a "Go to source" option in the context menu, but no action takes place. Right click on the "Expected exception [...]" message (in the Test Results Window) showes a "Go to source" option in the context menu, but no "jump to line" takes place. Right click on the "Failed asserting <null> is true." message (in the Test Results Window) showes a "Go to source" option in the context menu, too. And for that message netbeans jumps to the line. Maybe its because the stack trace is missing for "Expected exception [...]" messages... batch reassigning Hi, just for your information: PHPUnit 3.5.0RC2 and newer now returns the stacktrace when a unit test case did not fire an exception if an exception was expected (setExpectedException()). This makes the Netbeans 'Test Resuls'-windows be able to navigate to the code line as desired. Means: a solution when using PHPUnit is available. I am not sure if other frameworks (for PHP and/or Java) are printing a stacktrace in that case to the result xml, too. Please verify and close if other frameworks prints the stacktrace, too. I think it is solved in the actually nightly build... CLASSNAME::METHODNAME::METHODNAME with data set #0() Failed asserting that Array ( ) is of type "int". /Applications/xampp_very_old/xamppfiles/htdocs/project/tests/Frontend/User/Adapter/<Classname>.php:30 jumps to line 30 in classname.php, but the two methodnames in the title schould be fixed. |