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 253101 - AssertionError: No suites running
Summary: AssertionError: No suites running
Status: RESOLVED WORKSFORME
Alias: None
Product: utilities
Classification: Unclassified
Component: Selenium (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-22 06:37 UTC by macku
Modified: 2015-09-14 09:35 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 218093

Attachments
stacktrace (1.58 KB, text/plain)
2015-06-22 06:38 UTC, macku 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description macku 2015-06-22 06:37:58 UTC 
Build: NetBeans IDE Dev (Build nbms-and-javadoc-2765-on-20150307)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.45-b02, Java(TM) SE Runtime Environment, 1.8.0_45-b14
OS: Windows 7

User Comments:
macku: runing tests




Stacktrace: 
java.lang.AssertionError: No suites running
   at org.netbeans.modules.gsf.testrunner.api.TestSession.addTestCase(TestSession.java:219)
   at org.netbeans.modules.selenium2.webclient.api.TestRunnerReporter.addTestCase(TestRunnerReporter.java:350)
   at org.netbeans.modules.selenium2.webclient.api.TestRunnerReporter.handleTrouble(TestRunnerReporter.java:235)
   at org.netbeans.modules.selenium2.webclient.api.TestRunnerReporter.parseTestResult(TestRunnerReporter.java:206)
   at org.netbeans.modules.selenium2.webclient.api.TestRunnerReporter.processLine(TestRunnerReporter.java:178)
   at org.netbeans.modules.selenium2.webclient.protractor.ProtractorRunner$OutputLineConvertor.convert(ProtractorRunner.java:354)
Comment 1 macku 2015-06-22 06:38:00 UTC 
Created attachment 154321 [details]
stacktrace
Comment 2 Theofanis Oikonomou 2015-09-14 09:34:49 UTC 
I need some more info in order to properly fix this as I am unable to reproduce in latest builds. I am guessing you are seeing this as the first test case fails. There seems to be some output caught which triggers this. Could you reopen stating what kind of tests you are running, e.g protractor or mocha and ideally attaching a sample project or testcase+config that shows this behavior? Thank you for reporting