51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
34 lines
874 B
Plaintext
34 lines
874 B
Plaintext
== Why is this an issue?
|
|
|
|
There's no point in having a JUnit ``++TestCase++`` without any test methods. Similarly, you shouldn't have a file in the tests directory named ``++*Test++``, ``++*Tests++``, or ``++*TestCase++``, but no tests in the file. Doing either of these things may lead someone to think that uncovered classes have been tested.
|
|
|
|
|
|
This rule raises an issue when files in the test directory are named ``++*Test++``, ``++*Tests++``, or ``++*TestCase++`` or implement ``++TestCase++`` but don't contain any tests.
|
|
|
|
|
|
Supported frameworks:
|
|
|
|
* JUnit3
|
|
* JUnit4
|
|
* JUnit5
|
|
* TestNG
|
|
* Zohhak
|
|
* ArchUnit
|
|
* Pact
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|