THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Running System Test
- Specify what test cases to run
- Test Report Interpretation
- List of testcases and the description
Quick Start
Running System Test
...
Code Block |
---|
# ================================================ # # Test results interpretations # # ================================================ 1. PASSED case - A PASSED test case should have a test result similar to the following : _test_case_name : testcase_0201 _test_class_name : ReplicaBasicTest arg : bounce_broker : true arg : broker_type : controller arg : message_producing_free_time_sec : 15 arg : num_iteration : 3 arg : num_messages_to_produce_per_producer_call : 50 arg : num_partition : 3 arg : replica_factor : 3 arg : signal_type : SIGTERM arg : sleep_seconds_between_producer_calls : 1 validation_status : No. of messages from consumer on [test_1] at simple_consumer_test_1-0_r1.log : 711 No. of messages from consumer on [test_1] at simple_consumer_test_1-0_r2.log : 711 No. of messages from consumer on [test_1] at simple_consumer_test_1-0_r3.log : 711 No. of messages from consumer on [test_1] at simple_consumer_test_1-1_r1.log : 700 No. of messages from consumer on [test_1] at simple_consumer_test_1-1_r2.log : 700 No. of messages from consumer on [test_1] at simple_consumer_test_1-1_r3.log : 700 No. of messages from consumer on [test_1] at simple_consumer_test_1-2_r1.log : 604 No. of messages from consumer on [test_1] at simple_consumer_test_1-2_r2.log : 604 No. of messages from consumer on [test_1] at simple_consumer_test_1-2_r3.log : 604 Unique messages from consumer on [test_1] : 2000 Unique messages from producer on [test_1] : 2000 Validate for data matched on topic [test_1] : PASSED <---------- Validate for data matched on topic [test_1] across replicas : PASSED <---------- All validations Validate for merged log segment checksum in cluster [source] : PASSED <---------- PASSED Validate index log in cluster [source] : PASSED <---------- 2. FAILED case - A FAILED test case is shown below with data loss in topic test_1 : _test_case_name : testcase_5005 _test_class_name : MirrorMakerTest arg : bounce_leader : false arg : bounce_mirror_maker : true arg : bounced_entity_downtime_sec : 30 arg : message_producing_free_time_sec : 15 arg : num_iteration : 1 arg : num_messages_to_produce_per_producer_call : 50 arg : num_partition : 2 arg : replica_factor : 3 arg : sleep_seconds_between_producer_calls : 1 validation_status : Unique messages from consumer on [test_1] : 1392 <------ Unique messages from consumer on [test_2] : 1400 | Unique messages from producer on [test_1] : 1400 | Unique messages from producer on [test_2] : 1400 | Validate for data matched on topic [test_1] : FAILED <--------- FAILED because of data matched issue on topic "test_1" Validate for data matched on topic [test_2] : PASSED Validate for merged log segment checksum in cluster [source] : PASSED Validate for merged log segment checksum in cluster [target] : PASSED 3. Skipped case will have result similar to the following (No validation status details) : _test_case_name : testcase_0201 _test_class_name : ReplicaBasicTest arg : bounce_broker : true arg : broker_type : controller arg : message_producing_free_time_sec : 15 arg : num_iteration : 3 arg : num_messages_to_produce_per_producer_call : 50 arg : num_partition : 3 arg : replica_factor : 3 arg : signal_type : SIGTERM arg : sleep_seconds_between_producer_calls : 1 validation_status : |
Test Case Description
Kafka System Teststestcase description
Misc
Directory Structure Overview
...
The following describes the steps to troubleshoot a failing case running in a local machine. To troubleshoot failures in distributed environment (e.g. Hudson build failures), please refer to Kafka System Tests
Refer to Running System Test on how to quick starting System Test
...