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 178774 - Provide more flexible handling for locating tests in large projects
Summary: Provide more flexible handling for locating tests in large projects
Status: NEW
Alias: None
Product: php
Classification: Unclassified
Component: PHPUnit (show other bugs)
Version: 6.x
Hardware: Macintosh (x86) Mac OS X
: P3 normal (vote)
Assignee: issues@php
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-17 04:09 UTC by karsten
Modified: 2010-09-17 05:31 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Project structure in use (33.94 KB, image/png)
2009-12-17 04:09 UTC, karsten 		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 karsten 2009-12-17 04:09:03 UTC 
Created attachment 92703 [details]
Project structure in use

In FLOW3 we currently have a lot of unit tests and are on our way to make them self-contained enough to be run without our custom test runner. One major problem that still persists is the way NetBeans handles locating tests...

We have a structure that is composed of packages, each containing code, resources, documentation and tests. Thus I have a project in NetBeans that looks like depicted in the attached screenshot.

Now, to be able to use PHPUnit from within NetBeans my "test folder" actually needs to be a lot of folders. Or contain a wildcard (tried it, but NetBeans actually created a folder named "*" :).

The alternative of creating a NetBeans project per package would mean a lot of work, currently I have a NetBeans project per "Distribution".
Comment 1 Filip Zamboj 2010-09-15 12:36:50 UTC 
batch reassigning