Who broke the build? — Using Kuttl to improve E2E testing and release faster

[chukka]

Author's Name

Ram Mohan Rao Chukka

Author's Bio

Ram is a Senior Software Engineer at JFrog. Previously worked for startup companies like CallidusCloud (SAP Company), Konylabs. Loves Automation, Linux, openSource

Expected time

Standard talk (~40 min)

Language

• French
• English

Abstract

No one wants to be responsible for breaking the build. But what can you do as a developer to avoid being the bad guy? How can project leads enable their teams to reduce the occurrence of broken builds?
In talking within our own teams, we discovered that many developers weren’t running sufficient integration and End to End tests in their local environments because it’s too difficult to set up and administer test environments in an efficient way.
That’s why we decided to rethink our entire local testing process in hopes of cutting down on the headaches and valuable time wasted. Enter Kuttl. Connecting Kuttl to CI builds has empowered our developers to easily configure a development environment locally that accurately matches the final test environment — without needing to become an expert CI admin themselves.
These days, we hear, “Who broke the build?” far less often — and you can too!

Session Outline:

In this session, We’ll cover:
● A quick history of our testing challenges and what led us to Kuttl
● The benefits of our new testing approach — easy to configure and minimal investment
● How we combine Kuttl and CI pipelines for more streamlined testing and fewer broken builds

Session Key Takeaways:

1. When and why we decided to rethink our e2e testing practices and our subsequent discovery of Kuttl.
2. Why Kuttl has been the perfect tool for our developers to perform better local integration/e2e testing without the burden of becoming their own CI administrators.
3. A detailed account of how we utilize Kuttl to set up development environments locally that match our final test

[tormath1]

Hello @chukka, thanks a lot for your very interesting talk proposal! The event is based in Chambéry, France. Any chance to be present in person in September?
Let us know :D

[chukka]

yes , Sure

[chukka]

@tormath1 Can you please confirm the dates as well ?

[tormath1]

Hello @chukka the SummerCamp is the 2nd and 3rd of September 2023. As stated on the website, I'd like to remind you that the SRE SummerCamp is on purpose a low attendance event (~30 participants) - that said, we will be more than happy to have you here :D

[pabluk]

Hi @chukka,

First of all, we really thank you for your participation in the Call for Proposal for SRE SummerCamp 2023.

We are sorry to inform you that your talk, "Who broke the build? — Using Kuttl to improve E2E testing and release faster", has not been selected for SRE SummerCamp 2023.

Unfortunately we were not able to accept your talk this year due to the number of submissions, you can still talk about this topic as a lighting talk during the event or propose this talk in an upcoming SRE France meetup.

We hope you can join us regardless.

Best,

SRE SummerCamp Team