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 245483

Summary:	don't force karma config files to be in /config
Product:	javascript	Reporter:	John Jullion-ceccarelli <johnjullion>
Component:	Testing	Assignee:	Tomas Mysik <tmysik>
Status:	RESOLVED FIXED
Severity:	normal	CC:	vriha
Priority:	P3
Version:	8.0.1
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:	228650
Bug Blocks:

Description John Jullion-ceccarelli 2014-07-08 13:21:08 UTC

Currently if you have .config.js file outside of /config folder our support does not help you much. If it is in project root and you have public_html folder then you cannot even see it in the Projects window (general problem of HTML5 Projects layout). If it is in Tests or anywhere other than /config you can see it but cannot set it as the config file without going into project properties and using Browse.

Possible solutions:

* In Project Properties -> Karma, Search button for config should traverse entire project and not just /config
* All .config.js files should have a Test Project With action (wording?) that runs the tests with that config

Larger discussion is to get rid of Configuration Files/Unit Tests/Important Files nodes altogether and provide just directory based view of files under HTML5 project, which is what users are probably expecting anyway.

Comment 1 Tomas Mysik 2014-07-08 13:27:56 UTC

(In reply to John Jullion-ceccarelli from comment #0)
> * In Project Properties -> Karma, Search button for config should traverse
> entire project and not just /config

In this case, fixing issue #228650 would be more than helpful.

In any case, I will - at least - ensure that if any Karma config file is selected (in Project Properties), it is visible also in the context menu of the Karma node.

Thanks.

Comment 2 Tomas Mysik 2014-07-11 08:11:00 UTC

(In reply to Tomas Mysik from comment #1)
> In any case, I will - at least - ensure that if any Karma config file is
> selected (in Project Properties), it is visible also in the context menu of
> the Karma node.

Done. Once Karma config file selected by user, its directory is then considered to be "Karma Config" folder (so the Karma context menu is never empty).

Searching the whole directory tree is TBD (once issue #228650 is done).

Thanks.

http://hg.netbeans.org/web-main/rev/1efee42f66a8

Comment 3 Quality Engineering 2014-07-12 05:10:43 UTC

Integrated into 'main-silver', will be available in build *201407120001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/1efee42f66a8
User: Tomas Mysik <tmysik@netbeans.org>
Log: #245483 - don't force karma config files to be in /config

Comment 4 Tomas Mysik 2014-07-16 06:33:13 UTC

(In reply to John Jullion-ceccarelli from comment #0)
> * All .config.js files should have a Test Project With action (wording?)
> that runs the tests with that config

Reported as issue #245713.

Comment 5 Tomas Mysik 2014-07-25 06:52:36 UTC

*** Bug 245977 has been marked as a duplicate of this bug. ***

Comment 6 Tomas Mysik 2015-07-07 08:05:12 UTC

Closing this issue for now, the solution will be improved once issue #228650 is fixed.

Thanks.