[
https://issues.apache.org/jira/browse/BIGTOP-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Bukatovic updated BIGTOP-1321:
-------------------------------------
Description:
The TestCLI test cases has some assumptions which are not checked in the test
code. This is a proposal to add checks for each important assumption which
would make some cases fail if not met. This would save us some debugging time
when setting up new test environment and would make this test easier to reuse.
So far, I have identified these:
* the effective user must be hdfs (a root for HDFS)
* the HDFS trash feature must be disabled (`fs.trash.interval` should be 0)
* hdfs://tmp/testcli_TIMESTAMP directory has been really created
I expect there are additional assumptions worth checking, any other ideas?
was:
The TestCLI test cases has some assumptions which are not checked in the test
code. This is a proposal to add checks for each important assumption which
would make some cases fail if not met. This would save us some debugging time
when setting up new test environment and would make this test easier to reuse.
So far, I have identified these:
* the effective user must be hdfs (a root for HDFS)
* the HDFS trash feature must be disabled (`fs.trash.interval` should be 0)
I expect there are additional assumptions worth checking, any ideas? I will add
it here when I find another one.
> TestCLI: check assumptions before the test run
> ----------------------------------------------
>
> Key: BIGTOP-1321
> URL: https://issues.apache.org/jira/browse/BIGTOP-1321
> Project: Bigtop
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 0.8.0
> Reporter: Martin Bukatovic
> Priority: Minor
>
> The TestCLI test cases has some assumptions which are not checked in the test
> code. This is a proposal to add checks for each important assumption which
> would make some cases fail if not met. This would save us some debugging time
> when setting up new test environment and would make this test easier to reuse.
> So far, I have identified these:
> * the effective user must be hdfs (a root for HDFS)
> * the HDFS trash feature must be disabled (`fs.trash.interval` should be 0)
> * hdfs://tmp/testcli_TIMESTAMP directory has been really created
> I expect there are additional assumptions worth checking, any other ideas?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
