Do they belong to you? Claim these comments.
Ole Morten Amundsen
Is this you? Claim Profile »
1 year ago
in Some FitNesse tricks: Classpath and debugging on Thinking inside a bigger box
I share your philosophy. I want to run everything locally, including the fitnesse server. This is my startup script
java -cp fitnesse.jar;lib\fitnesse-pom-widget-1.0-SNAPSHOT.jar;lib\maven-embedder-2.0.4-dep.jar fitnesse.FitNesse -p 8091 -r FitNesseRoot -l logs -o -e 0
Guess you'd find a way to execute the fitness server from Eclipse, but I don't see why. It uses near to nothing of resources and don't need to be restarted to notice updates. A simple .bat or .sh is good enough.
RELOCATION
I presume you have your fixtures in source control, why not have fitnesse ialongside it? They definetly belong together.
/trunk/fitnesse
/trunk/fixtures (or wherever the fixtures are located)
Then you may use the relative path "!pom ../fixtures/pom.xml"
DEBUGGER
The option -html fitnesse.html in the debugger outputs the results in the same manner as pressing Test in the fitnesse page.
Sadly, there is no cigar with FitNesse. I say, use it to communicate requirements, supplement with a few test tables. It's a wiki, terrible to maintain and opposes refactoring. I've committed my share of sins. Do you have any rules/guidelines for this Johannes?
java -cp fitnesse.jar;lib\fitnesse-pom-widget-1.0-SNAPSHOT.jar;lib\maven-embedder-2.0.4-dep.jar fitnesse.FitNesse -p 8091 -r FitNesseRoot -l logs -o -e 0
Guess you'd find a way to execute the fitness server from Eclipse, but I don't see why. It uses near to nothing of resources and don't need to be restarted to notice updates. A simple .bat or .sh is good enough.
RELOCATION
I presume you have your fixtures in source control, why not have fitnesse ialongside it? They definetly belong together.
/trunk/fitnesse
/trunk/fixtures (or wherever the fixtures are located)
Then you may use the relative path "!pom ../fixtures/pom.xml"
DEBUGGER
The option -html fitnesse.html in the debugger outputs the results in the same manner as pressing Test in the fitnesse page.
Sadly, there is no cigar with FitNesse. I say, use it to communicate requirements, supplement with a few test tables. It's a wiki, terrible to maintain and opposes refactoring. I've committed my share of sins. Do you have any rules/guidelines for this Johannes?
1 year ago
in Some FitNesse tricks: Classpath and debugging on Thinking inside a bigger box
Finally, I might assist you, Johannes! Nice work, but sadly, I think you're reinventing the weel here. I meant to write a blog post about this, including how to use the pom. No excuses!
We include the pom in the Fitnesse page by writing "!pom path_to_the_pom_he_fixtures_were_built_from/pom.xml". See http://boss.bekk.no/fitnesse-pom-widget/usage.html
Now you may set up a debugger in eclipse. Java Application->new->
Main class: fitnesse.runner.TestRunner
Arguments: localhost 8091 YourWikiPathToTestOrSuite -v -html fitnesse.html
Bonus tip to your many readers: add "-e 0" to the startup of your FitNesse server to avoid those dreadful zips. Isn't FitNesse intuitive?
We include the pom in the Fitnesse page by writing "!pom path_to_the_pom_he_fixtures_were_built_from/pom.xml". See http://boss.bekk.no/fitnesse-pom-widget/usage.html
Now you may set up a debugger in eclipse. Java Application->new->
Main class: fitnesse.runner.TestRunner
Arguments: localhost 8091 YourWikiPathToTestOrSuite -v -html fitnesse.html
Bonus tip to your many readers: add "-e 0" to the startup of your FitNesse server to avoid those dreadful zips. Isn't FitNesse intuitive?