I suppose there must be, but it depends on how you run from Ecilpse. I’m not an Eclipse user. Maybe someone can help you with that if you describe how you run from Eclipse, in Java terms. For instance do you start the jar or are you running classes directly, without building a jar from them, how do you pass arguments?
Regarding your ‘fix’ button idea. I don’t really see what that has to do with log files. It sounds like you want to generate alternative versions of wiki pages, where expected values are updated to actual values. You could take a look at the code to generate the ‘re-run suite’ that is generated when some pages in a suite fail. That gives an indication how to create a new page, from code, that can immediately be run from the wiki. But I don’t think this can be a generic feature: test failures could depend on input values to a fixture, not just direct expectations, or symbols could be used as expected values (ie the expected value is the output of some other method). It could of course work in your specific test setup and fixtures.
Hey there, in our setup we have a small set of test pages which are used in multiple test suites. Until now, we have copied these test pages to each test suite. To reduce code duplication, I tried to create a new test page, which servers as a template an which is parametrized. The test page is on the same hierarchy level as the test suites.
When I try to reference the test pages via "!see Template_Test_Page" the command is not rendered like the reference manual shows (alternatively I tried an absolute path as well, but that didn't work either). Instead, the command is printed as is.
We are running an older version of fitnesse (20200308), but I couldnt find anything relevant in the changelogs.
Do you know, why it is not correctly rendered or how I can further debug this?
Yes fitnesse.org is down. See https://github.com/unclebob/fitnesse/issues/1348#issuecomment-1004655347
Unfortunately the server does not even allow remote logins at the moment. I Uncle Bob already indicated he doesn't manage the server either. Maybe Mike can access it, or knows who manages the sever
Is someone familiar with a separate password file or -Cypher? To login to our application, I want to login with user "pindakaas" and password "hagelslag". In a plain password file, this will be:
How can you include a password file? FitNesse needs to know - somehow - that there's a separate file.
What if you want to encrypt the passwords? Should package fitnesse.authentication be included?