I've added this unit test, PasCurnitCompatibility, as I described in my previous e-mail and in PAS-361.
I chose BuildPas0001 as the curnit to test against since it has the most stuff in it. So I ran that and put the resulting curnit archive in src/test/resources in org.telscenter.pas.curnits package. The PasCurnitCompatibility test loads that up, unmarshalls it and assembles it. If any of that doesn't does succeed (e.g. due to non-backwards-compatible changes in the codebase) an exception will be thrown and the test will fail. As Cynick has suggested, it would be a good practice to run tests within Eclipse before submitting. But since we do have a continuous integration server (Continuum), I propose we see how well it works at finding problems once there are good tests available for it to run. Maybe we should hook up the Jabber notification transport so developers are notified immediately if something they checked in has caused a problem. -t On Jan 11, 5:41 pm, "Turadg Aleahmad" <[EMAIL PROTECTED]> wrote: > Good point, Laurel. I wasn't aware that my changes broke > compatibility with older curnits. The building code is independent of > the producedcurnit. I suppose the breaker was fixing the typo in the > "reponses" property to "responses". Sorry for not realizing that > would break old curnits. > > It certainly is important to know whether a code edit breaks old > curnits. That would make an excellentunittest. > JIRA-TASKUnittest forcurnitbackwards compatibility > //Assignee:turadg > Store in the src/test/resources acurnitmade with a previous build > and have aunittest that unmarshalls and validates it. That way > Continuum can catch when such an edit happens. Developers can then > decide whether it's a bug or improvement. If it's a bug, fix it. If > it's an improvement, update the "old"curnitand notify SAIL-Dev. > > fwiw, I write the above in that syntax so my discussion-processor tool > can find it. I hope to have that working next week for us to use. > > -Turadg > > On 1/11/07, laurel <[EMAIL PROTECTED]> wrote: > > > > > Tony tells me that your email above implies that my curnits need to be > > rebuilt in order to use with the PAR. I have spent the last couple of > > days trying to figure out why my curnits wouldn't open in the authoring > > tool. If changes are made that do require curnits to be rebuilt, can > > you please specifically say that next time, since I really didn't know > > that is what I needed to do until Tony let me know today. > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
