Dave Piacente
Now, I think that both of these are great. It's a great starting point. I think, focusing on value is super important. But what I'm also articulating hopefully here and coming to a conclusion and hopefully inspiring you all is to maybe do something like this. But with some additional things. So we're going to, Yes and this and so I think that with that in mind, let's help create a perspective hopefully. Hopefully, all of these elements combined if you put these in your mind. And treat them with as inspiration and a lens to look through. I think it can help inform a path forward for us. And so I like the idea of a manifesto, but I do want something more concrete and actionable. But let's think about this and how it can be applied to test automation. So really the outcome that I'm looking for, starting with the end in mind, I want to start from the ground up in terms of the things we care about. And so I want to find a common language that we can all agree on and describe the foundational elements that lead to success in test automation. So not just values, but also more general attributes in the practices that we all have for wildly successful teams. And I want to write them down into a living document. And so some examples, at least on the value front to get started. I think we should focus on business values or business value rather over test coverage. So the idea of just focusing on 100% test coverage, or 100% browser and device coverage when you lose sight of why you're doing it. It's really focusing on delivering business value. And I think being the conscience of the team over sticking with the status quo just because things have been done a certain way, like we should always look for ways to try to work smarter, reinvent ourselves, and not just work hard just to get something done because this is the way it's been done, or just because somebody says it needs to be done this way. Understanding the underlying motivation and trying to be as effective and efficient at the same time as possible, I think is a bit of a superpower that we have. If we can focus on being the conscience of the team. And then check the things work for customers instead of works on my machine and really focusing on. It's like you can run tests headlessly. That's great. But customers don't run things headlessly. And like, there's kind of this. That's just one example. But that conversation where you want to try as close as you can to have parity with the experience that customers have to make sure that you are actually checking things, in a way that really gets you as close as possible while balancing efficiency and cost. And then, there's no comparison point here, just fast and reliable feedback. Full stop. I think that that's really ultimately, at the end of the day, that's what we're trying to do. We're trying to balance the idea of being technical practitioners, while also being like business analysts in trying to offer this efficient balance of those two perspectives and creating feedback loops so that we can inform all the relevant stakeholders to make sure that they're aware, of when something does work, when something does work, and trying to build high trust, but build it in a way that's like creating a system or set of systems that make people stay informed about the health of what's actually being built, both in terms of code and isolation and then applications in flight, all interacting and working together. And so in terms of zooming in a bit, some examples to get the conversation started around more general attributes. I think this is where the conversation starts to get a bit more interesting. Some examples, team in culture. And by that I mean skills, commitment to quality, and testability to pick the right tools for the job. And robust test framework, and simple authoring, align with team skills that is maintainable and reusable. And stable and scalable test infrastructure. Fast execution at scale executed across browsers in devices with stability baked in reporting and analytics, easily identified flaky tests, see results in real-time, efficient selection and prioritization of tests and test data in isolation. So the ability to mock services systems, generate test data, and create deterministic outcomes with minimum dependencies between tests and systems. Now, I think we can hopefully as you hear this list, think. Oh. Are these all the tenants of what I do in my team or if you think of teams another practitioner that do things really well? I'm trying to think in terms of fundamental pillars that like prop up the success of a team. And in a way this done again vendor agnostic, largely context-free. And my experience for the teams that I have consulted with colleagues, I've talked with customers, I've interviewed for Applitools. The list goes on. I think that these are fundamental like table stakes. Things that everybody ultimately practices and has at their disposal, which are not to say that they're easy or necessarily even fungible, but I think that they are true. It's like where team and culture are probably the hardest one to get right. It's like getting the right people, the right motivation, right mindset. Buy in from leadership, funding, and support for either education and focusing on open source or paying for licenses for commercial off the shelf tools or some combination of the two. I think that's one. And that takes time to grow and nurture. But I think the teams that have done the most wildly successful things with test automation, that's why I put that one first. The other stuff. Also still relevant and necessary. Some kind of robust test framework like you can't do test automation if you don't have a means for making it so people can offer tests simply that actually show up and meet them where they are, creating building blocks for tooling that are ideally in the language, that they're in or making it. So if it's not something they're familiar with that there's good, on ramps for them, in a way that's also maintainable and reusable, so easy for people to keep working and also solve the problem once and not have to have everyone else solve it as well. And then test infrastructure being stable and scalable, I mean, wildly important. The ability to scale horizontally and vertically, horizontally, being you want to have as fast as possible, so you scale out to across as many browser devices as possible, vertically being across different platforms, operating systems, browsers, and devices. And then, test flakiness being like the most violent and vane of our existence with the ability as we're seeing with new platforms emerging, the ability to bake in, some reliability. So self-healing locators being one fantastic example of that. And then reporting in analytics, I mean, being able to easily identify and flaky tests and potentially even like quarantine them out to triage them so that they don't, introduce doubt and have the freight trust in your solution. Amazing. Seeing results in real-time, with the ability to efficiently select and prioritize tests. And understand what's going on at a glance. Also super helpful. And then being able to of course, when something goes wrong, being able to dive in and understand what's going on and then test data in isolation, largely deserves its own because it's such a massive topic. But the ability to do what you need to do, to simulate a situation. If you catch a bug and you understand that it's like this orchestration between different services or specific data, then you can change the shape as needed and try to really introspect into what you need, where to test different scenarios that a customer run through, by generating test data. And then being able to also test in isolation so that you can actually really hit the other mark of need, the scalable test infrastructure because test isolation is really important if you're going to actually get into scale and test execution. And so, this is just my list, but I really want to know what's on yours. So I would love it if we could start the conversation, at least in the simplest, lovely format, which is to email me. So if you send me an email to the subject Redefining Test Automation to Dave.Piacente, it's [email protected] and let me know what's on your list. That'd be great.