'save screenshot after error' for 'check is'?

[raboof]

I like saving screenshots after errors.

I also like using 'check is' rather than 'ensure do', because it will show be right in the test results the difference between what was encountered and what was expected.

However, unless I misunderstand the slim protocol (and a quick glance at the code seems to confirm this), Xebium doesn't know the expectation of the 'check is' command, so it has no way of determining whether a command was in error.

Do I understand this correctly? Can we have the best of both worlds? How?

[marceloverdijk]

+1
This would be very nice

[raboof]

To do this properly I think we'd need to add something at the FitNesse side, see unclebob/fitnesse#211

[amolenaar]

Do we need our own table type? I think that would resolve quite a few issues that we've seen lately.