Releases: chrysocode/test-as-you-think
Releases · chrysocode/test-as-you-think
Standard streams as a result
All testing steps as stage by stage checked functions
- Improve the execution stage within a time limit and its corresponding assertions.
- Prepare the SUT separately, and other usual test fixtures.
- Prepare the arguments of the target method separately.
- Check the not yet checked testing steps.
- Check the preparation steps of the system under test.
- Check the preparation steps of the arguments of the target method.
- Check the execution steps.
- Check the verification steps.
- Verify no failure happens.
- Verify both the result and SUT expectations.
Fluent assertions as if you meant AssertJ
- Use the AssertJ assertions like an extension of the TestAsYouThink API with its
resultOf()end point.
System under test as a test fixture
- Prepare the system under test as any other test fixture.
- Prepare the arguments from their types.
- Improve errors: each testing stage has its own type of error, and the real failure becomes the cause of the error.
- Verify the cause of a failure with its message.
- Verify failures without having preparation previously.
Cobertura as a code coverage analyzer
- Generate the documentation TOC updating with markdown-toc and commit the documentation change while building with Maven.
- Check code coverage with Cobertura and publish reports to Codecov while building with Travis CI.
Travis CI as a continuous integration platform
- Build the project with Travis CI.
Time limit as an expectation
- Expect that the system under test replies within a time limit.
- Resolve ambiguous method calls in relation to using expression lambdas.
- Start to write a test with the when step.
TestAsYouThink as a Maven distributed OSS library
- Rename the API to TestAsYouThink.
- Choose an open source license.
- Publish artifacts to Maven Central.
- Check version updates.
Test fixtures as method arguments
- Include a data as a method argument during the preparation phase.
- Include two data as method arguments during the preparation phase.
- Include three data as method arguments during the preparation phase.
- Receive method arguments directly as values.
- Specify method arguments.
- Verify failures while invoking methods with arguments.
- Verify the expected exception and the expected message separately.
Given-When-Then as a canvas
- Write an unit or integration test by using the Given-When-Then canvas and full sequence.
- Delegate the system under test instantiation to the API.
- Reduce the syntactic sequence to a When-Then partial sequence (except the determining of the system under test).
- Specify fixtures in the Given step.
- Specify expectations in the Then step.
- Verify the expectations on the system under test, in addition to the result.
- Provide expectations as predicates.
- Verify failures.
- Separate preparations.
- Separate expectations.