kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Fung (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (KAFKA-440) Create a regression test framework for distributed environment testing
Date Tue, 07 Aug 2012 23:33:09 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430708#comment-13430708
] 

John Fung edited comment on KAFKA-440 at 8/7/12 11:32 PM:
----------------------------------------------------------

Uploaded kafka-440-v1.patch for review. After applying the patch, please do the following:

1. $ chmod u+x reg_test/suite_replication/bin/kafka-run-class.sh
2. Update reg_test/cluster_config.json for "kafka_home" & "java_home" specific to your
environment
3. To run the test, go to <kafka_home>/reg_test and run the following command:
$ python -B bin/reg_test_driver.py
                
      was (Author: jfung):
    Uploaded kafka-440-v1.patch for review. After applying the patch, please do the following:

1. $ chmod u+x reg_test/suite_replication/bin/kafka-run-class.sh
2. Update reg_test/cluster_config.json for "kafka_home" & "java_home" specific to your
environment
                  
> Create a regression test framework for distributed environment testing
> ----------------------------------------------------------------------
>
>                 Key: KAFKA-440
>                 URL: https://issues.apache.org/jira/browse/KAFKA-440
>             Project: Kafka
>          Issue Type: Task
>            Reporter: John Fung
>            Assignee: John Fung
>         Attachments: kafka-440-v1.patch
>
>
> Initial requirements:
> 1. The whole test framework is preferably coded in Python (a common scripting language
which has well supported features)
> 2. Test framework driver should be generic (distributed environment can be local host)
> 3. Test framework related configurations are defined in JSON format
> 4. Test environment, suite, case definitions may be defined in the following levels:
>   4-a entity_id is used as a key for looking up related config from different levels
>   4-b Cluster level defines: entity_id, hostname, kafka_home, java_home, ...
>   4-c Test suite / case level defines:
>     4-c-1 zookeeper: entity_id, clientPort, dataDir, log_filename, config_filename
>     4-c-2 broker: entity_id, port, log.file.size, log.dir, log_filename, config_filename
>     4-c-3 producer: entity_id, topic, threads, compression-codec, message-size, log_filename,
config_filename

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message