Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 2.0-alpha
-
Labels:None
-
Number of attachments :
Description
I am using Maven 2.2.1, and using a patched version of fitnesse-maven-plugin ( in MFITNESSE-30 ). Dependency of fitnesse 20081201 added (tried 20090709 and seems the same)
Assume I am running my maven build in machine A, and I have another machine F running FitNesse. In my test, I am using RestFixture which will connect to the webapp providing RESTful API. In my build script, I execute fitnesse:run in integration-test phase.
From the documents, I assume the way fitnesse:run works is, it will download the pages (of test cases etc) from F to local machine (A), and run it locally in A. However, I found that, when I build my app in A, the test case is unable to connect to my web server in localhost. By inspecting the test result in machine F, I found that tests are triggered in F, instead of A.
I would like to know if the "run locally" behavior provided by fitnesse test runner or done by the maven plugin? (it seems to me it is the former). Will it be the problem is caused by change in behavior in test runner of FitNesse (as the plugin is using 2005xxxx version internally)?