About my time in Split, Croatia; about Schengen rules for travellers, and Uber outside of the US
Continuous Delivery is undoubtedly an excellent methodology for faster and safer deployment. More importantly, it allows us to enforce the behaviour your customers expect from your app.
With a combination of Domain Driven Testing and Continuous Delivery, you can build a delivery system that emphasizes knowing and testing for what your customers are working with, rather than what your requirements specify.
In this talk, we discuss how to integrate Domain Testing tools like Jest, QuickTheory and TextTest with Continuous Delivery to improve your development lifecycle and ensure a higher quality product.
Continuous Delivery (CD) is more than just a deployment pipeline. CD enforces and audits your application's behaviour. This actual behaviour is what your customer interacts with on a daily basis. Continuous Delivery with its rigorous stream of publishing, building and testing, acts as your first customer, your gatekeeper.
While Continuous Delivery is an excellent methodology by itself, Domain Driven Testing practices can empower it even more! These practices emphasize knowing your customers rather than testing for what your requirements dictate.
In this talk, we discuss the core stages of Continuous Delivery and ways Domain Driven Testing can improve this process altogether. As a practice, we examine how Domain Approval Testing tools like Jest, QuickTheory and TextTest can fit into your deployment pipeline. Lastly, we explore at common pitfalls teams face when first introducing Continuous Delivery with Domain Testing.
- Core principles of Continuous Delivery (CD) and Domain Driven Testing (DDT)
- Steps to integrate Domain Testing into Continuous Delivery pipeline
- Common mistakes to avoid when introducing CD or DDT