Releases: jzbrooks/assertk-lint
Releases · jzbrooks/assertk-lint
v1.5.1
v1.5.0
Added
- KotlinAssertionDetector prohibits use of
kotlin.assertin tests - Quick fixes for null check and equality tests for UnusedAssertkAssertion
- Quick fixes for common junit 4 assertions detected by TestFrameworkAssertionDetector
- Quick fixes for common kotlin.test assertions cases detected by TestFrameworkAssertionDetector
Fixed
- Fully qualified function call handling is improved across several detectors
v1.4.0
Added
- EqualityComparisonAssertion prohibits equality expression in
assertThat - CollectionSizeAssertion prohibits
Collection.sizereads inassertThat
Fixed
- UnusedAssertkAssertion flags used assertion subjects in lambda expressions
v1.3.0
Added
- NullComparisonAssertion requires using assertk's
isNotNullandisNullassertions for null assertions - UseIndexAssertion requires using assertk's indexing assertions (
index,first, etc) to make assertions on a particular array or list value
v1.2.1
Fixed
- MapValueAssertion no longer raises issues on array indexing expressions as an
assertThatargument
v1.2.0
Added
- MapValueAssertion requires using assertk's
keyfunction to make assertions on a particular map value - KeySetAbsentAssertion requires using assertk's
doesNotContainKeyfunction to assert a key is absent in a map - KeySetPresentAssertion requires using assertk's
keyfunction to assert a key is present in a map - TryCatchAssertion requires using assertk's
assertFailurefunction to handle expected exceptions
v1.1.1
Fixed
- Updated detector scope to avoid requiring
checkTestSources - kotlin.test assertions were not detected by TestFrameworkAssertionDetector
v1.1.0
Added
- UnusedAssertkAssertion detects unused assertion subjects
v1.0.1
Fixed
- Jar metadata pointed to an incorrect lint issue registry class