Releases: serenity-bdd/serenity-core
v1.1.10: Release of 1.1.10
v1.1.9: Release of 1.1.9
v1.1.8: Release of 1.1.8
Pull requests:
- #123 feat: the phantomjs ssl-property can now be set using the PHANTOMJS_S… (@wakaleo)
- #121 see #37 (@cliviu)
- #119 Improving logging in ReportService (@HNygard)
Commits:
-
2f1bf50 feat: the phantomjs ssl-property can now be set using the PHANTOMJS_SSL_PROPERTY environment variable, like the PHANTOMJS_BINARY_PATH. Possible options are 'sslv2', 'sslv3', 'tlsv1' and 'any'. (@ddt-tdd)
-
Only record REST responses for non-binary response types.
-
9bd70c2 Changed dependencies back to mockito 1.9.5 to avoid dependency conflict issues (@wakaleo)
-
c6ed01d Added support for multiple browsers in the same test using the Journey pattern (@wakaleo)
v1.1.7: Release of 1.1.7
Commits:
-
7541585 Better integration of Actors and Question objects (@wakaleo)
Actors can now ask questions directly, e.g.
Integer totalCost = dana.asksFor(theTotalCost());
They can also remember the answers to questions for future use:
dana.remember("Total Cost", theTotalCost());
assertThat(dana.recall("Total Cost")).isEqualTo(14);
v1.1.6: Release of 1.1.6
Pull requests:
- #116 fix: Improved error reporting for provided drivers (@nartamonov)
Commits:
-
3006a4e fix: Improved error reporting for provided drivers (@nartamonov)
DriverSources may implement some non-trivial logic, so it is very handy
for debugging to include in stack trace exception occurred while tried to
initialize new webdriver. Especially in multi-node test environment
configurations. -
4404ea3 Refactored the journey demo test (@wakaleo)
To better illustrate tasks/interaction layers.
-
6345844 Removed redundant code that was causing errors in the reports. (@wakaleo)
If there were more than one given clause in a journey-style test, the initial givens where incorrectly nested.
-
743ec7b Revolving dependency conflicts with hamcrest 1.1 (@wakaleo)
-
a208972 Ensure that Consequence steps are not evaluated after a previous step has failed. (@wakaleo)
-
f77a999 Refactoring and better console reporting. (@wakaleo)
-
f7dc3d7 Added support for dropdowns in the interaction-level bundled Performables. (@wakaleo)
v1.1.5: Release of 1.1.5
Pull requests:
- #110 Fix #109 (@ihostage)
- #112 Fix inject Pages in super class (@ihostage)
- #108 Check for existence of the angular object. (@docurban)
Commits:
- 08c6aab Renamed 'serenity-ability-to-browse-the-web' to 'browse-the-web' (@wakaleo)
- 3afdafb Improved reporting of questions (@wakaleo)
- 8bec974 Fix inject Pages in super class (@ihostage)
- b06d961 Fix #109 (@ihostage)
- b7a8e71 Avoid unnecessary error messages with Java 8 lambdas. (@wakaleo)
- cfb3bd6 Check for existence of the angular object. (@docurban)
- d64e692 Refactoring build (@wakaleo)
- d7af4ed Fixed class conflict issue. (@wakaleo)
- ed62f93 Added the "ability-to-browse-the-web" module to the journey module. (@wakaleo)
v1.1.4: Release of 1.1.4
Pull requests:
Commits:
-
5ee8c7e Report task steps correctly when an error occurs in a task step (@wakaleo)
-
7755f2e Simplified variable injection into step descriptions. (@wakaleo)
You can now inject any member variable in the step class by name into step descriptions
You can now use member variables of a step library in the [@step annotation to augment the step description. Just refer to the variable using the name of the variable prefixed by a "#", as shown in this example:](https://github.com/Step annotation to augment the step description. Just refer to the variable using the name of the variable prefixed by a "#", as shown in this example:)
private final String siteName = "Etsy";
@Step("Search for a shop called {0} on the #siteName website")
public void searches_for_shop_called(String shopName) {
homePage.searchForShopCalled(shopName);}
-
95aa4af You can now use #this or #self in a @step description. (@wakaleo)
-
968c403 Better treatment of invalid or undefined fields in step definitions. (@wakaleo)
-
9722c90 You can now include assertions in the tests (@wakaleo)
You can now include assertions in the tests and reports using the Consequence class.
-
9b7c602 Inject step variables by name into step descriptions (@wakaleo)
You can now use member variables of a step library in the [@step annotation to augment the step description. Just refer to the variable using the name of the variable prefixed by a "#", as shown in this example:](https://github.com/Step annotation to augment the step description. Just refer to the variable using the name of the variable prefixed by a "#", as shown in this example:)
@Reported
private final String siteName = "Etsy";
@Step("Search for a shop called {0} on the #siteName website")
public void searches_for_shop_called(String shopName) {
homePage.searchForShopCalled(shopName);}
-
9e49f8c Got successful and failing journey scenarios working, as long as the failing assertion is in the performAs method. Currently, if one of the chained methods fails, the following steps are not executed and the results are unpredictable (@wakaleo)
-
cd553eb Improve readability of "View stack trace" dialog (#103) (@wakaleo)