Integration testing with Testcontainers
Automatic integration tests as part of the development life cycle can save a lot of time and money. Not only when dealing with other service APIs or offering some, also if the application …
Explore this topic 2 pages
- News
Database testing with Citrus
Database communication is an essential part of many applications, when persistent data storage is required. May it be orders, customer data, product recommendations or product information, …
Archived articles (32)
- — Automated CI/CD Build Pipeline with Jenkis in OpenShift
- — Introducing Citrus Admin Web UI
- — Java aktuell - Automatisiertes Testen in Zeiten von Microservices
- — Testing web-applications with a Citrus twist
- — Devoxx Talks about HTTP2 and Citrus Framework
- — Arquillian & Citrus in combination - Part 2
- — Arquillian & Citrus in combination - Part 1
- — Apache Camel integration testing - Part 3
- — Apache Camel integration testing - Part 2
- — Apache Camel integration testing - Part 1
- — Automated Integration Testing for webMethods with Citrus Part II
- — Citrus 1.4 is here!
- — Automated Integration Testing for webMethods with Citrus
- — Citrus 1.3 released
- — Citrus 1.2 Final
- — Validate Excel files in Citrus
- — Use TestNG data provider with Citrus
- — Citrus 1.2.M2
- — Citrus 1.2.M1 released
- — Integrate your own SoapAttachment Validator into your Citrus project
- — Citrus and TestNG groups
- — Citrus 1.1 released
- — Citrus with SOAP-ENV:mustUnderstand headers
- — Citrus: More XPath validation power
- — Citrus: XPath validation power
- — Citrus sources on GitHub
- — Localized citrus.properties
- — Citrus: Latest 1.1-SNAPSHOT version available
- — Customizing meta information
- — Performance testing with Citrus
- — Citrus still improving
- — Citrus 1.1-SNAPSHOT released