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: | compile tests along with source code | ||
---|---|---|---|
Product: | apisupport | Reporter: | Milos Kleint <mkleint> |
Component: | Project | Assignee: | Jesse Glick <jglick> |
Status: | CLOSED WONTFIX | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Milos Kleint
2005-08-19 13:57:32 UTC
apisupport is simply being consistent with other project types. If you want to always build & run tests, use Alt-F6 rather than F11. Anyway you *do* need to run tests before committing a change to the trunk; that's what they're there for. and what about at least an option to build tests along with sources? The issue is not about running tests. I don't argue that I should have run the tests before integration. I admit sometimes I forget. But aren't tools here to help us being consistent? Compiling (not running) tests along the sources is a cheap operation but helps in signalling that something got broken. BTW not sure if it's just the case of apisupport/project but running tests on a clean box doesn't work because one has to run tests in ant/project first. Otherwise the compilation fails. Daily tester machine is intended for that in general. Currently won't run apisupport tests - we need to refactor many of them to not require a full netbeans.org checkout. Dep on ant/project's test-build was already removed. If you use Linux you can just echo testedmodule=apisupport/project >> nbbuild/misc/build-site-local.sh If you don't, consider porting the script to your OS of choice. There's a target "test-build", which may do the job. Closing, but feel free to reopen. |