ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Chekanskiy" <>
Subject Re: Review Request 17146: Modify for running test Component Scripts
Date Tue, 21 Jan 2014 18:10:44 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Jan. 21, 2014, 6:10 p.m.)

Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko.


Improved error printing. Now, in the end of log, all failed tests printed with appropriate
stack traces.

Bugs: AMBARI-4370

Repository: ambari


Modified to run stack tests. All tests must be located in /stacks/stack_version/component
directories. Test files must be with following names: test_*.py. If test contain some none
test directories, we need to include them in STACK_EXCLUDE and/or SERVICE_EXCLUDE. All tests
for stack-component pair are running in sub-process, to prevent conflicts with module names.
All python tests of ambari-server are passed. Also, as tests for different components run
in separate test run, statistics for every run accumulated and shown in the end.

Diffs (updated)

  ambari-server/pom.xml 02fd326 
  ambari-server/src/test/python/ 9448bb6 



Tested ambari-server python tests with already commited components tests. Example of non successful
test run:
Component tests with errors:
stack:2.1.1 service:ZOOKEEPER
stack:2.1.1 service:HBASE
Total run:217
Total errors:0
Total failures:3
Total skipped:0


Eugene Chekanskiy

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message