aceunit-devel Mailing List for AceUnit (Page 3)
Status: Beta
Brought to you by:
christianhujer
Menu
▾
▴
aceunit-devel — aceunit developer talk list (medium traffic)
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(19) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(25) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2007-11-30 22:09:32
|
Bugs item #1841588, was opened at 2007-11-30 11:21 Message generated for change (Comment added) made by christianhujer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000227&aid=1841588&group_id=207094 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: Java Generator Group: trunk >Status: Closed >Resolution: Fixed Priority: 9 Private: No Submitted By: Christian Hujer (christianhujer) Assigned to: Christian Hujer (christianhujer) Summary: More than 1 Fixture: Fixture elements cause linker conflicts Initial Comment: Short Description: When more than one fixture is used, the tests cannot be linked. Expected Behaviour: Using more than one fixture works fine. No problems. Actual Behaviour: When more than one fixture is used, the linker will cause problems. Reason: The generated fixtures use non-unique names for variables and those variables are not declared static. Examples: before, after, beforeClass, afterClass etc.. Fix: Change the generator to create those variables prefixed with static. ---------------------------------------------------------------------- >Comment By: Christian Hujer (christianhujer) Date: 2007-11-30 23:09 Message: Logged In: YES user_id=465603 Originator: YES Fixed in revision 233. ---------------------------------------------------------------------- Comment By: Christian Hujer (christianhujer) Date: 2007-11-30 11:32 Message: Logged In: YES user_id=465603 Originator: YES Workaround: Modify generated header files to declare the variables static. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000227&aid=1841588&group_id=207094 |
|
From: SourceForge.net <no...@so...> - 2007-11-30 10:32:17
|
Bugs item #1841588, was opened at 2007-11-30 11:21 Message generated for change (Comment added) made by christianhujer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000227&aid=1841588&group_id=207094 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: Java Generator Group: trunk Status: Open Resolution: None Priority: 9 Private: No Submitted By: Christian Hujer (christianhujer) Assigned to: Christian Hujer (christianhujer) Summary: More than 1 Fixture: Fixture elements cause linker conflicts Initial Comment: Short Description: When more than one fixture is used, the tests cannot be linked. Expected Behaviour: Using more than one fixture works fine. No problems. Actual Behaviour: When more than one fixture is used, the linker will cause problems. Reason: The generated fixtures use non-unique names for variables and those variables are not declared static. Examples: before, after, beforeClass, afterClass etc.. Fix: Change the generator to create those variables prefixed with static. ---------------------------------------------------------------------- >Comment By: Christian Hujer (christianhujer) Date: 2007-11-30 11:32 Message: Logged In: YES user_id=465603 Originator: YES Workaround: Modify generated header files to declare the variables static. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000227&aid=1841588&group_id=207094 |
|
From: SourceForge.net <no...@so...> - 2007-11-30 10:20:58
|
Bugs item #1841588, was opened at 2007-11-30 11:21 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000227&aid=1841588&group_id=207094 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: Java Generator Group: trunk Status: Open Resolution: None Priority: 9 Private: No Submitted By: Christian Hujer (christianhujer) Assigned to: Christian Hujer (christianhujer) Summary: More than 1 Fixture: Fixture elements cause linker conflicts Initial Comment: Short Description: When more than one fixture is used, the tests cannot be linked. Expected Behaviour: Using more than one fixture works fine. No problems. Actual Behaviour: When more than one fixture is used, the linker will cause problems. Reason: The generated fixtures use non-unique names for variables and those variables are not declared static. Examples: before, after, beforeClass, afterClass etc.. Fix: Change the generator to create those variables prefixed with static. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000227&aid=1841588&group_id=207094 |
|
From: SourceForge.net <no...@so...> - 2007-11-26 23:00:41
|
Feature Requests item #1836413, was opened at 2007-11-22 12:49 Message generated for change (Comment added) made by christianhujer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836413&group_id=207094 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: Java Generator Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Christian Hujer (christianhujer) Assigned to: Christian Hujer (christianhujer) Summary: Warning if no test cases found Initial Comment: Current behaviour: If the generator is invoked and does not find test cases, it does not issue a warning and it does not generate header files. This is bad because a user that simply forgot annotations in his source will not know what exactly was going wrong. Desired behaviour: If the generator is invoked and does not find test cases, it issues a warning that no test cases were found along with a suggestion on how to fix that problem. Example message: path/to/foo.c: warning: No test cases found. Maybe the annotations are missing? ---------------------------------------------------------------------- >Comment By: Christian Hujer (christianhujer) Date: 2007-11-27 00:00 Message: Logged In: YES user_id=465603 Originator: YES Implemented with: "r231 /trunk/src/java/src/prj/net/sf/aceunit/GenTest.java: [ 1836413 ] Warning if no test cases found" Will be included in version 0.3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836413&group_id=207094 |
|
From: SourceForge.net <no...@so...> - 2007-11-24 12:48:06
|
Feature Requests item #1836413, was opened at 2007-11-22 12:49 Message generated for change (Settings changed) made by christianhujer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836413&group_id=207094 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: Java Generator Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Hujer (christianhujer) >Assigned to: Christian Hujer (christianhujer) Summary: Warning if no test cases found Initial Comment: Current behaviour: If the generator is invoked and does not find test cases, it does not issue a warning and it does not generate header files. This is bad because a user that simply forgot annotations in his source will not know what exactly was going wrong. Desired behaviour: If the generator is invoked and does not find test cases, it issues a warning that no test cases were found along with a suggestion on how to fix that problem. Example message: path/to/foo.c: warning: No test cases found. Maybe the annotations are missing? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836413&group_id=207094 |
|
From: SourceForge.net <no...@so...> - 2007-11-23 21:48:03
|
Feature Requests item #1836423, was opened at 2007-11-22 12:56 Message generated for change (Settings changed) made by christianhujer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836423&group_id=207094 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: Java Generator Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Hujer (christianhujer) >Assigned to: Christian Hujer (christianhujer) Summary: Log what's happening Initial Comment: Current behaviour: The Java Generator is very silent. It does not issues any messages about what's going on. Desired behaviour: It should be possible to optionally have some logging information printed on STDERR, e.g. about which files were identified to be test fixtures, which header files were generated etc.. There should be different log levels. Without specifying a log level, the behaviour should stay the same as it is now. With fine, the generator should tell which header files were generated. With finer, the generator should tell which source files were looked at. With finest, the generator should tell what file and directory it traverses. (For the generic description of the levels, see http://java.sun.com/javase/6/docs/api/java/util/logging/Level.html) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836423&group_id=207094 |
|
From: SourceForge.net <no...@so...> - 2007-11-22 11:56:23
|
Feature Requests item #1836423, was opened at 2007-11-22 12:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836423&group_id=207094 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: Java Generator Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Hujer (christianhujer) Assigned to: Nobody/Anonymous (nobody) Summary: Log what's happening Initial Comment: Current behaviour: The Java Generator is very silent. It does not issues any messages about what's going on. Desired behaviour: It should be possible to optionally have some logging information printed on STDERR, e.g. about which files were identified to be test fixtures, which header files were generated etc.. There should be different log levels. Without specifying a log level, the behaviour should stay the same as it is now. With fine, the generator should tell which header files were generated. With finer, the generator should tell which source files were looked at. With finest, the generator should tell what file and directory it traverses. (For the generic description of the levels, see http://java.sun.com/javase/6/docs/api/java/util/logging/Level.html) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836423&group_id=207094 |
|
From: SourceForge.net <no...@so...> - 2007-11-22 11:49:42
|
Feature Requests item #1836413, was opened at 2007-11-22 12:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836413&group_id=207094 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: Java Generator Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Hujer (christianhujer) Assigned to: Nobody/Anonymous (nobody) Summary: Warning if no test cases found Initial Comment: Current behaviour: If the generator is invoked and does not find test cases, it does not issue a warning and it does not generate header files. This is bad because a user that simply forgot annotations in his source will not know what exactly was going wrong. Desired behaviour: If the generator is invoked and does not find test cases, it issues a warning that no test cases were found along with a suggestion on how to fix that problem. Example message: path/to/foo.c: warning: No test cases found. Maybe the annotations are missing? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1000230&aid=1836413&group_id=207094 |
|
From: Christian H. <ch...@ri...> - 2007-10-07 16:40:55
|
Hi, the current status of the project is: * It's probably good enough for a first alpha release. * There's a nice example project in src/doc/examples/sort/ * Typing make there works (at least for me). General information can be found in the repository at src/doc/. If you think there is a show stopper for a 0.1 release, please speak up.=20 Otherwise I will release AceUnit 0.1 very soon. What I've done so far: * Registered and Setup the project with ** SourceForge - http://sourceforge.net/projects/aceunit *** Setup SVN repository and commit hooks (CIA etc.) at http://aceunit.svn.sourceforge.net/svnroot/aceunit/ (SVN) http://aceunit.svn.sourceforge.net/viewvc/aceunit/ (Web) *** Setup mailing lists @lists.sourceforge.net: aceunit-commit, aceunit-devel and aceunit-news=20 ** FreshMeat - http://freshmeat.net/projects/aceunit/ ** Ohloh - http://www.ohloh.net/projects/9006 *** Added SVN repository to enlistments ** FreeNode IRC Channel - irc://irc.freenode.net:6667/%23aceunit *** Registered channel with ChanServ, set topic ** CIA - http://cia.vc/stats/project/aceunit *** Setup CIA to have a CIA bot on #aceunit IRC Channel * Created compilable example project. ** The header file generated by the Java program now works. ** The java program now can be easily built with Ant. ** When running the example with make, ant will be run automatically. ** The C framework now works. ** The example works. * Created some documentation. What I've not done: * Testing on Microsoft Windows, so if somebody please could... * Testing on Mac OS X ... =46inally, an Ohloh Factoid: "Across all C/C++ projects on Ohloh, 20% of all source code lines are=20 comments. For AceUnit, this figure is 51%. [...] very impressive [...] best= =20 10% of all [...]." (This was before I added the license comments!) http://www.ohloh.net/projects/9006/factoids/243410 Cheers =2D-=20 Christian Hujer =46ree software developer mailto:ch...@ri... http://www.riedquat.de/ PGP Fingerprint: 03DE 4B72 4E57 A98D C79B 24A5 212E 0217 0554 CCAB |
