Anna Royzman
We're going to be talking about Strategic Solutions. And so then I'm going to give you the strategy guide. But I want to go back to this very important slide. I want to reiterate the only reason that you in this talk is because I want to reiterate to you that you are the customer of test automation, you the manager, user's stakeholder is the customer. And as a customer, this instrument has to fit your needs. It has to be there when you need it. It has to perform tasks that you need. It has to fit in all the environments that you needed it to fit, and it must cover scenarios that you prioritize. If something is important to you, then it should be doing that. I'm going to give you this strategic solution factors first, and then we're going to talk about ownership, because sometimes I've seen a lot of test managers who are not the owners of these solutions. For some reason, they delegate or they assume that somebody else will do it for them and they got very frustrated because it doesn't perform the way they perform. Today, I assume that you in the very high rank school, I'm going to teach you how to define the strategic solutions for your test automation needs. In order to define your strategic solution for test automation, you have to understand your system architecture, your business domain, your SDLC software development lifecycle and release cadence, which is how fast you're doing the release. And you have to evaluate your resources, the skillsets of your people, the number of your people, the time, the technology, and the budgets. Very important. If you're stakeholders, then obviously you deal with the budget and you make decisions on the budget as well. So first you have to have a good understanding of the system architecture and as you can see, there is a lot of different components that you as a trader, if you trading stocks, you probably know if you're not trading stocks, you're not aware how complex the system is. Putting test automation in it and just do it from like users to interface systems. It's impossible and it's not even needed. You have to break down into the chunks and where you can put strategically, where you can put the test of automation. Some of that will be integration testing definitely. But you probably don't want to do end-to-end system testing in automation unless you necessarily need to, but you can do some integration components into test automation. You definitely don't want to put everything all your testing on UI. Look how much happening on the backend. It's like an iceberg, you don't really want to test ever since through UI automation because it's useless. It's crazy. But you probably want to talk, to test more on the backend on the order process block. You want to put some tests of automation on the data in the database? You probably want to put some automation into the messaging system, messaging between your backend and the thirty-party backends. And this is how you approach strategically the test automation solution. You totally never do it for UI. There are some systems where you should be doing through UI because that's the only thing you have. But when you're in a very complex scenario, then break it down. But you have to have a good understanding of the system architecture and this shit has to be in front of you. All this diagram has to be in front of you when you're making decisions for test automation. You have to be confident of the business priorities I put here 4 different businesses. One is on travel business and other social media business. The third one is medical business and the fourth is the entertainment business. What would be the priorities for each? In travel, you will have reliability is like a big deal for you. When the flight don't go as planned then they have to be able to reschedule tickets. There is so much in travel and you probably know if you're frequent traveler, how much social media is totally something different. Analytics statistics is something that is very big deal in the social media. And finding bugs in that area is actually also a big deal because social media is used for business. Digital health aid hospitals rely on it. All your health providers rely on it. The big deal for them is actually people's lives. There is additional layer of compliance on and everything that you test for else and there is an additional regulation. So you don't just provide your testing, but you have to provide the documentation of what was tested and there are certain rules of how you do it. It's a life-threatening situation if you make mistakes and find bugs in it. Definitely different focus. Business priority would be on saving lives. Entertainment streaming, you want to be uninterrupted entertainment is a big deal for uninterrupted experience, and it should give you the choices if you have subscription should be working well and it should be working for you in different countries. Definitely each of these businesses have different priorities and you want to test when you do your automation, you have to put the focus on these business priorities because this will drive your test automation solutions as well. And it also will drive your strategy in test automation strategy, because it will be different for all of them. Then you have to fit your test of automation solution into your software development lifecycle or you have to change your software development lifecycle, which is okay if this is part of the if you are in charge of it or if you are influencer to change your solutions, then go for it and change it so the test automation is not an afterthought, which is often the case. But test automation is actually involved from the early stages and you can enable the teams to use the test the test automation when it's actually needed, not as an afterthought. What I have seen happening is so yeah, we have to develop those of the main those test cases, but we cannot do it in this sprint because we're doing something else. We're going to do the next sprint for this, this case automation for. If it's not for the team who is delivering then what are you doing then? It's really a big deal. And putting the test automation takes time to do its development. Like anything else, it has to be part of your SDLC. For example, if you see over here, I put 3 different I just Google for diagrams. Do you see anywhere with test automation? No, it doesn't. This is testing. What does it mean testing? You cannot do like test automation after your implementation because you have to do deployment and you don't have time for test automation. You have to be plan it carefully because usually what happens is the test automation is either as becoming the technical depth or it's completely not correlated with your software development lifecycle, which is a bit. It means that it's not used when it needs to be used. Be very responsive to your SDLC and where in this SDLC, you want to put your test automation. Very big deal is managing your resources. Resource management is a big deal for any strategic decision. You have to totally evaluate the skill sets of your people. You have to know what they do and what they are capable of. And you have to know the number of people on your team or who can be doing the test automation. If it's not people on your team. So who is actually dedicated to test automation? How much time do they have, do you have on the project? You need to understand the technology because different technology requires different skill sets and you can leverage some of the technology if you're already as an example. So development is already building your front end with certain language, right? Say is Java, for example, it won't make sense to create the test automation solution, which is more or less in Java as well. Doesn't have to be bad what it gives you advantages of it is that the same developers that are coding they could help you with solving some of your issues with test automation because you have like experts next door. Just consider it, it doesn't have to be, but consider it. Also the budget, you need to understand how much money you're spending on test automation. And big deal of test automation is maintenance, because if you create the test and it's no longer valid with the for example, you have a version number two of your software and you have to rework your workflows. Then all of a sudden, test automation is no longer valid. You need to change the test automation script, and it's a reality of a new software development. Don't be surprised. It's not the like, disruption, it's the reality. The test automation solutions and not 100% reusable. They have to be maintain for the next release. And this work has to be taken into consideration as part of the story. It's not a technical debt, it's real work that you have to adjust your test scripts to the new features. It has to be done. Otherwise, you can throw away your test automation. Work allocation. Who is working on test automation when there are some times when you need some resources to put on something else. For example, you can have test automation team, but they need input from your testers and your testers are very busy doing something else. For example, that was hard to release. You need to release now. So then somebody is waiting on somebody. And you have to understand how you can reallocate work if situation like this. So you have to prepare for anything like, any CrowdStrike situation, you have to be prepared for. Project milestones, when you have to deliver at what time you're already committed. And if you are a manager, you know that these are big deals for business and for your management. The milestone, when you put the date on something, you have to hit this date. If you don't hit this date, you don't have a bonus. You have something that on your review, you didn't fit the goal. Milestones are always like those, a commitment that you gave to your management. Just be aware it you have to deliver there as much as you can, you have to. And if you don't deliver to this milestone, then you have to explain why you don't and you better be persuaded from that. But always take into consideration any project that you committed to, all the milestones that you committed to. Growth opportunity to some of you people will be. You have to put into consideration right? When you're thinking about test automation strategy, you have to think about people because people are working with it. Unless you outsource, then you don't have to worry about growth opportunities. People in your team, they would want promotion, they would want to change directions. They would want to acquire new skills for promotion and do use the test automation as part of your growth opportunities strategies as well. When you do planning for people, put some of test automation in there get to the next level kind of situation milestones because you don't want your test of automation to be in the backburner, like assuming that it's always going to be working. You always have the people. You have to use the test automation as another step in people's promotion, for example, doesn't necessarily need to be but to say, Yeah, I want to master this, then make it us a goal for people and use it as a growth opportunity. Just another thing that you want to consider, if you're a manager, you have to have a backup and in your growth opportunities. If people want to get to the level of management or leadership, teach them what I'm teaching you today. Teach them how to create strategies for test automation because it's just a huge deal for everybody in QA or testing. You really have to manage it and you have a long term plans for all of that. Organization goals. So do know where your organization is going because if, for example, the organization wants to retire, some solutions definitely research that. So you prepare because your test automation solution may not work in a new market and then be aware of what the organization planning to. If you are in management, the leadership, you probably will be exposed to some of it. But be proactive about this because you have your internal organization goals aligned with your long term decisions. Okay, I'm going to be giving you for 4 lessons of mastering automation strategy. We're going to go over all those four, but those four last lists define, de-clutter, decouple it all. And we start with. Lesson number one. Define. I'm just going to describe it in this exercise. But you have to do it by yourself. If you already have test automation, then yes, you do. I assume most of you do. Just do this exercise just for yourself. Redefine it. Define the purpose of test automation. Just write it down. What is the purpose of test automation and you'll be surprised because there are some assumptions that are like, you will have to reveal them. What are the purpose of test automation for your. Don't just say that it has to say anything. Then you're going to compare to what you say to what it actually does. The purpose of test automation. What are the priorities of test automation? What are the most major points of their test automation has to give you results, defined measurements. How would you know that test automation is actually does what is intended to do? How do you measure the success? Like by which measurements you would know that by which numbers or whatever it is, you know that it does what you intended it to do. And obviously some KPI, it doesn't have to be. But if you're on it, then use some of those too. This is the like very first step and you have to identify the purpose and priorities, how you're going to measure your success? Then declutter, where to use automation in software development lifecycle. There are different places in the lifecycle where test automation may be useful and where it has to be more or less perform. You can start test automation, at which point you can start it in this SDLC and at which point it has to be workable. Solution has to be workable. It doesn't mean nothing if it's already done. If it's not working, then you have no solution.