Hi All, I am trying run just one sample test case using xml http test and json http tests using hsac-fitnesse-fixtures-2.12.2.jar

I have downloaded the jar and given !path in the wiki table as below.

!define TEST_SYSTEM {slim} !path D:/APIConnect/hsac_jar/latest/* !define POST_BODY_2 { {{{ <s11:Envelope xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"> s11:Body <ns1:GetCityWeatherByZIP xmlns:ns1="http://ws.cdyne.com/WeatherWS/"> ns1:ZIP@{zip}</ns1:ZIP> </ns1:GetCityWeatherByZIP> </s11:Body> </s11:Envelope> }}} }

|script|xml http test| |table template |send request | |post |${POST_BODY_2} |to |http://localhost:7080/apitest| |check |response status|200 | |show |response |

and getting the below error.

can anyone please provide some inputs to make this work.

Thanks,

I'm using defines to create nested tables. It works well, but I ran into a problem when I used a character that's not allowed in XML. Here's my define - notice the description for item 4: !define BONUSRatingTbl {| RATING_NBR | DESCR2 | | 1 | Met 100% of goals | | 2 | Met 75% of goals | | 3 | Met 50% of goals | | 4 | Met < 50% of goals | }

This resulted in the following text being passed to SLIM:

<table>
    <tr>
        <td>RATING_NBR</td>
        <td>DESCR2</td>
    </tr>
    <tr>
        <td>1</td>
        <td>Met 100% of goals</td>
    </tr>
    <tr>
        <td>2</td>
        <td>Met 75% of goals</td>
    </tr>
    <tr>
        <td>3</td>
        <td>Met 50% of goals</td>
    </tr>
    <tr>
        <td>4</td>
        <td>Met < 50% of goals</td>
    </tr>
</table>

When my fixture tries to convert the string to an XML object for conversion, it fails due to the invalid < character being in the text, which I believe should be encoded as `

Edit: In reality, it ought to be encoded as <, which still isn't happening in my case.

Problem Description

I think I have uncovered a possible defect in Fitnesse, more specifically after version 20140901. I can't seem to find any other person that have experienced a similar problem, so I figured that I should post it here.

When starting a test in Fitnesse I get the following error:

Could not complete testing: fitnesse.slim.SlimError: Error SLiM server died before a connection could be established.

My OS is Windows 7 and I'm running Fitnesse in a Java project which uses jdk1.7.

Problem Diagnosis

I have performed some diagnosis to try to figure out what could be the reason for this error.

I am cooperating with another person who uses a Mac instead of Windows, and he does not experience this error.

When ONLY changing the Fitnesse version in maven pom I have uncovered the following:

1. This problem does NOT occur on version 20140901.
2. I get the reported error message on version 20150424 and 20150226.
3. When using version 20150114 the test just hangs and never exits.

When debugging the error I have found the following:

1. The exception is thrown on line 92 in SlimCommandRunningClient.java
2. This seems to be because the isDead() method returns true for the process in slimRunner(CommandRunner)
3. This process is implemented as a java.lang.ProcessImpl for Windows, while on Mac it is implemented as a UNIXProcess
4. The exitValue for the process is 1

Another peculiar thing that I found was that when using the remote debug option in Fitnesse(?responder=test&remote_debug=true), the test works and no errors occur(This works on version 20150114, 20150424 and 20150226).

So, what could be the cause for this error? According to my diagnosis this problem started to occur after version 20140901.

The order in which suites are run is illogical (at least not the same order in which it is presented)

my suites are ordered as follows: Backend Tests * - Suite Instrument Search * ... - Suite Ordering * ... - Suite Relation Search * ... - Suite Set Up Frontend Tests * - Suite Cms * ... - Suite Employee Login * ... - Suite Employee Navigation Bar * ... - Suite Instrument Search * ... - Suite Money Transfer * ... - Suite Ordering * ... - Suite Portfolio Overview * ... - Suite Relation Search * ... - Suite Site Navigation * ...

When running these tests the following order is executed:

FrontendTests.SuiteCms.SuiteSetUp (51.683 seconds) FrontendTests.SuiteCms.TestCase249001 (40.106 seconds) FrontendTests.SuiteCms.TestCase249002 (0.281 seconds) FrontendTests.SuiteCms.SuiteTearDown (0.000 seconds) FrontendTests.SuiteEmployeeNavigationBar.SuiteSetUp (21.312 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase078001 (1.094 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase078002 (28.496 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase078003 (5.656 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase078004 (6.140 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase104001 (0.250 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase104002 (0.000 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase104003 (0.719 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase105001 (0.000 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase105002 (10.609 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase106001 (0.000 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase401001 (9.420 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase401002 (1.953 seconds) FrontendTests.SuiteEmployeeNavigationBar.TestCase417001 (0.484 seconds) FrontendTests.SuiteEmployeeNavigationBar.SuiteTearDown (0.000 seconds) BackendTests.SuiteSetUp (0.109 seconds) BackendTests.SuiteInstrumentSearch.TestCase096002 (0.031 seconds) BackendTests.SuiteInstrumentSearch.TestCase096003 (0.016 seconds) BackendTests.SuiteInstrumentSearch.TestCase096004 (0.000 seconds) BackendTests.SuiteInstrumentSearch.TestCase096010 (0.000 seconds) BackendTests.SuiteOrdering.TestCase108002 (0.062 seconds) BackendTests.SuiteOrdering.TestCase108003 (0.047 seconds) BackendTests.SuiteOrdering.TestCase108007 (0.047 seconds) BackendTests.SuiteRelationSearch.TestCase099001 (0.750 seconds) BackendTests.SuiteRelationSearch.TestCase099002 (0.719 seconds) BackendTests.SuiteRelationSearch.TestCase099003 (1.265 seconds) BackendTests.SuiteRelationSearch.TestCase099008 (0.078 seconds) FrontendTests.SuiteInstrumentSearch.SuiteSetUp (19.095 seconds) FrontendTests.SuiteInstrumentSearch.LayoutAndContent.TestCase095001 (0.016 seconds) FrontendTests.SuiteInstrumentSearch.LayoutAndContent.TestCase153001 (5.280 seconds) FrontendTests.SuiteInstrumentSearch.LayoutAndContent.TestCase338001 (0.000 seconds) FrontendTests.SuiteInstrumentSearch.LayoutAndContent.TestCase364001 (1.938 seconds) FrontendTests.SuiteInstrumentSearch.LayoutAndContent.TestCase364004 (6.939 seconds) FrontendTests.SuiteInstrumentSearch.LayoutAndContent.TestCase419005 (2.594 seconds) FrontendTests.SuiteInstrumentSearch.QueryMatching.TestCase096001 (1.453 seconds) FrontendTests.SuiteInstrumentSearch.QueryMatching.TestCase096005 (0.625 seconds) FrontendTests.SuiteInstrumentSearch.QueryMatching.TestCase096006 (0.000 seconds) etc...

Pull request for the patch supplied in Issue #244:

• src/fitnesse/wiki/fs/FileSystemPageFactory.java, src/fitnesse/responders/editing/SymbolicLinkResponder.java

  Main change.

• src/fitnesse/wiki/fs/FileSystemPage.java

  Multi-platform correctness, also necessary for passing the tests under Windows.

• FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/SymbolicLinks/content.txt

  Minor documentation update.

• The rest are updates to the tests.

The FitNesse homepage is now looking really dated, and the user guide is an old version as well.

Is there anything stopping updating the site to the latest release?

FitNesse is using a directory (the page name) and two files: content.txt and properties.xml to store a wiki page to disk.

While this works fine if you're only using FitNesse from the wiki, this structure has some downsides when used from IDE's. Version control is also somewhat more laborious with those many files.

I'd like to propose a single file format: <page-name>.wiki for a single wiki page.

Nesting of pages

~~I think here the folder should have the page name and it should contain a default file: content.wiki.~~

Do as Gregor says.

Page properties

Page properties (if it's a test page, symlinks, etc.) will be stored in a "front-matter", just like Jekyll does it (https://jekyllrb.com/docs/frontmatter/). So a wiki page, when opened in a text editor, may look like this:

---
Edit
Test

---
Page content comes here

To do list:

• [x] Use old and new style pages interchangeably
• [x] Parse Front mapper with current wiki parser
• [x] Create page properties from front matter
• [x] Create page data
• [x] Remove pages and sub pages
• [x] Pages should be listed in the contents section
• [x] Store new file versions
• [x] Create (zip) backup files -> support VersionsController interface
• [x] Use new page format as default for new pages

What are the exact coding style guidelines? I know about the 2-space indent but some files have 4-spaces or even tabs. I can't figure out the import order of the classes or when to use the *.

Is it possible the create such guidelines? Maybe it's even possible to create IDE specific configuration files.

Spun off #150:

Not sure how it might be related, but regular exception thrown from the input method doesn't get an indicator/link in the decision table - just the stack trace displayed prior that, however the custom message exception gets shown in the table. Seems like every exception which gets an indicator where it has happened, is doubly counted.

I've observed the same behavior of not showing indicator for regular exceptions, but for "message exceptions", with script tables, also - for void methods or rows of regular function calls which don't perform symbol assignment, for example.

May be (just may be) solving this would make more obvious which of the two exception increasing statements mentioned in #150 further, is superfluous.

I've had problems with this since the slim.timeout feature was activated and haven't been able to use releases past Jan 9th, 2015. Finally today to take some time to try and figure out what was happening.

Basically I don't want the timeout parameter in use because we have a number of long running tests. However when I specify -Dslim.timeout=0 or any other value on the FitNesse command line, all but the first test fails with the error: Could not complete testing: fitnesse.slim.SlimError: Error connecting to SLiM server on localhost:8088

What I've realized is that it fails on every test except the first port in the pool. So when I run the first test, port 8085 is used and it works. The rest of the tests start incrementing the port though, and even though my slim server comes up on the specified port, FitNesse doesn't appear to recognize it. I assume FitNesse tries to communicate using 8085. If I keep testing until the port loops back to the first in the pool, that test will succeed but then all that follow fail again and it loops back through the pool.

This only happens if I change the timeout parameter on the command line however. And it doesn't help anything if I add the other parameters to the command line too, such as -slim.port or Dslim.pool.size. If I change the time-out, the port pool feature doesn't seem to work.

By the way, I'm not using the java slim client, but PowerSlim instead. Also, I'd be happy to try to use a plugins.properties file, but I don't have one currently and not exactly sure how one would look.

Cloning the repo, checkint out master, and running ant produces a failed build.

I'm running Oracle JDK 8, ant 1.9.4, on Windows 7 (ultimate).

From experience, is this likely to be environmental?

I can see a few errors in the test outputs such as: -

[junit] <span class="error">Could not complete testing: fitnesse.slim.SlimError: Got invalid slim header from client. Read the following: </span>

junit.framework.AssertionFailedError: The regexp <<td><span class="pass">wow</span></td>> was not found in: HTTP/1.1 200

After running a test, we normally share the test with others using the link in browser address bar. This link has the responder ?test and when the other person clicks on this link to view it, it actually executes it instead of just viewing it. This happens too frequently with new members joining a team and sometimes even the experienced members.

Is there any way to redirect to getPage or latest pageHistory after test run is completed so that the link can still be shared without executing?

Over a period of time, there will be a good number of methods/scenario written and used across teams. When it's time to clean-up/refactor those scenario, it's important to know where they are used to assess impact and plan.

After a number of tests already written, if we change a method name in the automaton code, it should be possible to easily modify existing tests with the new methods. It should also retain the existing parameters in the tests.

There is a replace feature already available in FitNesse, we can enhance it to replace method like below.

** General Description ** I'd like to add new node to test XML response, because it would be beneficial to our needs. However, I failed to find a corresponding place in code. Could you please, navigate me, how could I implement this? Thanks in advance!

** What have you tried? ** I tried to inspect the FitNesse code in order to figure out solution on my own

General Description My overall goal is to be able to execute individual tests via the Restful API and then process the response as follows:

1. Extract summary results (right/wrong/ignored/exceptions)
2. Create a link to the full HTML test results (e.g. http://host.com:8000/ClientSuites.ClaimsMigrationSuites.LossNoticeMigrator?pageHistory&resultDate=20221108155215)

This processed response is then stored in a DB. 1 is easily accomplished with a regex. 2 is more difficult as explained next.

The test results HTML has this timestamp info:

If the API response had this timestamp as well, I could easily construct the link to the full HTML results. Alas, the API response does not include this timestamp.

What have you tried?

I tried generating a timestamp in my code (Java) just before the call to the FitNesse API but, alas, the code generated timestamp does not reliably correspond to the test timestamp (it seems to differ by 1 second and I'm not confident that's reliable).

Can someone provide a way to solve this problem?

I've been hosting fitnesse.org for twenty years or so; but the time is coming when this should change. I suggest that the contents of fitnesse.org be moved to a github static website. Also, at some point, fitnesse deserves it's own github account.