[
https://issues.apache.org/jira/browse/BIGTOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284258#comment-14284258
]
Konstantin Boudnik commented on BIGTOP-1608:
--------------------------------------------
You are making a good point Jay - running tests from the source code, e.g. in a
script form is very convenient. We also need to have a way to publish test jars
along with the released software stack, because the premise and the value-add
of Bigtop was and is to guarantee that the software stack is validated with
fist-class tests built for that particular stack. You can't do it with just
source code - you have to have dependency and version management for that.
That said: for dev. purposes - running from source code is great. But we need
to have a way to publish the jars as a part of the release. I believe Gradle
should allow us to do both. Am I making sense?
> all smoke-tests should compile and use iTest as source, no jar. Remove ITEST
> env variable.
> -------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1608
> URL: https://issues.apache.org/jira/browse/BIGTOP-1608
> Project: Bigtop
> Issue Type: Improvement
> Components: tests
> Affects Versions: 0.8.0
> Reporter: David Capwell
> Assignee: David Capwell
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1608-first-part.patch, BIGTOP-1608.1.patch
>
>
> If you try to run the smoke tests without setting {{BIGTOP_HOME}} they will
> run and be unable to find tests, so nothing runs. This variable should be
> added to checkEnv to make sure its present while running
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
