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.
Although it happens on at least 2 machines (Windows 7 + dev build and 8.1 beta / Windows 10 with beta and rc1), I can't find any duplicate for this. JUnit test results simply aren't displayed. If I manually open the test results window, it's just empty. This has been like this since 8.1 July or August builds Tests run normally. My projects are multi-module mvn projects. I usually run tests with CTRL-F6 or right-clicking (whole file or 'focused method'). I can collaborate for details if needed.
Please reopen attaching ide's log file and some sample project that shows the issue as I cannot reproduce. Thank you
Created attachment 156678 [details] simple project with simple test
Created attachment 156679 [details] ide log Here it is. Please note that it now works on the same machine, in RC1, which didn't import my user configuration and seemed to recreate it. Still, that means I have to redefine everything: project groups, maven settings, other settings etc.. So, this is a workaround but it doesn't solve the problem.
I cannot reproduce it either. If I open the attached NbJunitBroken project and hit Ctrl+F6 on either the project node or NewEmptyJUnitTest.java, NetBeans runs the test, build succeeds and notification shows up for a few seconds allowing me to open the results window. If I click the link, "Test Results" output panel is displayed with green progress bar saying that "Tests passed: 100%". All this is as designed. Tested in: Product Version: NetBeans IDE 8.1 RC2 (Build 201510122201) Java: 1.8.0_60; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-b27 System: Linux version 3.13.0-37-generic running on amd64; UTF-8; cs_CZ (nb)
It does work on a RC1 install with clean user directory. On DEV/Beta/RC1 with existing user directory, I just can't have any test results. I can provide you with my user settings if that helps.
(In reply to ymajoros from comment #5) > It does work on a RC1 install with clean user directory. > > On DEV/Beta/RC1 with existing user directory, I just can't have any test > results. > > I can provide you with my user settings if that helps. so, it seems there is some problem with your user settings. You can zip it and attach it here for further investigation. Thank you
Please reopen when attaching the settings in question from comment 5. Thank you
I'd like to send my user settings, but I'm concerned with passwords or sensitive information that could be in it. Do you have some email address where I can send it privately?
Please either use theofanis [dot] oikonomou [at] oracle [dot] com or jiri [dot] kovalsky [at] oracle [dot] com. Thanks!
(In reply to ymajoros from comment #8) > I'd like to send my user settings, but I'm concerned with passwords or > sensitive information that could be in it. Do you have some email address > where I can send it privately? No need to worry actually. When you export your user settings you can just uncheck the "Keyring & Passwords" category. That way no such info will be included in the zip file. You can actually check in any case before attaching it here to be 100% sure :)
How do you export them? I thought I needed to copy my user folder.
"Tools > Options" from main menu, then "Export..." button.
Created attachment 156820 [details] nb settings
Product Version: NetBeans IDE 8.1 RC2 (Build 201510122201) Java: 1.8.0_60; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-b27 System: Linux version 3.13.0-37-generic running on amd64; UTF-8; cs_CZ (nb) I cannot reproduce it. I have imported your settings in my Release Candidate 2 (see above), opened your NbJUnitBroken project, invoked "Test" action from its popup menu and the test was executed, it succeeded and for couple of seconds I could see a notification about it in the output window. Later I could just click the "1" bubble to open the "Notifications" output tab and selecting "Tests (1) finished..." row displayed "Open Test Results Window" link. Clicking that link opened the Test Results window. Since this is not 100% reproducible I am downgrading the priority. Fanis, are you able to reproduce this issue?
Still, I'm having it on 2 different computers and am willing to help reproduce it. What could we do?
(In reply to ymajoros from comment #15) > Still, I'm having it on 2 different computers and am willing to help > reproduce it. What could we do? ok as I am not also able to reproduce could you please try the following: 1) When the tests finish successfully do you see a bubble notification stating so? The bubble should be visible for ~15 seconds. 2) What happens when you modify your test to fail? Does TWR display then? 3) Could you make a short screencast of what is happening in your case in order to get a visual understanding and attach it here? Thank you
Another thing you could do is to start netbeans with -J-Dorg.netbeans.modules.gsf.testrunner.level=FINEST in order to get some more logging in the IDE's log file which you should attach here. Thank you
1. No bubble 2. Failing or succeeding, still no bubble ;-) 3. Any soft for that? If this really helps, I'll check it out. But it's really as described in 1/2 + IDE logs.
Created attachment 156982 [details] ide logs
No new line in IDE log after running the test.
If that helps, from Window menu, Output submenu is empty. From test output tab: cd C:\dev\gestemps\Gestemps-ejb; "JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_60" cmd /c "\"\"C:\\Program Files\\NetBeans 8.1 RC2\\java\\maven\\bin\\mvn.bat\" -Dtest=be.valuya.gestemps.server.RecurrenceUtilsTest -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans 8.1 RC2\\java\\maven-nblib\\netbeans-cos.jar\" -Dfile.encoding=UTF-8 -T4 -DGLASSFISH_HOME=c:/glassfish41 surefire:test\"" Running NetBeans Compile On Save execution. Phase execution is skipped and output directories of dependency projects (with Compile on Save turned on) will be used instead of their jar artifacts. Scanning for projects... Building with 4 threads ------------------------------------------------------------------------ Building Gestemps-ejb 2015.10.02-SNAPSHOT ------------------------------------------------------------------------ --- maven-surefire-plugin:2.10:test (default-cli) @ Gestemps-ejb --- Surefire report directory: C:\dev\gestemps\Gestemps-ejb\target\surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running be.valuya.gestemps.server.RecurrenceUtilsTest Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.406 sec <<< FAILURE! Results : Failed tests: testFindRealStartDateYearlyReccurence3(be.valuya.gestemps.server.RecurrenceUtilsTest) Tests run: 5, Failures: 1, Errors: 0, Skipped: 0 ------------------------------------------------------------------------ BUILD FAILURE ------------------------------------------------------------------------ Total time: 4.054s (Wall Clock) Finished at: Mon Oct 26 20:41:18 CET 2015 Final Memory: 10M/223M ------------------------------------------------------------------------ Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-cli) on project Gestemps-ejb: There are test failures. Please refer to C:\dev\gestemps\Gestemps-ejb\target\surefire-reports for the individual test results. -> [Help 1] To see the full stack trace of the errors, re-run Maven with the -e switch. Re-run Maven using the -X switch to enable full debug logging. For more information about the errors and possible solutions, please read the following articles: [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
(In reply to ymajoros from comment #18) > 1. No bubble > 2. Failing or succeeding, still no bubble ;-) > 3. Any soft for that? If this really helps, I'll check it out. But it's > really as described in 1/2 + IDE logs. This is strange. When there is a failure TRW must always open and take focus in order to show the user that something needs his attention. In this case no bubble is shown but the actual TRW is shown. I am sorry but I am out of ideas what could be wrong in your case. In the attached log I see way too many FNFE from jasper report plugin. Maybe it makes a difference? Hard to say...
If TRW means "Test results window" and is the UI with green/red, it's never shown. Whenever I run my test, it stays on maven output, which includes test status and a general build FAIL/SUCCESS message. That's about all it gives. I could disable all Jasper plugins, or even others, if that helps. Still, I don't have Jasper plugins on my work machine, where it does happen with my old user settings. Next step could be to make a mix between my current config and a new, working one. Any idea on how to do that easily?
I am seeing the same issue in the released version
Created attachment 157548 [details] test opening results screenshot of the workaround
workaround: untick "Print Maven output logging level" in the Maven settings tab see attachment
Unfortunately, this workaround seems to have no effect on my machine.
Created attachment 157613 [details] screencast to demo problem Hi, i attached a screencast that shows this bug * NetBeans is started * I have a simple testcase that fails on assertEquals(2, 3); * No nice test output (no red visible in this case), just maven output visible greetz, Joeri
Just tried again removing my settings directory on a machine where I still had the problem. It didn't work: test results are consistently not displayed, not even "no tests executed".
Hi, I had the same issue, luckily following the workaround given by davti "workaround: untick "Print Maven output logging level" in the Maven settings tab" solved the situation. I'm now able to see again the test results pane content. Thanks a lot davti! ;)
I observe the same issue on my machine with NB 8.1. If I use surefire 2.18 it works properly but it fails with 2.19(.1). Reinstalling without importing old settings does not help as well as the mentioned workaround. Product Version: NetBeans IDE 8.1 (Build 201510222201) Java: 1.8.0_45; Java HotSpot(TM) 64-Bit Server VM 25.45-b02 Runtime: Java(TM) SE Runtime Environment 1.8.0_45-b14 System: Mac OS X version 10.11 running on x86_64; UTF-8; en_US (nb) User directory: /Users/mkoppen/Library/Application Support/NetBeans/8.1 Cache directory: /Users/mkoppen/Library/Caches/NetBeans/8.1
The comment in this issue helped me: https://netbeans.org/bugzilla/show_bug.cgi?id=257563 Adding -e displays the test results. Unfortunately only failed tests are shown now.
I am seeing this issue using Maven 3.3.3 and 3.3.9 + TestNG 2.19.1 as well. It started in NetBeans 8.0.2 a couple of months ago. I'm not sure what change triggered it but I did update a lot of my dependency versions around that time. I installed NetBeans 8.1 today with no user settings import and it still happens. Based on comments and https://netbeans.org/bugzilla/show_bug.cgi?id=257563 I downgraded to surefire version 2.18 and it opened the test result window just fine. I saved the output and reran with the newer version and diff'd the two logs. Interesting lines missing from the output when using 2.19.1 which changed via pull request: https://github.com/apache/maven-surefire/pull/95/files - Surefire report directory: C:\MyProject\target\surefire-reports - Configuring TestNG with: TestNG652Configurator Assuming the root cause is because NetBeans relies on the output to find the surefire-report location in order to show it, could the location instead be determined based on the actual POM/project configuration with the default being <PROJECT_HOME>/target/surefire-reports? If I can help provide more info from my environment, I'll help where I can.
In my case the issue is the maven-surefire-plugin. Since 2.19 the Problem exists. See: https://netbeans.org/bugzilla/show_bug.cgi?id=257563
(In reply to helmut.at.work from comment #34) > In my case the issue is the maven-surefire-plugin. Since 2.19 the Problem > exists. See: https://netbeans.org/bugzilla/show_bug.cgi?id=257563 Yes, this is present on 2.19.1 as well. Reverted to 2.18.1 and it works.