You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2008/12/06 01:27:44 UTC
[jira] Commented: (SCXML-93) SCXMLTestHelper generates a lot of
serialisation files which are not tidied up
[ https://issues.apache.org/jira/browse/SCXML-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654002#action_12654002 ]
Sebb commented on SCXML-93:
---------------------------
It's not too difficult to walk the call stack to find a calling method with the name textXXX, but this does not uniquely identify all usages.
So I suggest just replacing the millisecond stamp (which is not necessarily unique, by the way) with a simple int counter.
This can be a static (class) variable. If the test is re-run without reloading the class, then the counter will increase, but at least repeated "mvn test" runs won't create lots of files.
Is that OK?
> SCXMLTestHelper generates a lot of serialisation files which are not tidied up
> ------------------------------------------------------------------------------
>
> Key: SCXML-93
> URL: https://issues.apache.org/jira/browse/SCXML-93
> Project: Commons SCXML
> Issue Type: Bug
> Reporter: Sebb
> Priority: Minor
> Fix For: 1.0
>
>
> SCXMLTestHelper generates files to test serialisation of classes in testExecutorSerializability() and testModelSerializability().
> These files are only used temporarily, but are not cleared up at the end of a run.
> They can be replaced by using ByteArray classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.