[
https://issues.apache.org/jira/browse/MIME4J-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara updated MIME4J-64:
----------------------------------
Attachment: ExampleMessagesRoundtripTest.java
Updated the test with new features.
Now the resulting output is parsed again in a Message and written back to
stream and the result is compared both writing it in LENIENT and in STRICT mode.
The good news is that only 1 test still fail (the one having rhe base64 encoded
rfc822 message).
I've yet to better ionvestigate on the base64/rfc822 issue. I'll open a bug
according to this.
I repeat that ".out" files attached are not really what I would expect from
mime4j but simply what mime4j currntly return (JAMES people don't like TDD).
Please note that this test currently fail anyway because the roundtrip on the
base64/rfc822 message fails.
> More tests for the roundtrip new Message(input).writeto(output) usage.
> ----------------------------------------------------------------------
>
> Key: MIME4J-64
> URL: https://issues.apache.org/jira/browse/MIME4J-64
> Project: Mime4j
> Issue Type: Task
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.4, 0.5
>
> Attachments: ExampleMessagesRoundtripTest.java,
> ExampleMessagesRoundtripTest.java, testmsgs-currentout.zip
>
>
> I think it worth introducing ".msg" file based massive testing also for the
> DOM based parsing/writing.
> We don't expect to have identical input/output files, but it is good to
> record the expected result so that we'll have more chance to catch
> regressions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
