bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <>
Subject [jira] [Updated] (BIGTOP-685) provide a way to specify the parameters expected by a test
Date Thu, 09 Aug 2012 19:40:18 GMT


Roman Shaposhnik updated BIGTOP-685:

    Affects Version/s:     (was: 0.5.0)
        Fix Version/s:     (was: 0.5.0)
> provide a way to specify the parameters expected by a test
> ----------------------------------------------------------
>                 Key: BIGTOP-685
>                 URL:
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: Tests
>    Affects Versions: 0.4.0
>            Reporter: Wing Yew Poon
>            Assignee: Wing Yew Poon
>             Fix For: 0.4.0
>         Attachments: contract.txt
> Many tests take parameters. Parameters may be passed into a test via system properties
or environment variables. These parameters can be regarded as part of the test's contract.
Over time, with increasing number of tests, it becomes hard to keep track of the set of parameters
that may be used by the tests.
> I propose to address this issue at two levels:
> 1. Introduce an annotation type for annotating a test class with the list of system properties
and environment variables used by it. This allows for the contract to be exposed in the javadoc,
as well as to annotation processing tools.
> 2. Provide utility functions for automatically obtaining the parameters and their values
from the above annotation.
> Not addressed in this proposal: Injecting 2. into the test runner itself (currently we
are running tests through JUnit).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message