From: SourceForge.net <no...@so...> - 2007-02-11 22:03:50
|
Bugs item #1657550, was opened at 2007-02-11 16:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438935&aid=1657550&group_id=44253 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: JUnit integration Group: 2: Annoying Status: Open Resolution: None Priority: 5 Private: No Submitted By: ongardie (ongardie) Assigned to: Nobody/Anonymous (nobody) Summary: Empty java files cause junit test error Initial Comment: * Create a project with some empty .java source files, some non-empty .java source files, and a test case. * Note that compiling and running work as expected, ignoring the empty files. * Try running the tests. You'll get three dialogs in a row: 1. To unit test all documents, you must first compile all out of sync source files. Would you like to compile all files and run the specified test? [Yes] [No]. // This comes up even if you've just compiled all files. Click Yes. 2. All open source files must be compiled before running a unit test. [Ok] // Didn't we just give it permission to do that? Click Ok. 3. There are no compiled JUnit TestCases available for execution. Perhaps you have not yet compiled your test files. [Ok] // But I have compiled them and they are available. Click Ok. The test do not run, and the series of seemingly irrelevant dialog boxes offers no help. My suggestion is that blank files should be ignored for testing purposes. -Diego Ongaro ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438935&aid=1657550&group_id=44253 |