Fitnesse: the results for |check not| for BLANK is confusing me

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

The right exporting folder

check execute cmd /c dir /B “C:\ExportEmpty” BLANK
check not execute cmd /c dir /B “c:\ExportNotEmpty” [2d1313b9-cfb8-4405-8e5f-91f34b5a1e08 ]

expected [BLANK]

The best way is to say NOT EXPECTED [BLANK]

the script for the page:

|check|execute|cmd /c dir /B “C:\ExportEmpty”|BLANK|
|check not|execute|cmd /c dir /B “c:\ExportNotEmpty”|BLANK|

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

Schools kill creativity

Check this out

I heard a great story recently — I love telling it — of a little girl who was in a drawing lesson. She was six and she was at the back, drawing, and the teacher said this little girl hardly ever paid attention, and in this drawing lesson she did. The teacher was fascinated and she went over to her and she said, “What are you drawing?” And the girl said, “I’m drawing a picture of God.” And the teacher said, “But nobody knows what God looks like.” And the girl said, “They will in a minute.” – by Ken Robinson

dotNetInstaller is a widely used, general-purpose setup bootstrapper

dotNetInstaller enables the developer to define the application prerequisites and install the correct version(s) of these components in a predictable order based on the processor architecture, user operating system type and language, allow the user to download these components from the web, install these components directly from a single packaged setup, local media or both. dotNetInstaller is very feature rich and runs on all known Windows operating systems with a very tiny footprint.

A boostrapper doesn’t replace tools like InstallShield, Wise, Visual Studio Setup and Deployment Project or Wix. The goal is to create an application to help users with installing the correct prerequisites. Most real world applications need to install several components to work properly, including Windows Service Packs, Internet Explorer, MDAC or .NET Framework. This kind of applications are most commonly known as bootstrappers. dotNetInstaller is such a bootstrapper.

Release notes should be tested as well

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
Interesting case have got today. We had started using Fitnesse for acceptance testing 3 years ago.
Now we have big test suite (~ 1000 tests) on Fitnesse. There are useful feature in it – Symbolic Links.
When you can just make a new test with small changes in the defines.
Have done this to test my product against new environment.
And found that my product doesn’t support some things. Several tests are red.
Stay these tests as red in my regression suite is not a good idea.
Remove these symbolic links (kill these tests) for the new environment also is not a good idea.
So I need to add the records to the Release Notes and have the 3rd color for such tests.
So Release notes should be tested as well as the production feature.
But these tests should not be green or red.
BTW: you’ll get the signe if you fix something from RN accidentally:)