kompile-testing alternatives and similar libraries
Based on the "Tests" category.
Alternatively, view kompile-testing alternatives based on common mentions on social networks and blogs.
-
-
Kotest
Powerful, elegant and flexible test framework for Kotlin with additional assertions, property testing and data driven testing -
-
-
kotlin-faker
https://serpro69.github.io/kotlin-faker/ Generate realistically looking fake data such as names, addresses, banking details, and many more, that can be used for testing and data anonymization purposes. -
hikaku
A library that tests if the implementation of a REST-API meets its specification. -
-
minutest
Simple, Expressive, Extensible Testing for Kotlin on the JVM -
balin
Balin is an automation library for Kotlin. It's basically a Selenium-WebDriver wrapper inspired by Geb. -
arbitrater
Arbitrater is a Kotlin library for creating arbitrary instances of classes by reflection for use in testing. In contrast to POJO generators, it supports Kotlin's optional parameters and nullable types. -
SeleniumBuilder
Kotlin DSL for Selenium. Provide a possibility to write tests in Kotlin type-safe builders style -
aspen
Aspen is a simple test runner for Kotlin that allows you to write tests using your own DSL. -
-
mock-fuel
JUnit 5 extension to easily test with the http client Fuel for Kotlin
Appwrite - The Open Source Firebase alternative introduces iOS support
Do you think we are missing an alternative of kompile-testing or a related project?
|
Clean code begins in your IDE with SonarLint
sponsored
www.sonarlint.org
|
Popular Comparisons
-
kompile-testingvsatrium
-
kompile-testingvshikaku
-
mockkvsmockito-kotlin
-
Kotestvsspek
-
Kotestvsmockk
|
Access the most powerful time series database as a service
sponsored
www.influxdata.com
|
README
kompile-testing 
A library for testing kotlinc compilation with kotlin annotation processors(kapt) which is strongly inspired by google/compile-testing.
kompile-testing gives you an easy way to assert not only annotation processors can handle incorrect inputs and prints the correct errors but also the generated Kotlin file is correctly formed.
NOTE: Current library's status is still in development especially due to performance issue. Use at your own risk:D
Installation
latestVersion is 
dependencies {
testImplementation "org.permissionsdispatcher:kompile-testing:{latestVersion}"
}
Usage
A simple example that tests compiling a source file succeeded and make assertions about generated file is:
kotlinc()
.withProcessors(YourProcessor())
.addKotlin("input.kt", """
import kompile.testing.TestAnnotation
@TestAnnotation
class TestClass
""".trimIndent())
.compile()
.succeededWithoutWarnings()
.generatedFile("generatedKtFile.kt")
.hasSourceEquivalentTo("""
class GeneratedKtFile
""".trimIndent())
You can also test that errors or warnings were reported.
The following tests compiling a source file with an annotation processor reported an error:
kotlinc()
.withProcessors(YourProcessor())
.addKotlin("input.kt", """
import kompile.testing.TestAnnotation
@TestAnnotation
class TestClass
""".trimIndent())
.compile()
.failed()
.withErrorContaining("Expected error message here.")
License
Copyright (C) 2019 permissions-dispatcher contributors.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*Note that all licence references and agreements mentioned in the kompile-testing README section above
are relevant to that project's source code only.