Hi Jason, > if a suite of tests is using the old syntax and there are no plans to > update the tests using the new syntax why upgrade to the latest > version of Rhino.Mocks?
How about an actively evolving project that already have hundreds of test fixtures (which translate to thousands of test cases) using old syntax and would like to use new syntax on other few hundreds of test fixtures yet to be written? > At some point there would be pain to migrate > from old syntax to new syntax, how that process is managed will > determine how much effort is required. The point is that, ideally, I shouldn't be forced to migrate. I'll just leave the old test cases as is and create new test cases with new syntax within the same project. Cheers, Kenneth --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino.Mocks" 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/rhinomocks?hl=en -~----------~----~----~----~------~----~------~--~---
