• New Features
  • API
  • Logic/Core aka write own expectation functions
• Fixes
• Improvements
• Deprecation
• Breaking Changes
• Migrating deprecated functionality
• Sponsors

Full Changelog: https://github.com/robstoll/atrium/compare/v1.2.0...v1.3.0

• none this time

• none this time

• none this time

• none this time

• none this time

• none this time

• all enums in atrium-translations-de_CH were deprecated, switch to atrium-translations-en_GB (we will drop it with Atrium v1.3.0)

We will make a major refactoring on core and logic level. Those changes should not affect most Atrium users. It might affect you if you:

• created own expectation function based on assertionBuilder or other types which are defined in core or logic.
• use an own expectation verb
• we will drop the support for internationalization with 1.4.0, all functions involving Translatable will be deprecated in v1.3.0
• might be we drop en_GB from package names
• might be we move BulletPointProvider to another package

Migration steps/pointers will be provided in the release notes as usual.

The following changes are planned:

• replace Assertion with Proof and along with it rename many types incorporating Assertion in its name or in its package's name => we will remove Assertion and co. with 1.5.0 at the latest)
• re-write reporting entirely, a lot of types in ch.tutteli.atrium.reporting will be affected (could be we move this to 1.3.0)

Planned (previously deprecated or announced)

• dropped support for Kotlin 1.3
• we use the IR compiler backend for JS

Unplanned

• we added an extra parameter (with default) to withHelpOnFailureBasedOnDefinedSubject, a binary BC, please re-compile

• we will drop support for translating the output - API might persist until 2.0.0 but we might already only use UsingDefaultTranslator
• we might introduce interface groups for ReporterBuilder - binary compatibility break
• BulletPointProvider might use a BulletPointIdentifier from a different package
• we might drop the experimental expectExtension such as expect(...).withOptions provide it in a different form

Use the ReplaceWith in the corresponding @Deprecated annotations.

Please have a look at older release-notes in case you don't migrate from 1.0.0

We would like to thank   (Tegonal Cooperative, Bern, Switzerland) for sponsoring the time @robstoll is working on Atrium.

Are you using Atrium at work?

Please consider to support the project as well by:

• sponsoring robstoll (Author and main contributor)
• share your expectation functions with others
• report bugs
• provide feedback in case you miss a feature