Behavior driven integration with Cucumber and Citrus
summary
Combines Cucumber and Citrus so Gherkin feature files drive real integration tests against a running Spring Boot voting app, exercising HTTP REST, JMS and mail endpoints; Citrus supplies a Citrus object factory and ready-made step definitions so tests run as JUnit and require almost no custom glue code. Demo sends HTTP calls, receives JMS messages, captures SMTP mail with live comparison of subject/body, shows green runs and a deliberate failing assertion, and includes Selenium web steps.
AI-written summary · about
chapters (15)
- 0:00Start
- 5:12Feature specification
- 6:46JUnit Cucumber test
- 7:37Step definitions
- 9:25Data tables
- 11:44Background
- 12:07Scenario Outline
- 15:15Citrus & Cucumber
- 15:48Messaging feature
- 16:26Endpoint Injection
- 18:04Endpoint Configuration
- 18:49Citrus endpoints
- 19:22Mail SMTP messaging
- 21:06JMS messaging
- 29:25Reading & information
related talks
33mBehavior driven integration with Cucumber and Citrus
44mBDD with JUnit 5 and Cucumber
36mBDD With Cucumber
44mSelenium and Cucumber
16mCucumber Tests: Legends and Reality
34mWriting end to end tests with a smile
45mLet's talk about software behaviour (BDD)
29mUsing Selenium and Cucumber to test a healthcare information system