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.
| Summary: |
Provide more flexible handling for locating tests in large projects |
| Product: |
php
|
Reporter: |
karsten <karsten> |
| Component: |
PHPUnit | Assignee: |
issues@php <issues> |
| Status: |
NEW
---
|
|
|
| Severity: |
normal
|
CC: |
tmysik
|
| Priority: |
P3
|
|
|
| Version: |
6.x | |
|
| Hardware: |
Macintosh (x86) | |
|
| OS: |
Mac OS X | |
|
|
Issue Type:
|
ENHANCEMENT
|
Exception Reporter:
|
|
|---|
| Attachments: |
Project structure in use
|
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".