My favorites | Sign in
Project Home Downloads Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 73: Write migration path/strategy for CFUnit and CFCUnit users
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by virtix, Mar 4, 2008
I've held off on this, but it appears that this _need_ comes up frequently.
The fact MXUnit is being actively developed is very appealing to people and
with that said, I do not see us as competitors. 

So, let's come up with a few ways to help people make the jump. We should
need to define what needs to be changed in the code, using the assertion
extension mechanisms, and likely upgrading and refactoring the framework to
align with this goal.

Volunteers?
Mar 13, 2008
Project Member #1 a.hask...@gmail.com
Its not exhaustive but Sean wrote up some stuff of what he did to migrate from
cfcUnit: http://corfield.org/blog/index.cfm/do/blog.entry/entry/MXUnit
Jan 22, 2009
Project Member #2 virtix
(No comment was entered for this change.)
Status: Fixed

Powered by Google Project Hosting