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 245480 - Remove Karma node from Projects?
Summary: Remove Karma node from Projects?
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: Testing (show other bugs)
Version: 8.0.1
Hardware: All All
: P2 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-08 13:08 UTC by John Jullion-ceccarelli
Modified: 2014-10-06 13:06 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Jullion-ceccarelli 2014-07-08 13:08:17 UTC
The Karma node under each project is weird as Project nodes should be for project artifacts, preferably files, and Karma is more like a service. I understand there is one server per project, hence the idea. Main functionality exposed by Karma node are:

1 Start/Stop/Restart server
2 Set config file
3 Toggle Debug

1 and 3 probably belong in the Test Results window but would require additional UI. For 2 we discussed a Debug Project With context action on .config.js files to choose the config file. This is needed anyway since if config files aren't in config folder (very likely with existing projects) they don't show up in Set Config action on Karma node.
Comment 1 Tomas Mysik 2014-07-08 13:18:06 UTC
(In reply to John Jullion-ceccarelli from comment #0)
> 1 and 3 probably belong in the Test Results window but would require
> additional UI.

Adding Theofanis to CC.
Comment 2 Theofanis Oikonomou 2014-07-08 14:41:59 UTC
(In reply to Tomas Mysik from comment #1)
> (In reply to John Jullion-ceccarelli from comment #0)
> > 1 and 3 probably belong in the Test Results window but would require
> > additional UI.
> 
> Adding Theofanis to CC.

Well Test Results Window is supposed to show the results and provide some actions like rerun tests, navigate to source/test files etc. Adding actions for manipulating karma server can be done. They should be context aware and provide this info to testrunner, in order not to pollute the UI when not needed. From the top of my head a UI similar to the Usages window with the extra toolbar could be used.