[
https://issues.apache.org/jira/browse/BIGTOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285148#comment-14285148
]
Konstantin Boudnik commented on BIGTOP-1608:
--------------------------------------------
bq. what is the advantage of not putting itest in the same build system as the
tests
the advantage is perhaps of pure design aesthetic. iTest is a framework, that
has its own unit and integration tests and can be used outside of the Bigtop,
e.g. it provides good primitives for order test runs, etc. Hence is me pressing
on this as it provides functionality for the test and should be separated in a
different module. I never said it shouldn't be a part of the same build system.
In fact it should be: either of Gradle or Maven. Doesn't have to be in both.
> Create Unified testing solution: Smoke-Tests and Test-Artifacts
> ---------------------------------------------------------------
>
> 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)
