[
https://issues.apache.org/jira/browse/ACCUMULO-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459145#comment-15459145
]
Josh Elser commented on ACCUMULO-4443:
--------------------------------------
[~ctubbsii], It appears to me that you changed the semantics of
PerformanceTests with
https://github.com/apache/accumulo/commit/be5c4334a7a6fda223c3213c66f4f9acda8e9f46
By having both categories, {{\@Category(\{MiniClusterOnlyTests.class,
PerformanceTests.class\})}}, developers who don't want to run the
PerformanceTests have to explicit specify them in the excludedGroups too. This
is a change, no?
I don't think the documentation reflects this change. If I'm not off my rocker,
can you please fix the documentation?
> Make performance test category usage consistent with other categories
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-4443
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4443
> Project: Accumulo
> Issue Type: Sub-task
> Components: test
> Affects Versions: 1.8.0
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Priority: Minor
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, performance tests categories are excluded by default in 1.8+
> branches.
> This is unexpected when trying to do a full build.
> It is also documented as being triggered differently than other test
> categories, even though it is using the same basic categorization method.
> For consistency, we should include all tests by default, and update the
> performance tests documentation to match how the other test categories are
> documented and used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
