[
https://issues.apache.org/jira/browse/BIGTOP-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik resolved BIGTOP-685.
-------------------------------------
This has now been committed and will be part of the Bigtop 0.5.0 release.
Wing Yew, could you please open individual JIRAs to start converting tests for
the Bigtop 0.6.0 release?
> 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, contract.txt, TestDummy1a.java,
> TestDummy1b.java, TestDummy2.groovy
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
