How long does your build take? Hours? How many times does your build go red, but no one seems to have broken it? You know it, this build smells, but how you can improve your build and keep it green? It’s easy, Just move the touchy tests to the bottom of the testing pyramid. Talk description: Wait, what is a testing pyramid and how can it help me and my team? Basically, “testing pyramid” is a concept introduced by Mike Cohn in his book “Succeeding with Agile” that explains relevant proportions of unit test cases, integration test cases and end-to-end test cases. But aren’t End-to-End test cases the best!!! Yes I know, they are cool. It seems that the logical way to start testing is to just take the application and execute the workflows that the user is going to perform so we can test the application as a whole and follow actions that a user might do. Sounds great doesn’t it? UI test cases seem so cool, look at this the mouse is moving!! For this reason (and many other valid reasons) we tend to create UI test cases. But then the reality strikes, our builds are slow, fragile and they don’t provide valid feedback, then developers lose trust and faith in our test cases, and that could be the beginning of the end. How I can solve it? It’s easy to follow the pyramid, so we should prioritize our test cases, define a strategy and involve all the team in the development of test cases. During this talk I am not only going to talk about theory, I will apply my experience in the creation of three testing strategies for different projects, like web, mobile and wearable/IOT. Each project has a different shape of our pyramid and during my talk I will show you how to make yours by example. This talk was done at Selenium Conference in Tokyo, I might change the content based on new projects in LINE.

October 25 @ 10:45
10:45 — 11:30 (45′)

Elena Alejo Teissiere