JarCasting
@RunWith(SpecRunner.class)
public class ExampleTest extends AcceptanceTest<TestResult> {
private final GivenTheWeatherService theWeatherService = new GivenTheWeatherService(this, testInfrastructure);
private final ThenTheAccessLogLinesContaining theAccessLogLines = new ThenTheAccessLogLinesContaining();
private final ThenAssertion<ThenTheResponse, TestResult> theResponse = ThenTheResponse::new;
private final ThenAssertion<ThenTheResponseHeaders, TestResult> theResponseHeaders = ThenTheResponseHeaders::new;
private final WhenTheWeatherIsRequested theUser = new WhenTheWeatherIsRequested(testInfrastructure, "TheUser");
private final ThenTheWeatherServiceWasCalled theWeatherServiceWasCalled = new ThenTheWeatherServiceWasCalled();
@Test
public void assertionTest() {
given(theWeatherService.willReturn().weatherDescription("light rain").forCity("London"));
when(theUser.requestsTheWeather().forCity("London"));
then(theResponse).isEqualTo("There is light rain in London");
and(theResponseHeaders).contains("Content-Length").contains("Date");
}
@Test
public void assertionBuilderTest() {
given(theWeatherService.willReturn().weatherDescription("light rain").forCity("London"));
when(theUser.requestsTheWeather().forCity("London"));
then(theAccessLogLines.containing("GET /weather")).hasSize(1);
}
@Test
public void verificationTest() {
given(theWeatherService.willReturn().weatherDescription("light rain").forCity("London"));
when(theUser.requestsTheWeather().forCity("London"));
then(theWeatherServiceWasCalled.withCity("London"));
}
}
Dependency:
<dependency>
<groupId>io.github.theangrydev.fluentbdd</groupId>
<artifactId>all</artifactId>
<version>8.2.2</version>
</dependency>
You can also depend on the modules core, assertj-extensions, hamcrest-extensions, mockito-extensions and yatspec-extensions separately if you don't need all of them.
Module Stability
| Module | Stability | Comments |
|---|---|---|
| core | Stable | Used by a small Agile team on a daily basis since March 2016, contains the bulk of the Fluent BDD framework |
| yatspec-extensions | Stable | Used by a small Agile team on a daily basis since March 2016, lightweight module that pulls in the YatSpec dependency and provides some small integrations |
| assertj-extensions | Experimental | No real world users yet, added since AssertJ has lots of useful assertion methods that could come in handy |
| hamcrest-extensions | Experimental | No real world users yet, added since Hamcrest is a popular framework that users might already be invested in |
| mockito-extensions | Experimental | No real world users yet, developed as a curiosity to see how integration with Mockito could be possible |
Releases
The versioning scheme follows Semantic Versioning 2.0.0, to help you identify non backwards-compatible changes when you are upgrading.
8.2.2
- Minor release after some refactoring, no functional changes
8.2.1
- Improving the documentation of the
fluent-mockitomodule
8.2.0
- #11 New module:
hamcrest-extensionsthat acts as a bridge for using Hamcrest matchers asthenassertions
8.1.2
- Added some javadoc to the
allmodule with links to javadoc of the other modules
8.0.0
- #15 Fixed by making
WithFluentAssertJ<TestResult>extendWithFluentBdd<TestResult>and callingrecordThenin eachthenandandmethod. This change is not backwards compatible
7.2.2
- Updated transitive dependency versions
- Marked the transitive dependency
yatspec-zohhak-pluginastestscope notcompilescope
7.2.1
- New module:
assertj-extensionsdelegates to theWithAssertionsAssertJ convenience methods - New module:
assertj-extensions-generator, that produces a plugin that is used to generate the source code forassertj-extensions
7.1.0
- Added an
allconvenience dependency that pulls in all the other modules
7.0.0
- Removed the concept of having a base class, instead encouraging using fields that are exposed via the
With*interfaces - New module:
mockito-extensionsthat integrates with Mockito - New JUnit
@RuleFluentMockitoto use in conjunction withFluentBdd, along withWithFluentMockito
6.0.0
- #8 Renamed the library to fluent-bdd. This change is not backwards compatible
- The
groupIdis nowio.github.theangrydev.fluentbddand theartifactIdiscoreandyatspec-extensions - The packages were changed to reflect this, there is now
io.github.theangrydev.fluentbdd.coreandio.github.theangrydev.fluentbdd.yatspec - The
YatspecFluentclass was renamed toFluentYatspec, similarlyWithYatspecFluentwas renamed toWithFluentYatspec - There is a
FluentBddclass that does not require yatspec at all, with a correspondingWithFluentBddinterface
5.0.2
- #7 The functionality implemented in #6 turned out to be a bit too strict about what it considered to be "mutable". Now the definition of "mutable" is that all the fields must be final. This allows synthetic classes (e.g. a constructor reference) to go through, which turned out to be a common way to write ThenAssertion implementations
5.0.1
- Renamed the base class from
FluentTesttoYatspecFluent. This change is not backwards compatible - Support for using
YatspecFluentas a JUnit@Rulealongside aWithYatspecFluentinterface for the BDD methods if you do not want to extendYatspecFluentas the base class for your tests
4.2.0
- #6 Check if
ThenAssertioninstances have been reused. Also relaxed all the instance checks to classes that appear to be mutable (have at least one instance field)
4.1.1
- Minor changes to the validation messages
4.1.0
- #3 Check that the same
Giveninstance is not used more than once. This is to make it harder to accidentally share state by using the same builder style instance more than once. Similarly forThenVerification
4.0.1
- #5 There are now two kinds of
thenmethods.ThenAssertionis used for chained assertions.ThenVerificationis used for a blob verification that is built up. See theExampleTestfor example usage. This change is not backwards compatible sinceThenwas renamed toThenAssertion
3.0.1
- Made the
FluentTestmethods public. Protected was enough, but it's clearer that they are part of the public API if they are public - Fixed some javadoc language issues
3.0.0
- Removed
InterestingGivensandCapturedInputAndOutputsfields. TheTestStatecan be accessed via the interfaceWithTestStateif it is really needed. This change is not backwards compatible since the fields were visible to subclasses ofFluentTest
2.0.1
- #4 Remove
RequestfromWhen. This change is not backwards compatible - Mark
Givenas a@FunctionalInterfacesince it has a single abstract method
1.6.0
- #1 Relax all the wording validation because it was just getting in the way for users rather than providing any value
1.5.0
- Adapt when to given
- Relax the constrains on when you must use
and. Now you are free to useandandgivenandandandtheninterchangeably, so long as the firstgivenis agivennot anandand the firstthenis athennot anand
1.4.0
- Make it clear that the raw yatspec captured inputs and outputs and interesting givens should not be used
1.3.0
- Allow multiple givens of the same type, even if the given is the same instance (this is useful for e.g. priming a rest endpoint for multiple ids)
1.2.1
- Allow multiple givens of the same type, but not exactly the same one
1.2.0
- Lots of javadoc and renamed
ReadOnlyTestItemstoWriteOnlyTestItems
1.1.0
- Do not allow given given (should be given and)
1.0.7
- Make interesting givens and captured inputs and outputs protected because some yatspec plugins (e.g. sequence diagram generator) need to read them
1.0.6
- Updating yatspec to 1.23
1.0.0
- An alternative approach to givensbuilders etc in yatspec