Konstantin Vlasenko

Good news:) With Fitnesse + PowerSlim the problem described here can be solved gracefully. You can use Test-Path PowerShell CMDlet:

!|script|PowerShell|
|check|eval|Test-Path "C:\ExportEmpty\*"|False|
|check|eval|Test-Path "c:\ExportNotEmpty\*"|True|

With powerslim you can Query a file.

!|script|PowerShell|
|eval |!-function get_lines($file){Get-Content $file | % {New-Object PSObject -Property @{Line=$_}}}-!|

!|Query:PowerShell|get_lines c:\myfile.txt|
|Line|
|text at first line|
|text at second line|

What you can see in the Fitnesse User Guide

You can hide the first row of a table. This allows you to write comment tables that just look like ordinary HTML tables.
The complete table still gets executed, the first row is just hidden by a CSS rule.
Precede the first row with a ‘#’.  (KV comment: will be changed to – instead of # in the upcomming Fitnesse releases)

But I want to expand this definition.
You can use Hidden table heads feature to conceal the needless things in your acceptance test script!

Fitnesse Visual Polymorphism

Imagine that you have two scenarios
------------ScenarioLibrary page------------
|scenario|execute and check|command|
|check|cmd|@command|0|
|scenario|execute|command|
|cmd|@command|
------------ScenarioLibrary page------------
You can use them in your test
------------SetUp page------------
-!|execute|
|command|
|cmd /c rd /S /Q "C:\AnyDirectory"|

-!|execute and check|
|command|
|WMIC product where name='My Product'" call Uninstall|
------------test page------------
The first one tries to delet the directory. cmd will return 0 if success and 2 if directory doesn’t exists. So I am not care about the result. Using the execute scenario.
The second performs the product uninstallation. It is critical to know the result (e.g. if this SetUp page will be included into product setup testing suite). So I use the different scenario execute and check in that case.
But all this things (check or not to check) are just the noise in that case. So I am hidding them into scenario and making the Tables Heads hidden.
The final SetUp page will not have any noise.  Just facts:)

It is too confusing that the Fitnesse highlight expected [BLANK] in second case.

The right exporting folder

The best way is to say NOT EXPECTED [BLANK]

the script for the page:

BTW: Why should I type BLANK for the second scenario? I’ll get the IGNORE result if I left them empty

It is good to have green suite of acceptance tests

If something wrong we should get the red test/tests

We do not have to get used to the red tests