Adding annotations to a test prevents the test from running
See original GitHub issueclass SampleTest : BehaviorSpec()
Works fine.
@Category(UnitTest::class)
class SampleTest : BehaviorSpec()
Cannot be run with kotest as an individual test. (gutter icon disappears and right click context menu does not work anymore). This seems like a regression since this worked before I updated the kotest plugin.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
JUnit Annotations Tutorial with Example: What is @Test and ...
This annotation is used if you want to execute some statements before all the test cases for e.g. test connection must be executed...
Read more >Label your tests with advanced JUnit annotations
JUnit 4 comes with some useful annotations which let you label your tests, a little like marking which chapter or topic they fall...
Read more >Setting Test annotation dynamically - java - Stack Overflow
It is not possible to add an annotation to an existing class at ... This example creates a TestNG object and runs the...
Read more >TestNG Annotations - Benefits, Hierarchy & TestNG Test ...
Tests annotate to decide the sequence of the tests that run. Annotations are taken from the Java language and are an excellent tool...
Read more >Learn How to Use TestNG Annotations in Selenium (with ...
In this article, we tried to discuss some of the important TestNG annotations and attributes which are frequently used by testers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
There is a new plugin release pending approval by Jetbrains (they have to approve each upload) that will fix this. Should be approved by Tuesday.
Fixed in the latest plugin release.