Skip to content

This release brings support to some of the new features of the Build Failure Analyzer Plugin, closing #148, #170 and #228.
In short, you can now provide your fellow devs with more detail when the reason of a build failure is found.

How do you do this? As I continue to replace a traditional user guide with acceptance tests, I'll suggest that you follow an example from the new acceptance test: "Displaying the number of failed tests" and let me know if you found it easy to follow 😃

Of course, displaying the number of failed tests is just one example usage! Will you use this feature for any other purpose? Let me know!

scaled_81e09cd2c6d6e9ae1edcd4c15168247f

I'm looking forward to hearing your thoughts on the latest changes, and don't forget to 👍 the ideas and suggestions you'd like to see implemented next!

Oh, and one more thing! I'm planning to write an article on how the Screenplay Pattern and Serenity BDD are used on Build Monitor. If you don't want to miss it, follow me on Twitter and Medium!

Best,
Jan Molak


Do you find Build Monitor useful? Support its development :)

Give it a star! ★
Found a bug? Raise an issue or submit a pull request.
Have feedback? Let me know on twitter: @JanMolak

Flattr Button

Assets 3
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.