Home > Archive > Extreme Programming > May 2005 > Fitnesse fixture dlls
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Fitnesse fixture dlls
|
|
|
| I was wondering if anyone has worked with Fitnesse and has run into
issues with the tables not recognizing the fixture dlls. Our shop is
investigating using Fit and Fitnesse for acceptance test leading into a
philosophy change from water fall to agile development approaches.
I have set up a mock wikki test page in Fitnesse and specified the
class path where the dll containing my fixture code is located. I then
clicked test to test the code and received an exception stating that
the fixture could not be found. I compared fixture solutions from the
fitnesse download site and found that there was no difference,,,,, so I
tried a number of things one of which was to move the dll to the
directory containing all the other fixture code that was downloaded
from the Fitnesse site because they were working. Still no success.
Does anyone have any suggestions or unwritten requirements that will
bridge the gap between my test page and my fixture code.
| |
|
| Holly wrote:
> I was wondering if anyone has worked with Fitnesse and has run into
> issues with the tables not recognizing the fixture dlls. Our shop is
> investigating using Fit and Fitnesse for acceptance test leading into a
> philosophy change from water fall to agile development approaches.
May I suggest...
- use the FITnesse mailing list for technical question
(Micah et al don't post here)
- transition from Waterfall without replacing it with another Waterfall
You need to switch to two-w iterations, and test-first at the unit level.
Those two techniques will force a lot of procedural changes. These will lead
to new understanding of the role of literate tests in specifying user
stories, and to more test infrastructure. At that time, you might start to
ask the Onsite Customer to specify features as tests, and that's when you
need FITnesse.
Instead, you seem to be going to Big Test Up Front.
--
Phlip
[url]http://www.c2.com/cgi/wiki?ZLand[/url]
| |
|
| And,,, that Fitnesse mailing list is where?
As for the development methodology switch that is something that has
been in the
works for months now. Our Architects, testers and management have been
exploring and researching the right approach for our site and although
we all know that this will change as we use the philosophy they have
laid down some very strong beginnings to the change.
User stories are being developed but unless we get to the point that we
can use Fit and feel that it gives us function that NUnit doesn't
already provide we won't be using it at all. My task is to get it
running in a mock environment to see if it is even a tool we are
interested in using for test driven development. Otherwise our manual
test cases will serve as the specification from which the developers
will code.
Our users and execs are on board with the agile approach and the ones
that are involved in the process are excited about how it has worked
thus far. Development management has decided to go with "yesterday's
weather" to drive our iterations and I think as far as implementing
agile within our organization they seem to be driving it in the
direction that works best for our shop. Agile of course being a
philosophy and not a hardened fast set of rules that must be followed.
I think they did start with the 2 w iterations on the project that
is currently using the methodology and may still be using that length
of time. But, as for acceptance testing, it is strickly manual at this
point. The goal is to automate all but the tests at the GUI level.
I am still trying to figure out how you determined that we are doing
the Big Test Up Front. We write the test cases but without the
completed code to test there is no way to perform the "Big Test", the
tests we perform are just the iterative tests.
| |
| John Roth 2005-05-06, 8:56 pm |
| Yes, take this to either the Yahoo Fitness group or the
fit-devl list on sourceforge. Both lists discuss this issue
quite a bit. You're not the only person who has problems
with dll versioning in the dotNet versions of FIT.
John Roth
"Holly" <hlk4631@yahoo.com> wrote in message
news:1115402234.741154.174500@z14g2000cwz.googlegroups.com...
>I was wondering if anyone has worked with Fitnesse and has run into
> issues with the tables not recognizing the fixture dlls. Our shop is
> investigating using Fit and Fitnesse for acceptance test leading into a
> philosophy change from water fall to agile development approaches.
>
> I have set up a mock wikki test page in Fitnesse and specified the
> class path where the dll containing my fixture code is located. I then
> clicked test to test the code and received an exception stating that
> the fixture could not be found. I compared fixture solutions from the
> fitnesse download site and found that there was no difference,,,,, so I
> tried a number of things one of which was to move the dll to the
> directory containing all the other fixture code that was downloaded
> from the Fitnesse site because they were working. Still no success.
> Does anyone have any suggestions or unwritten requirements that will
> bridge the gap between my test page and my fixture code.
>
| |
|
| Holly wrote:
> And,,, that Fitnesse mailing list is where?
http://groups.yahoo.com/group/fitnesse
> I am still trying to figure out how you determined that we are doing
> the Big Test Up Front.
No prob. My bad. Your post didn't mention all the pre-existing work, so I
just pointed out that starting with an advanced tool could lead to BTUF.
--
Phlip
[url]http://www.c2.com/cgi/wiki?ZLand[/url]
|
|
|
|
|