Skip to content

Latest commit

 

History

History
54 lines (36 loc) · 3.33 KB

manual_testing.rst

File metadata and controls

54 lines (36 loc) · 3.33 KB
Raw

Manual testing

The producer can be tested manually against a Kafka running in devstack.

Setting up for testing

  1. Make or refresh a copy of this repo where it can be seen from inside devstack: rsync -sax -delete ./ ../src/event-bus-kafka/ (and rerun rsync after any edits as needed)

  2. In devstack, start Kafka and the control webapp: make dev.up.kafka-control-center and watch make dev.logs.kafka-control-center until server is up and happy (may take a few minutes; watch for INFO Kafka startTimeMs)

  3. Sometimes kafka fails to start, run make dev.up.kafka-control-center again.

  4. Load the control center UI: http://localhost:9021/clusters and wait for the cluster to become healthy

  5. You can either create the topic you want to use for testing manually or perform the action in LMS or studio which will publish the event, creating the topic automatically. For the examples used in the management commands, you'll want to use dev-user-login with default settings.

  6. Update below settings in cms/envs/devstack.py, make sure that they are defined only once.

    EVENT_BUS_PRODUCER = 'edx_event_bus_kafka.create_producer'
EVENT_BUS_CONSUMER = 'edx_event_bus_kafka.KafkaEventConsumer'
EVENT_BUS_KAFKA_SCHEMA_REGISTRY_URL = 'http://edx.devstack.schema-registry:8081'
EVENT_BUS_KAFKA_BOOTSTRAP_SERVERS = 'edx.devstack.kafka:29092'
EVENT_BUS_TOPIC_PREFIX = 'dev'

  7. In edx-platform's cms/envs/devstack.py, add 'edx_event_bus_kafka' and 'openedx_events' to the INSTALLED_APPS list

  8. In devstack, run make devpi-up studio-up-without-deps-shell to bring up Studio with a shell.

  9. In the Studio shell, run pip install -e /edx/src/event-bus-kafka

  10. In the Studio shell, run pip install 'confluent_kafka[avro,schema-registry]' (necessary external dependency)

(Any IDA should work for testing, but all interactions have to happen inside devstack's networking layer, otherwise Kafka can't talk to itself.)

Testing the consumer

The consumer may not read older events from the topic—and it never will for the first run of a topic/group pair—so you may need to started it before the producer, or re-run the producer after the consumer is started.

  • Run below example command:

    python3 manage.py cms consume_events -t user-login -g user-activity-service -s org.openedx.learning.auth.session.login.completed.v1

  • Once an event comes in, expect to see output that ends with a line containing "Received SESSION_LOGIN_COMPLETED signal with user_data"

Testing the producer

The Studio producer can be exercised by setting SEND_CATALOG_INFO_SIGNAL = True in cms/envs/devstack.py and editing a course's settings. Or, it can be invoked directly by management command using the below instructions.

Note: If you're also running the consumer, you'll need to do this in a separate studio shell.

  • Run the example command listed in the edx_event_bus_kafka.management.commands.produce_event.Command docstring
  • Expect to see output that ends with a line containing "Event delivered to topic"
  • Go to the topic that was created and then into the Messages tab; select offset=0 to make sure you can see messages that were sent before you had the UI open.