Re: [Mailman-Developers] Basic workflow of the ARC implementation
Aditya Divekar writes:
- ARC Authentication Result - arc verification code completed. tests passed. merge request created.
How do you propose to create tests for #4?
Here, we could consider a few scenarios- headers. In this case the verification is not performed.
- A message is passed to the function which does not have any previous ARC
- A message containing a valid ARC chain is passed to the function.
The problem is how do you get such a message? The easiest way is if you have implemented the creation functions for the ARC-* fields.
Then you can check that you can roundtrip your own fields (create and verify). Of course you will eventually need to test against other implementations (currently Google and AOL have implementations that I know of), but for now it makes sense to "eat your own dogfood".
Regards,
Hi Steve,
The problem is how do you get such a message? The easiest way is if you have implemented the creation functions for the ARC-* fields.
Then you can check that you can roundtrip your own fields (create and verify). Of course you will eventually need to test against other implementations (currently Google and AOL have implementations that I know of), but for now it makes sense to "eat your own dogfood"
Yes, in that case the arc verification would need to be postponed to after the entire code for the header generation has been written. I'll need to rethink the milestones a bit, since this testing part would have to be added at the end, and things will change quite a bit. I'll work this out properly and reach back to you.
On a side note, would posting on the arc-discuss list for help in the above problem of testing be acceptable?
Thanks
Aditya
participants (2)
-
Aditya Divekar -
Stephen J. Turnbull