accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4443) Make performance test category usage consistent with other categories
Date Fri, 02 Sep 2016 17:42:20 GMT


Josh Elser commented on ACCUMULO-4443:

[~ctubbsii], It appears to me that you changed the semantics of PerformanceTests with

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:
>             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

View raw message