[
https://issues.apache.org/jira/browse/BIGTOP-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916224#comment-13916224
]
jay vyas commented on BIGTOP-685:
---------------------------------
Metadata for tests is now en vogue again :) . We are working bigtop
https://issues.apache.org/jira/browse/BIGTOP-1222, gradlelizing the smokes to
make them easier to control, and will be pulling in this meta data in some kind
of user friendly way.
> provide a way to specify the parameters expected by a test
> ----------------------------------------------------------
>
> Key: BIGTOP-685
> URL: https://issues.apache.org/jira/browse/BIGTOP-685
> Project: Bigtop
> Issue Type: New Feature
> Components: Tests
> Affects Versions: 0.4.0
> Reporter: Wing Yew Poon
> Assignee: Wing Yew Poon
> Priority: Blocker
> Fix For: 0.5.0
>
> Attachments: BIGTOP-685-2.txt, TestDummy1a.java, TestDummy1b.java,
> TestDummy2.groovy, 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 was sent by Atlassian JIRA
(v6.1.5#6160)
