Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add interceptor support to Slim's MethodExecutor #724

merged 11 commits into from May 6, 2015


Copy link

@fhoeben fhoeben commented Apr 24, 2015

Adds the option for a Java Slim fixture to 'intercept' all calls made to it by Slim, by implementing fitnesse.slim.fixtureInteraction.InteractionAwareFixture.

This allows a fixture to implement some generic behavior without having to add it to all of its methods invoked by Slim.

Examples of such behavior:

  • exception handling allowing exceptions from any of its methods to be converted to SlimExceptions (without having to implement that in each method invoked), or
  • waiting for the system under test to be in a stable state before invoking the next method (again without having to add that waiting to each method).

Personally I have 2 specific wishes I hope to implement based on this. I'm hoping to extend my Selenium based fixture so that

  1. it will include a screenshot in the FitNesse generated HTML each time a Selenium exception is thrown, and
  2. implement waiting for Angular DOM manipulation to complete before having my fixture's method interact with the browser.
Copy link

@six42 six42 commented Apr 27, 2015

Hi Fried,

sounds like a nice feature which helps to reduce the amout of glue code
to be written.
Could you add a FitNesse page which explains and demonstrates the new
feature with an example.
This will assure that many people can benefit from your new feature.

An example which adds a screenshot or an image to the test results would
be really cool.
But not sure how many dependencies this adds.

Copy link
Collaborator Author

@fhoeben fhoeben commented Apr 27, 2015

I'll try to get around to writing the wiki page.

The screenshot functionality I use, have in mind, adds a Selenium dependency which I fear will be a bit too much to have in FitNesse itself. Adding screenshots is quite a powerful feature in my experience. I already have it in my BrowserTest fixture (invoked as |show|take screenshot|myName|) and even developed a custom Slim table, 'storyboard' (, that does it for each row.

I have exception handling that takes a screenshot currently implemented with a custom 'fixture interaction' (, but this change will make it easier to implement and will remove the need for this customer fixture interaction (and the need to configure it in the wiki using a slim.flags variable).

@amolenaar amolenaar added this to the Next release milestone May 6, 2015
@amolenaar amolenaar merged commit 1e005a9 into unclebob:master May 6, 2015
amolenaar added a commit that referenced this pull request May 6, 2015
Add interceptor support to Slim's MethodExecutor
@fhoeben fhoeben deleted the fhoeben:InteractionWithInterceptorSupport branch May 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants