Skip to content
This repository has been archived by the owner on Nov 13, 2023. It is now read-only.

Latest commit

 

History

History
113 lines (72 loc) · 5.48 KB

news.md

File metadata and controls

113 lines (72 loc) · 5.48 KB

News

Most recent first

  • 08th of March 2016

1.2.10 release - this release brings an improved aggregated report in the JSON format.

Previous versions of spock-reports already generated a file called .aggregated_data in the reports directory. This file was a JSON representation of all specifications run by Spock, and was used to keep track of tests running in separate processes, so that the index.html file could contain all tests, not only the ones running in the last process to terminate.

This file, however, turned out to be useful when you have multi-projects and end up with multiple index.html reports for each project... because this file is in the json format and is so easy to parse, external tools can use these files to aggregate the summaries of all projects into a single, final report, much more easily.

In this release, the JSON report aggregation file was improved and renamed to aggregated_report.json so that it is more visible and can be freely used by external tools.

  • 14th of February 2016

1.2.9 release - this is the first release to be published on Maven Central!

Many users complained about restrictions regarding Maven repositories in their working place, so hopefully this will help a lot of users to start getting proper reports out of their Spock specifications.

Another worthy new feature in this release is the option to not inline CSS in HTML files, avoiding CSP violations (see issue #54).

  • 6th of January 2016

1.2.8 release - a new feature and a few fixes are included in this release.

Also, the logging framework has been changed from JUL to Slf4J due to several complaints about JUL making it hard to configure the logging behaviour of spock-reports. Now, you can easily choose a logger implementation that is compatible with slf4j, such as Log4j or Logback, and configure it to enable as much logging as you wish from spock-reports!

The new feature: it is now possible to, optionally, include the stack-trace of a Throwable that caused a test failure in HTML reports. This should be useful for developers to track down bugs without having to chase stacktraces using other sources.

  • 15th of August 2015

1.2.7 release - a really quick release this time! That's because the previous release, 1.2.6, unfortunately missed adding support for documentation annotations (@Ignore, @Issue, @See, @Title, @Narrative). Support for all of these annotations have been added in this release (the release notes have been amended to reflect this).

As usual, this release also includes some tiny bug fixes... and template reports are now easier to write.

  • 12th of August 2015

1.2.6 release - this release brings support for parallel builds. Until now, individual specification reports would be created just fine, but the aggregated report would only contain the specifications run by the last Thread of a parallel build. After this release, that is no longer the case!

Other minor improvements were also included in this release, check the release notes for details.

BREAKING CHANGE: for users of template reports, a necessary breaking change had to made: in Specification report templates, to iterate over features you must now call method eachFeature instead of forEach. This was necessary because the old name conflicted with a native method when using Java 8. Sorry for the inconvenience.

  • 8th of March 2015

1.2.5 release - added support for Spock 1.0, which has been released, finally!! Also, but not less important, now spock-reports has support for templates! This lets you make your report look like whatever you want!

  • 14th of February 2015

1.2.4 released - some nice new features included, such as Table of Contents.

  • 08th of November 2014

1.2.3 released - downgraded minimum Groovy version required to 2.0.8 (benefits some Grails users).

  • 03rd of November 2014

Small feature release (1.2.2): added support for @Unroll-ing variables not only in Spec names, but also in block texts (given, when, then...)

  • 01st of November 2014

Bug fix release, 1.2.1. Fixed problems with bad-behaving Specification setup methods and removed usage of some Groovy features to allow running spock-reports with any recent JDK 7 or 8 version.

  • 3rd of August 2014

Release of version 1.2! This release includes full support for @Unroll, amongst other small improvements.

  • 3rd of July 2014

After a long delay, I have finally published the 1.1 release on a public repo, thanks to @JayStGelais contribution. So now spock-reports is available on Bintray's JCenter!

  • 14th of September 2013

Release of version 1.1 with some minor bug fixes and improvements in the information shown in reports. Please check the release notes in the file releases/Release_Notes.txt.

  • 6th of August 2013

Today, I am proud to release version 1.0 of this project! I have made sure to make it as stable as possible so that you can start reading proper reports for your Spock specifications without worries. You can find the jar in the releases directory! Download it, place it in your classpath and you're done! By default, the reports will be saved in the directory build/spock-reports, but you can change that if you want, just check below. I hope you find this project as useful as I have (I actually developed this out of my own need for it!).

I wrote a blog post about the motivation behind this project. Please check it out!