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 44: some small fixes to test generator
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by marc.es...@gmail.com, Jan 1, 2008
here are some small fixes i'd like to see to the test generator. i'd like
to take a stab at them since i'm not familiar with how the generator works
and this would be a good introduction.

1) have the stubs use fail("not yet implemented") instead of assertTrue(false)

2) have a "style" option: either have the tests generate code that uses
cfinvoke OR <cfset actual = obj.doSomething(arg1,arg2)>

3) recursively create tests for all subdirectories. right now, you have to
select the subdirs yourself and do multiple generation runs. i can't
imagine it'd be too hard to make it recurse.

 
Jan 1, 2008
Project Member #1 marc.es...@gmail.com
one other change: I'd like to have it generate a testsuite file that uses the
directorytestsuite instead of suite.add(), since that doesn't force the user to
continually update their suite as they add new tests.
Jan 24, 2008
Project Member #2 virtix
Mike's MXUnit Blaster covers this.
Cc: AnodynePres v.rajkumar
Jan 24, 2008
Project Member #3 AnodyneP...@gmail.com
Let's see if this works.  I guess I own this item.
Owner: AnodynePres
Cc: -AnodynePres marc.esher
Mar 4, 2008
Project Member #4 AnodyneP...@gmail.com
(No comment was entered for this change.)
Status: Fixed

Powered by Google Project Hosting