Content of Slim Table rendered incorrectly #65

Closed
docbobo opened this Issue Jul 23, 2013 · 6 comments

Comments

Projects
None yet
3 participants

docbobo commented Jul 23, 2013

For some reason the content shown in the slim table is rendered in as HTML text. For example, this is the content of the expected status code.

I already tried both 3.0 and 3.1 of RestFixture as well as different builds of Fitnesse (and even different browsers)

405<br/><i><span class='fit_label'>expected</span></i><hr/><br/>400<br/><i><span class='fit_label'>actual</span></i><hr/><br/>not&nbsp;match:&nbsp;405<br/><br/><i><span class='fit_label'>errors</span></i>

the actual HTML grabbed from Chrome looks like this:

<span class="fail">405&lt;br/&gt;&lt;i&gt;&lt;span class='fit_label'&gt;expected&lt;/span&gt;&lt;/i&gt;&lt;hr/&gt;&lt;br/&gt;400&lt;br/&gt;&lt;i&gt;&lt;span class='fit_label'&gt;actual&lt;/span&gt;&lt;/i&gt;&lt;hr/&gt;&lt;br/&gt;not&amp;nbsp;match:&amp;nbsp;405&lt;br/&gt;&lt;br/&gt;&lt;i&gt;&lt;span class='fit_label'&gt;errors&lt;/span&gt;&lt;/i&gt;</span>
@ghost

ghost commented Jul 23, 2013

I have the exactly same problem. Also tried 3.1 masterbuild and 3.0.

same problem here - makes test results almost unreadable (which kinda defeats my argument for fitnesse 👍

Reading a bit on Slim I don't see how it ever would work as Slim seems to expect plain strings to be returned from the fixture - not formatted HTML as the RESTfixture nobly tries to do.

Owner

smartrics commented Jul 24, 2013

Hi, what version of fitnesse are you using?
On Jul 24, 2013 3:21 AM, "Shawn" notifications@github.com wrote:

same problem here - makes test results almost unreadble (which kinda
defeats my argument for fitnesse [image: 👍]


Reply to this email directly or view it on GitHubhttps://github.com/smartrics/RestFixture/issues/65#issuecomment-21459748
.

docbobo commented Jul 24, 2013

I did some debugging today and there seems to be a compatibility issue between Fitnesse and RestFixture, starting end of January (Fitnesse commit e65c631d). I've created a Fitnesse issue for that and will stick to the old Fitnesse version for now (unclebob/fitnesse#292).

Owner

smartrics commented Jul 24, 2013

Hi, that's what I thought. The code in the master branch of RestFixture
fixes the issue with the incompatibility with the latest version of
fitnesse.
On Jul 24, 2013 9:05 AM, "Boris Prüßmann" notifications@github.com wrote:

I did some debugging today and there seems to be a compatibility issue
between Fitnesse and RestFixture, starting end of January (Fitnesse commit
e65c631d). I've created a Fitnesse issue for that and will stick to the old
Fitnesse version for now (unclebob/fitnesse#292unclebob/fitnesse#292
).


Reply to this email directly or view it on GitHubhttps://github.com/smartrics/RestFixture/issues/65#issuecomment-21469479
.

@ghost

ghost commented Jul 24, 2013

Thanks for the debugging. I was able to run fitnesse with Restfixture without rendering issue by taking 20121220 tag of fitnesse.

smartrics closed this Aug 1, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment