[
https://issues.apache.org/jira/browse/SCXML-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar updated SCXML-93:
-------------------------------
Fix Version/s: 1.0
When running a single (problematic or new) test at a time, as I prefer to do,
its actually not difficult to locate serialization artifacts (they are usually
< 5 per test, and timestamp order corresponds to document order of
serialization).
I agree on accumulation, and since you insist on this, I don't mind those bits
being redone such that we use names that match the testcases etc. I agree its
an improvement since the number would be limited on a complete run (or many
runs) as you say above.
However, its not something I personally care to do (which is why the Won't Fix
before).
So I'm setting the fix version to 1.0 (which currently means 'some time in the
future if a well-tested patch appears on this ticket').
> 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.
