You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2021/07/13 08:31:00 UTC
[jira] [Commented] (SLING-10547) JUnit TeleporterRule sets
incorrect Sling-Test-Regexp
[ https://issues.apache.org/jira/browse/SLING-10547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379728#comment-17379728 ]
Bertrand Delacretaz commented on SLING-10547:
---------------------------------------------
I agree this looks like a bug.
> JUnit TeleporterRule sets incorrect Sling-Test-Regexp
> -----------------------------------------------------
>
> Key: SLING-10547
> URL: https://issues.apache.org/jira/browse/SLING-10547
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: JUnit Tests Teleporter 1.0.22
> Reporter: Julian Sedding
> Priority: Minor
>
> The {{ClientSideTeleporter}} sets the {{Sling-Test-Regexp}} to the fully qualified class name (FQCN) of the test-class followed by a wildcard (".*"). This causes inner classes to be matched as tests. Since the {{TeleporterRule}} is meant to package individual test classes into an ad-hoc bundle for automatic deployment, it seems more appropriate to set the regexp just to the FQCN of the test-class.
> [~bdelacretaz]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)