BEGIN:VCALENDAR
PRODID:-//AddEvent Inc//AddEvent.com v1.7//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:20261101T010000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260308T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DESCRIPTION:Integration testing for distributed containerized applications poses new challenges in terms of practices\, tools\, and environments for developers who want to carry out more prod-like integration testing earlier in the development lifecycle.\n\nIn-memory databases are useful but cannot provide the level of assurance needed as you test against a real database. This option is also limited to data services\, but not all services provide an in-memory alternative.\n\nTestcontainers is a framework for instantiating standalone containers for any number of services to test against. The framework offers some out-of-the-box options\, but you can also provide your own image\, and even your own Dockerfile to instantiate the service of your choice.\n\nIn this talk\, we’ll explore testcontainers and push the boundaries in order to explore how they may be used in conjunction with Cloud Native Buildpacks. This approach has the added benefit of ensuring that all testing is carried out on the same container stack.\n\n------\n\nPowered by addevent.com \nShare your next event with us!\n
X-ALT-DESC;FMTTYPE=text/html:Integration testing for distributed containerized applications poses new challenges in terms of practices, tools, and environments for developers who want to carry out more prod-like integration testing earlier in the development lifecycle.<br><br>In-memory databases are useful but cannot provide the level of assurance needed as you test against a real database. This option is also limited to data services, but not all services provide an in-memory alternative.<br><br>Testcontainers is a framework for instantiating standalone containers for any number of services to test against. The framework offers some out-of-the-box options, but you can also provide your own image, and even your own Dockerfile to instantiate the service of your choice.<br><br>In this talk, we’ll explore testcontainers and push the boundaries in order to explore how they may be used in conjunction with Cloud Native Buildpacks. This approach has the added benefit of ensuring that all testing is carried out on the same container stack.<br /><br />------<br /><br />Powered by addevent.com <br>Share your next event with us!<br>
UID:1775919542addeventcom
SUMMARY:Prod-Like Integration Testing for Distributed Containerized Applications
DTSTART;TZID=America/Los_Angeles:20220127T110000
DTEND;TZID=America/Los_Angeles:20220127T120000
DTSTAMP:20260411T145902Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION:https://youtu.be/-7MwaJABmiE
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
BEGIN:VALARM
TRIGGER:-PT30M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR