v1.1.4: Release of 1.1.4

Pull requests:

• #107 Fix issue #106 (@ihostage)

Commits:

• 5ee8c7e Report task steps correctly when an error occurs in a task step (@wakaleo)

• 65da516 Added the Question as a concept. (@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);

  }

• 7848a32 Test refactoring (@wakaleo)

• 7ae80bf Test refactoring (@wakaleo)

• 7f8f10c Fix issue #106 (@ihostage)

• 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)

• c0b0fff Added support for TypeSafeConfig (@wakaleo)

• cd553eb Improve readability of "View stack trace" dialog (#103) (@wakaleo)

• d29c52e Minor refactoring (@wakaleo)

• e50e557 Refactored a unit test for more clarity (@wakaleo)

• eeb1f73 Works for nested failing tasks (@wakaleo)

• f353c36 Refactoring (@wakaleo)