{"id":73151,"date":"2020-03-09T07:36:00","date_gmt":"2020-03-09T07:36:00","guid":{"rendered":"https:\/\/coforge.site\/cigniti_new\/?post_type=product&p=73151"},"modified":"2024-10-21T06:24:39","modified_gmt":"2024-10-21T06:24:39","slug":"agile-transformation-test-automation-mark-bland","status":"publish","type":"product","link":"https:\/\/coforge.site\/cigniti_new\/resource\/podcasts\/agile-transformation-test-automation-mark-bland\/","title":{"rendered":"Realizing Agile Transformation With Test Automation with Mark Bland"},"content":{"rendered":"

You are listening to QA talks, a podcast for quality assurance executives implementing digital transformation in their organizations. In this show, we focus on the unique pitfalls inherent in quality assurance and quality engineering and how these executives are navigating them to position their organization for the future. Let’s get into the show.<\/span><\/i>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Welcome back to QA Talks. I’m Logan Lyles, your host for today’s episode from Sweet Fish Media. We\u2019ve got with us today two very experienced speakers on the podcast. I\u2019m joined by Mark Bland, Senior Test Manager over at Premier Farnell. Mark, how is it going sir?<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>Hey it\u2019s good. Nice to meet you, Logan.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Great to have you on the show, Mark. I\u2019m also joined by Nanda\u00a0Padmaraju. He is the SVP at Cigniti Technology. Nanda, welcome back. Great to have you on the show for this episode.<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Hey Logan. Thank you\u00a0<\/span>so<\/span>\u00a0much for having me back on this podcast<\/span>.\u00a0<\/span>Pleasure<\/span>!<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Absolutely. Gentlemen, we are going to have a great conversation today about agile transformation, test automation<\/span>,<\/span>\u00a0and some other hot topics for listeners today<\/span>.<\/span>\u00a0<\/span>Before\u00a0<\/span>we do that<\/span>,<\/span>\u00a0I want to provide a little bit of background on both of our speakers for some context. As we mentioned, Mark Bland is senior test manager over at\u00a0<\/span>Premier\u00a0<\/span>F<\/span>a<\/span>rnell with 15 years of experience. During that time, he’s worked on everything from large<\/span>–<\/span>scale platform replacements to small feature delivery on\u00a0<\/span>websites\u00a0<\/span>and mobile apps.<\/span>\u00a0<\/span>He’s managed onshore and offshore resources both directly and outsourced in multiple locations and in functional automation and non-functional disciplines, implementing\u00a0a number of\u00a0tools and frameworks in automation and non-functional testing along the way. He says he accidentally fell into software testing after 10 years of working as an electronic and electro<\/span>–<\/span>mechanical engineer but found that he immediately loved the industry. And now a little bit more about our other guest today,\u00a0<\/span>Nanda.\u00a0<\/span>\u00a0<\/span><\/p>\n

Nanda\u00a0Padmaraju<\/span>\u00a0<\/span>is senior vice president at\u00a0<\/span>Cigniti<\/span>\u00a0Technologies.<\/span>\u00a0<\/span>He is our co<\/span>–<\/span>speaker for this edition of the podcast<\/span>. Nanda heads up the\u00a0<\/span>UK<\/span>–<\/span>EU business unit for\u00a0<\/span>C<\/span>ignit<\/span>i<\/span>. He brings in 22 years of experience in consulting, advising<\/span>,<\/span>\u00a0and helping global enterprises across domains in their quality assurance and quality engineering transformation.\u00a0<\/span>\u00a0<\/span><\/p>\n

All right. Now that we’ve set the stage a little bit, Mar<\/span>k<\/span>, I want to turn to you with our first question for today. You know, agile and DevOps really transform the way enterprise functions today.<\/span>\u00a0<\/span>I think\u00a0all of\u00a0our listeners really understand that. I’d love to kick it off with a question for you about, you know, really, what would you say are the primary characteristics required in an agile transformation from leadership?\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>Yes. Well, I think first and foremost, you’ve got to be open<\/span>–<\/span>minded and willing to embrace\u00a0<\/span>change. I think I’ll give you an opportunity to work together as a team and really deliver something with a common goal rather than traditional methods, which would have been some way that teams working against each other at times.<\/span>\u00a0<\/span>So<\/span>\u00a0you’ve got the ability to listen to other people’s opinions. They’re willing to have your opinion challenged. I found that that is probably one of the one of the bigger ones. They just haven’t been willing to have your opinion challenged and accept that, you know, whilst your\u00a0<\/span>way<\/span>\u00a0might not be a particularly wrong, it might not be the best way. You’ve got a collaborative mindset. You’ve got to be one willing to work with other people and\u00a0and\u00a0contribute to work as a team.<\/span>\u00a0<\/span>And one of the things I think I find really helped me along the way\u00a0<\/span>is<\/span>\u00a0learning to step back and allow my team to self-organize and not only make but learn from their own mistakes without jumping in and micromanaging<\/span>\u00a0them<\/span>. I think as a manager, Agile really is about taking a step back and letting the teams do what we hired the teams to do and get to\u00a0<\/span>round it<\/span>. Oh, I would summarize that. You know, it takes a lot of courage and trust.<\/span>\u00a0<\/span>I think as a manager, I need to trust my team\u00a0<\/span>and I need to have<\/span>\u00a0the courage to like\u00a0<\/span>stand<\/span>\u00a0back and let them deliver using the skills that I hired them for, but also pass that message back up to my management and go the other way with that. You know, and coach my management to trust that we will deliver what<\/span>\u2019s been asked of\u00a0<\/span>us.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Mark<\/span>, I love the way that you rounded that up there. You know, for listeners, I think you hit on four key elements<\/span>\u00a0<\/span>ther<\/span>e \u2013<\/span>\u00a0humility and approach of collaboration, leadership that does not micromanage<\/span>,<\/span>\u00a0trust<\/span>\u00a0\u2013\u00a0<\/span>fostering that within your team<\/span>,<\/span>\u00a0and also kind of managing up<\/span>\u00a0and\u00a0<\/span>looking to build trust and\u00a0instill\u00a0trust in in your leadership as well. You know, Mark, some people talk about this difference between doing agile and, you know, kind of dipping your toe in the water and being agile.<\/span>\u00a0<\/span>Do you see a big difference between those two mindsets in your experience with your teams?<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>Oh, absolutely yes. Something,<\/span>\u00a0<\/span>simply\u00a0<\/span>put, you can follow all the steps and run an agile process and stick to all the rules and guidelines set out for best practice<\/span>s<\/span>. We’re running\u00a0<\/span>agile<\/span>\u00a0and you can do all that while still underneath\u00a0<\/span>I\u2019ll<\/span>\u00a0believe\u00a0<\/span>it’s\u00a0<\/span>just a fad or a trend and just pay the whole thing lip service<\/span>.<\/span>\u00a0<\/span>So,\u00a0<\/span>you’ll manage<\/span>, y<\/span>ou’ll get well delivered<\/span>,<\/span>\u00a0and you’ll be doing\u00a0<\/span>agile<\/span>. I think what tends to happen<\/span>\u00a0\u2013<\/span>\u00a0I love teams<\/span>\u00a0\u2013\u00a0<\/span>I’ve seen this in transition as far as you start out and that will be some members of your team being in leadership<\/span>, the\u00a0<\/span>people within the team will start out with that, doing\u00a0<\/span>agile<\/span>\u00a0following the rules<\/span>,<\/span>\u00a0mindset. But then what you hope happens is that over time all those people will start to realize the benefit of\u00a0<\/span>delivering<\/span>\u00a0in this way and w<\/span>i<\/span>ll start to buy into the principal and the culture of it. I think that’s when you stop being agile, when everything that you do is approached in the agile, collaborative way.<\/span>\u00a0<\/span>So<\/span>,<\/span>\u00a0any challenge you face, you don’t go back to the drawing board and go back to old methods of dealing with these problems<\/span>. You\u00a0<\/span>come together\u00a0<\/span>with\u00a0<\/span>a new solution, not problem. And here you do\u00a0<\/span>that in a way that\u00a0<\/span>best serves<\/span>\u00a0the scrum team. And if you’re doing scrum<\/span>\u00a0out there in the<\/span>\u00a0delivery team, whichever message you use in best delivers the best result for your end user and your customer.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>I love that, Mark. So<\/span>,<\/span>\u00a0talking about the end result for the end user and customers, you know, customers today are really expecting a world<\/span>–<\/span>class digital experience. They expect it to be seamless, frictionless<\/span>\u00a0\u2013 al<\/span>l of those buzzwords that we hear, you know, and I know that you’re involved in making that digital experience better for your customers at F<\/span>a<\/span>rnell. Can you share some specific ways that you’ve started to orchestrate and implement some of those changes for customer<\/span>–<\/span>facing experience?<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>Yeah, I’m by no means an expert on this. I have my views and things that work for me. But I think implementing testing practices as a whole that enable a faster delivery and the\u00a0<\/span>test code in a really short<\/span>\u00a0timescale is the key<\/span>. Contirbuting more to the<\/span>\u00a0team<\/span>,<\/span>\u00a0<\/span>for\u00a0<\/span>me, getting more involved with the solution\u00a0<\/span>and<\/span>\u00a0the\u00a0<\/span>sculpting\u00a0<\/span>side of the applications<\/span>,<\/span>\u00a0the<\/span>\u00a0<\/span>ne<\/span>w<\/span>\u00a0things that we were delivering and making sure\u00a0<\/span>we are catching<\/span>\u00a0any failure at all\u00a0<\/span>and\u00a0<\/span>risk<\/span>s<\/span>, but also making sure that we can feed back at that point<\/span>\u00a0the\u00a0<\/span>experiences we’ve had with customers and the negativity we’ve seen with things that haven’t\u00a0<\/span>worked<\/span>\u00a0in the past. I think one of the things that moved us forward a lot in terms of providing\u00a0<\/span>a better<\/span>\u00a0solution for our customers was introducing the likes of security test into our basic automation test, smoke tests<\/span>,<\/span>\u00a0and principles. So covering another risk that customers base is very aware of in terms of\u00a0<\/span>their\u00a0<\/span>security and financial data security, those kind of things, but also looking at how you can then expand on that and look at introducing early and testing for accessibility in those kinds of usability challenges that you’ve started to come to the forefront really in terms of creative design and and application design.<\/span>\u00a0<\/span>All the things we tried to focus on were expanding our automation coverage to cover more variations,\u00a0<\/span>of\u00a0<\/span>user scenario, a more compatibility type way. So different browsers, different types of\u00a0<\/span>setup<\/span>\u00a0within the actual application, including mobile variation and tablet variations, all those kinds of things mean that you are trying to deliver a much more rounded quality experience to\u00a0<\/span>you<\/span>\u00a0customer. Beyond that, I think\u00a0<\/span>it all<\/span>\u00a0comes back to the plumbing<\/span>, r<\/span>eally<\/span>.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Yeah, that makes a lot of sense<\/span>, M<\/span>ark<\/span>. So<\/span>,<\/span>\u00a0you<\/span>\u00a0talked about, you know, mobile variations and browser compatibility. Can you go a little bit further there, Mark? You’ve mentioned testing and how that helps you go faster. Can you speak a little bit about, you know, automation testing and in some of the specific increases in effectiveness, efficiency<\/span>,<\/span>\u00a0and coverage of the software testing<\/span>?<\/span>\u00a0<\/span>In\u00a0<\/span>addition to helping you just increase that release velocity, which you mentioned, you know, is a great benefit to the customer experience when you’re able to deliver solutions faster<\/span>, are\u00a0<\/span>there other things that you’ve seen in the benefits of testing automation in the projects that you’ve been involved with?\u00a0<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>So, I think<\/span>\u00a0automation, if you improve it<\/span>\u00a0right, if you<\/span>\u00a0implement<\/span>\u00a0it<\/span>\u00a0correctly, it doesn’t just add another layer of testing.<\/span>\u00a0What, i<\/span>n theory, it should do is move obstacles out of your current test team’s way to enable them to do much more complex and interesting testing. So<\/span>,<\/span>\u00a0you get your teams more engaged because they’re doing the more interesting testing themselves manually.<\/span>\u00a0<\/span>But then you give yourself this capability to expand the breadth of your automation coverage, and\u00a0<\/span>your<\/span>\u00a0test coverage to cover multiple\u00a0<\/span>web\u00a0<\/span>browsers, cover multiple combinations of compatibility issues to cover\u00a0<\/span>security,<\/span>\u00a0to cover\u00a0<\/span>a\u00a0<\/span>lots more functionality<\/span>.<\/span>\u00a0<\/span>For\u00a0<\/span>ourselves<\/span>,<\/span>\u00a0<\/span>one\u00a0<\/span>of the big challenges we had was that we actually have\u00a0<\/span>48<\/span>\u00a0<\/span>web<\/span>sites<\/span>.<\/span>\u00a0<\/span>Across\u00a0<\/span>those\u00a0<\/span>48<\/span>\u00a0Web sites<\/span>,<\/span>\u00a0<\/span>we\u00a0<\/span>cover 28 languages. So<\/span>,<\/span>\u00a0there’s a lot of variation in that as a manual test<\/span>.<\/span>\u00a0<\/span>If\u00a0<\/span>you were to test all of that and make sure it was right in all those scenarios<\/span>, you’ll\u00a0<\/span>be there for weeks. The automation gives us the ability to write a single set of\u00a0<\/span>tests<\/span>\u00a0that we can roll out with just environment variables to cover those variations. I think<\/span>,<\/span>\u00a0<\/span>in\u00a0<\/span>theory,<\/span>\u00a0it<\/span>\u00a0gives you that capability to test\u00a0<\/span>wider<\/span>, reduce regression times<\/span>,<\/span>\u00a0and expand the\u00a0<\/span>amount<\/span>\u00a0of tests you\u00a0<\/span>are doing,<\/span>\u00a0all in a much smaller time<\/span>frame<\/span>, which is\u00a0<\/span>in<\/span>valuable\u00a0<\/span>be<\/span>cause<\/span>,<\/span>\u00a0as\u00a0<\/span>we all know,<\/span>\u00a0time<\/span>–<\/span>to<\/span>–<\/span>market<\/span>\u00a0is<\/span>\u00a0the biggest demand<\/span>\u00a0now.<\/span>\u00a0I’m a firm believer that there’s a shift in our market from quality assurance to delivery assurance where people are more concerned about\u00a0<\/span>getting<\/span>\u00a0things fast and<\/span>\u00a0about<\/span>\u00a0getting things right, you know.<\/span>\u00a0<\/span>So<\/span>,<\/span>\u00a0we’ve really got to cater to our customers\u00a0<\/span>with that<\/span>\u00a0and be able to deliver<\/span>\u00a0at that pac<\/span>e<\/span>\u00a0while<\/span>\u00a0keeping that risk low.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Well<\/span>, Mark, that is a really good connection because anytime that we approach things with the end in mind\u00a0<\/span>and<\/span>\u00a0what is the customer’s viewpoint, you make a really great connection there between the expectation of speed of delivery, even more so sometimes over quality and thinking about those shifts and how they impact how do we go to market.\u00a0<\/span>\u00a0<\/span><\/p>\n

Nanda,<\/span>\u00a0we’ve introduced a lot of your experience at the top of the episode, and I haven’t given you a chance to to chime in here<\/span>.<\/span>\u00a0<\/span>Since\u00a0<\/span>we’re jumping in on testing a good bit here<\/span>, a<\/span>s Mark’s been talking about automation, you know, many customers have benefited from\u00a0<\/span>Cigniti\u2019s<\/span>\u00a0test advisory and transformation service. Can can you elaborate on some of the benefits customers have seen from this service<\/span>\u00a0w<\/span>hile we’re on the subject of testing here.<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Sure<\/span>, Logan. I’ll take a real example. We work with a\u00a0<\/span>large Airline<\/span>\u00a0conglomerate. They have five brands<\/span>.<\/span>\u00a0<\/span>Most\u00a0<\/span>of them came into the<\/span>ir<\/span>\u00a0<\/span>fore through M&A<\/span>\u00a0route<\/span>\u00a0and\u00a0<\/span>hence have<\/span>\u00a0their own code base, their own teams, their own vendors, frameworks<\/span>,<\/span>\u00a0and tools.<\/span>\u00a0<\/span><\/p>\n

When we landed up with the client<\/span>\u2019<\/span>s place, we gave them a thirty<\/span>–<\/span>thousand feet view of why they need to kick start a common approach that is then drawn down by all the\u00a0<\/span>brands<\/span>.<\/span>\u00a0<\/span>Aspects\u00a0<\/span>such as scalability, reusability, maintainability can drive a lot of efficiency gains that translate into multi-<\/span>million dollar<\/span>\u00a0<\/span>savings<\/span>\u00a0p<\/span>er\u00a0<\/span>year for large enterprises<\/span>. Tool rationalization<\/span>,<\/span>\u00a0focused approach to increasing release velocity<\/span>,<\/span>\u00a0and moving from waterfall agile\u00a0<\/span>\u2013\u00a0<\/span>agile is a topic that Mark touched upon earlier, and very rightly so<\/span>\u00a0– and\u00a0<\/span>now to DevOps, which includes all aspects, including the culture, people, tools<\/span>,<\/span>\u00a0and technologies,\u00a0<\/span>are<\/span>\u00a0all initiatives that are an outcome of the advisory and\u00a0<\/span>transformation<\/span>\u00a0service that\u00a0<\/span>Cigniti<\/span>\u00a0offers. We have a group of top<\/span>–<\/span>notch consultants who are the best of the breed come with loads of relevant experience and they normally operate at\u00a0<\/span>a CIO<\/span>–<\/span>level Logan.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>That is<\/span>\u00a0a great rundown there,\u00a0<\/span>Nanda.<\/span>\u00a0<\/span>That\u00a0<\/span>sounds like the team has been doing some really top<\/span>–<\/span>notch work. Can you speak a little more broadly as well\u00a0<\/span>Nanda on<\/span>\u00a0just the importance of having an enterprise test strategy and maybe a little bit on how\u00a0<\/span>Cigniti<\/span>\u00a0can help build one for customers, so one two punch there<\/span>\u00a0and\u00a0<\/span>in the response\u00a0<\/span>here<\/span>.<\/span>\u00a0<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Sure<\/span>, Logan<\/span>.<\/span>\u00a0<\/span>At C<\/span>ignit<\/span>i<\/span>, we believe in having a signed off\u00a0<\/span>enterprise\u00a0<\/span>test strategy is fundamental to ensuring quality in everything that goes into production.\u00a0<\/span>The test<\/span>\u00a0strategy will act as a Bible and not just for the testing function, but also for the upstream\u00a0<\/span>Dev\u00a0<\/span>and downstream\u00a0<\/span>Ops<\/span>. It will guide the business analyst to document not only the functional requirements, but also the non-functional<\/span>\u00a0<\/span>requirements upfront.\u00a0<\/span>It will analyze<\/span>\u00a0how we can drive the ambiguity\u00a0<\/span>out of<\/span>\u00a0the requirements early on using the shift<\/span>–<\/span>left practices.<\/span>\u00a0<\/span>It will clearly state that\u00a0<\/span>quality<\/span>\u00a0gate criteria. It will encourage the adoption of agile and DevOps as their enterprise\u00a0<\/span>test\u00a0<\/span>strategy needs to be aligned with the overall objective of I<\/span>T<\/span>\u00a0and that\u00a0<\/span>of the<\/span>\u00a0business. Leveraging the latest tool sets and focusing on being an independent\u00a0<\/span>voide of quality<\/span>\u00a0in the\u00a0<\/span>S<\/span>DLC is better achieved when you have an agreed\u00a0<\/span>enterprise test<\/span>\u00a0strategy<\/span>. Cigniti leverages our<\/span>\u00a0collective wisdom of serving hundreds of customers and bring<\/span>\u00a0<\/span>in the best practices while understanding the context and constraints of each customer in putting together the most relevant, practical\u00a0<\/span>enterprise test<\/span>\u00a0strategy that works and is aligned to the overall vision of the CIO office.<\/span>\u00a0<\/span><\/p>\n

Individual projects will then draw down and prepare project level\u00a0<\/span>test<\/span>\u00a0strategies\u00a0<\/span>or test\u00a0<\/span>plans to ensure they stay aligned and are combined with the enterprise\u00a0<\/span>test strategy<\/span>. Back to you, Lo<\/span>gan.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Thank you for that<\/span>, Nanda<\/span>. That collective wisdom<\/span>,\u00a0<\/span>I loved hearing that line that you just shared. You know, Mark,\u00a0<\/span>Nanda\u00a0<\/span>was speaking a little bit there about the toolset. You know, automation testing<\/a> is highly tool<\/span>–<\/span>dependent. Can you talk about the challenges that you’ve had to address to identify the right automation testing tool for your application landscape<\/span>?<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Absolutely<\/span>, yeah<\/span>.\u00a0<\/span>So<\/span>\u00a0we like all companies and organizations that think about our fair share of challenges with this.<\/span>\u00a0<\/span>When<\/span>\u00a0I earlier joined the team that I’m in now, I really didn’t have much experience in testing. And I was given\u00a0<\/span>QTP \u2013\u00a0<\/span>an old version of\u00a0<\/span>QTP. The\u00a0<\/span>record inside of that\u00a0<\/span>worked gre<\/span>at<\/span>. And it\u00a0<\/span>added<\/span>\u00a0some benefits. I really didn’t understand the principles back then. I guess\u00a0<\/span>it\u2019s<\/span>\u00a0how you should be\u00a0<\/span>looking to build out a test framework to act as an augmented resource<\/span>\u00a0for your\u00a0<\/span>activities.\u00a0<\/span>So<\/span>\u00a0I went through a number of journeys I think with\u00a0<\/span>test tools \u2013 trying<\/span>\u00a0different tools, trying different approaches. The first really successful framework we manufacture<\/span>d<\/span>\u00a0<\/span>here\u00a0<\/span>was<\/span>\u00a0put together was on an old scripting language called\u00a0<\/span>Ruby<\/span>, a test\u00a0<\/span>framework called<\/span>\u00a0Walter<\/span>,<\/span>\u00a0web application tested\u00a0<\/span>in Ruby,<\/span>\u00a0really simple language to code\u00a0<\/span>with a\u00a0<\/span>test framework. We built a framework that worked very much in a kind of way, you could call it, from a simple web browser.<\/span>\u00a0<\/span>And that were all open<\/span>–<\/span>source. And I think this is one of the challenges I find with companies. A lot of the t<\/span>he t<\/span>ime<\/span>,<\/span>\u00a0<\/span>people\u00a0<\/span>want\u00a0<\/span>automation,<\/span>\u00a0but<\/span>\u00a0they<\/span>\u00a0don’t want to spend a lot of money on tool\u00a0<\/span>for<\/span>\u00a0automation upfro<\/span>nt<\/span>. They want to know that it can work<\/span>. To\u00a0<\/span>anybody out there who’s looking to implement automation<\/span>,<\/span>\u00a0I strongly recommend you pull up proof of concept\u00a0<\/span>together<\/span>\u00a0first and prove its worth before trying to get b<\/span>uy-<\/span>in for funding.<\/span>\u00a0<\/span>It just makes life so much easier<\/span>.<\/span>\u00a0<\/span>That is\u00a0<\/span>one of the biggest challenge I had to be getting for\u00a0<\/span>it<\/span>\u00a0to implement. But when\u00a0<\/span>we<\/span>\u00a0got the idea, then implement a framework. And like I sa<\/span>id<\/span>, the first\u00a0<\/span>Ruby<\/span>\u00a0framework actually worked fantastically and was a great tool until Firefox started doing weekly updates to\u00a0<\/span>their<\/span>\u00a0code. So once Firefox\u00a0<\/span>started<\/span>\u00a0doing agile delivery and start rolling out new versions of Firefox every couple of days, the plugins were needed to enable the framework to work\u00a0<\/span>and we\u00a0<\/span>weren’t being\u00a0<\/span>there<\/span>\u00a0quick enough.<\/span>\u00a0<\/span>We quickly fell behind in terms of compatibility and had to have to take a step back. So<\/span>,<\/span>\u00a0we took a look at the industry again and a lot of people seem to be using\u00a0<\/span>Selenium<\/span>. And so<\/span>,<\/span>\u00a0we implemented the selenium framework<\/span>\u00a0\u2013\u00a0<\/span>again a very basic one at first. But then gradually you learn from your mistakes.\u00a0<\/span>You<\/span>\u00a0learn from trying to over<\/span>c<\/span>omplicate\u00a0<\/span>an<\/span>\u00a0automation framework and you learn what was actually important to the framework and gradually get to this point through those exercises where you understand what the key things are<\/span>\u00a0that<\/span>\u00a0you need to put in place and the tool becomes agnostic<\/span>, if\u00a0<\/span>I’m honest<\/span>. At\u00a0<\/span>this point, once you understand what is\u00a0<\/span>it that you\u2019re<\/span>\u00a0trying to achieve with the automation tool, it really doesn’t matter which\u00a0<\/span>tool<\/span>\u00a0you use. That said, there’s a lot of new\u00a0<\/span>tools<\/span>\u00a0on the market which\u00a0<\/span>are<\/span>\u00a0introducing a whole new dimension to automation for me that I’d love to start exploring, but that’s probably a story for another time.<\/span>\u00a0<\/span><\/p>\n

Logan:<\/span><\/b>\u00a0I love it,<\/span>\u00a0<\/span><\/b>Mark<\/span>.<\/span>\u00a0<\/span>Some\u00a0<\/span>really good context there.\u00a0<\/span>Nanda,<\/span>\u00a0I’d love to hear your thoughts here on picking the right test automation tool and also where you’ve seen customers leverage<\/span>\u00a0Cigniti\u2019s<\/span>\u00a0test automation framework<\/a>. You know, Mark spoke to the importance of developing your framework there. So<\/span>,<\/span>\u00a0another kind of two<\/span>–<\/span>part question coming back at you<\/span>, Nanda.<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Sure,<\/span>\u00a0Logan<\/span>. A<\/span>nd just going back to what Mark said<\/span>, I<\/span>\u00a0<\/span>100%<\/span>\u00a0support<\/span>\u00a0that\u00a0<\/span>whole thought process of laying the right emphasis on the right\u00a0<\/span>test automation<\/span>\u00a0tool is half the battle won.<\/span>\u00a0<\/span>So\u00a0<\/span>Cigniti<\/span>\u00a0has an automation center of excellence which comprises of automation architects that build and maintain best\u00a0<\/span>automation frameworks to cater to\u00a0<\/span>various<\/span>\u00a0underlying platforms, applications<\/span>,<\/span>\u00a0and technologies<\/span>. Cigniti also\u00a0<\/span>has partnership with all the leading\u00a0<\/span>tool\u00a0<\/span>vendors, which\u00a0<\/span>entitles<\/span>\u00a0us to have a preview of the upcoming version of the test tools. With the skill and capability backed by the tool partnership and deep technical expertise, Cigniti offers tool feasibility study as one of its offerings. So, we go to a technology landscape and understand the technology lay of the land, the future technology roadmap, the current and future application roadmaps as well. And put in a mix of open-source and commercial tools to then build and run a few automation scripts and compare them objectively.\u00a0<\/span>So<\/span>\u00a0we have an objective rating criteria across 30 parameters and then aggregate that and do a total score which will help the customer make the right choice. There are several parameters, not just technical, commercial, but ease of use and maintainability, scalability, robustness, and future proofness. So, all of these together give you an objective score that has significantly helped the customer make the right choice. And once they make the right choice, Cigniti, having served hundreds of customers, has the right frameworks independent of the underlying technology landscape to be able to aggregate all the classes, frameworks, and reusable tools to be able to bring to bear the jumpstart kit, which usually saves about 20 to 30 percent of the effort for all new customers whoare embarking on this automation journey. Logan?<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>If I\u00a0<\/span>may..<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Go ahead, Mark.<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>To add to that, I think companies like Cigniti, you\u2019re starting from nothing with automation, you just begin to\u00a0<\/span>ream into\u00a0<\/span>implement<\/span>ing<\/span>\u00a0automation. Then for a lot of cases, I think partnering with a company like Cigniti, that’s actually a godsend because they bring all that learning wisdom<\/span>, they bring<\/span>\u00a0experience with multiple applications and all the challenges that you will face if you try\u00a0<\/span>and<\/span>\u00a0develop your own frameworks have already been covered<\/span>. And\u00a0<\/span>all the other challenges that find people how with automation<\/span>,<\/span>\u00a0<\/span>if<\/span>\u00a0trying to automate too much too soon.<\/span>\u00a0<\/span>If you just automate every test that you do<\/span>, what\u00a0<\/span>you actually create\u00a0<\/span>is\u00a0<\/span>a massive maintenance task<\/span>,\u00a0<\/span>not helpful<\/span>\u00a0automation\u00a0<\/span>framework. And I think companies like\u00a0<\/span>Cigniti<\/span>\u00a0bring a wealth of experience that really helped\u00a0<\/span>you start<\/span>\u00a0that journey. And you know,\u00a0<\/span>like Nanda said it gets you<\/span>\u00a0the way through right from the start of understanding what you need. I think that insight can be absolutely invaluable if you come into this blind.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>I love that context, Mar<\/span>k<\/span>. You know, talking about speed\u00a0<\/span>and<\/span>\u00a0the benefit there from earlier in the conversation, like you said, getting kind of a 30 percent jumpstart can be so invaluable. You know, I think both of you gentlemen have alluded to this a little bit, but I’d like to round out the conversation a little bit here with with you, Mar<\/span>k<\/span>\u00a0to share some best practices on how to get the right mix of automation and manual testing.<\/span>\u00a0<\/span>We’ve spent a good bit of time talking about the value and the\u00a0<\/span>applications of automation in testing. But I imagine that doesn’t lead you to believe that automation should just be applied blindly everywhere<\/span>, ri<\/span>ght?\u00a0<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>You know, I’m currently in the process of potentially chang<\/span>i<\/span>n<\/span>g<\/span>\u00a0my opinion<\/span>\u00a0<\/span>on this. I’ve always been a strong advocate that<\/span>\u00a0<\/span>you require both a manual\u00a0<\/span>test<\/span>\u00a0phase and automation test phase<\/span>. B<\/span>ut\u00a0<\/span>for purely<\/span>\u00a0pragmatic reasons<\/span>, u<\/span>p until very recently, automation tests have only been able to deliver simple functions that\u00a0<\/span>are\u00a0<\/span>repeatable tasks. But with the advent of machine learning and AI, we’re getting to a point now where automation frameworks can, in theory,\u00a0<\/span>make<\/span>\u00a0decisions about what the right route to take in\u00a0<\/span>effect<\/span>, what the right\u00a0<\/span>data<\/span>\u00a0to use. And, you know, these are things that up until now, automation hasn’t been able to do.<\/span>\u00a0<\/span>It hasn’t been\u00a0<\/span>able to make those<\/span>\u00a0intelligent decisions about for this particular kind of test. With this feedback I’m getting from the application, I now need to make it simple, whereas AI and\u00a0<\/span>ML<\/span>\u00a0give you a whole new world of possibilities that will only improve as you implement it<\/span>\u00a0and as it<\/span>\u00a0grows<\/span>. Right\u00a0<\/span>now<\/span>,<\/span>\u00a0<\/span>personally<\/span>, I think we’re not quite there yet. So<\/span>,<\/span>\u00a0I would always argue that you will not get to 100 percent automation test coverage and companies have said that they have.<\/span>\u00a0<\/span>In my experience, when you really break it down, what they mean is they’ve got to 100 percent coverage of\u00a0<\/span>automatable<\/span>\u00a0all tasks. I\u00a0<\/span>think<\/span>\u00a0that’s the real question here is not how much can you ultimate, but how much of your application is\u00a0<\/span>automatable,<\/span>\u00a0how much of it is complex and require<\/span>s<\/span>\u00a0too many inputs and that\u00a0<\/span>is<\/span>\u00a0challeng<\/span>ing.<\/span>\u00a0I think I and I know a really going to blow the doors wide open on that. And we may actually get to a point now where you can 100 percent automate things.<\/span>\u00a0<\/span>I imagine\u00a0<\/span>it\u2019ll<\/span>\u00a0be a good 10 years before that mainstream fall for every other company out\u00a0<\/span>there. It\u00a0<\/span>will be led by Googles and\u00a0<\/span>Amazons<\/span>\u00a0and people of that nature. But I have genuinely changed my opinion in the last couple of years due to things I’ve seen and worked with<\/span>.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>Well Mark, that’s\u00a0<\/span>a really good\u00a0<\/span>context<\/span>. I appreciate the insights into how you’re thinking about this now and also, you know, seeing the trends. And I you know, I just\u00a0<\/span>jot it<\/span>\u00a0down is as you were talking that question that I think listeners should be thinking of as you change the context of how much have we automated and what is\u00a0<\/span>automable<\/span>\u00a0and what’s potentially going to be\u00a0<\/span>automable<\/span>\u00a0in the next few years and kind of just making that subtle shift in where you look at applying your test\u00a0<\/span>automation<\/span>.<\/span>\u00a0<\/span>N<\/span>anda<\/span>, I’ll kick it back over to you as we round out the conversation. When give you a chance to to chime in on Mark’s context that he just shared there.\u00a0<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Sure.<\/span>\u00a0<\/span>Thanks, Logan. I’ll go back to one of the earlier comments that Mark made, and rightfully so. When he touched upon mercury toolsets<\/span>,\u00a0<\/span>I got nostalgic<\/span>. I<\/span>\u00a0believe about 16 to 20 years ago when I personally made my hands dirty<\/span>\u00a0with WinRunner<\/span>\u00a0at that time, which then went on to become the\u00a0<\/span>QTPs\u00a0<\/span>of the world and the\u00a0<\/span>UFTs\u00a0<\/span>of the world, an<\/span>d<\/span>\u00a0<\/span>now the LeanFTs<\/span>. So<\/span>,<\/span>\u00a0tools change, technology changes that\u00a0<\/span>I think we’ve improved.<\/span>\u00a0<\/span>There are two main outcomes old concepts. A one a lot of people believe that life is too short to focus on your weaknesses. Focus on your strengths and lean on the experts to blunt the weaknesses. So that’s fair. I think\u00a0<\/span>Cigniti<\/span>\u00a0comes into play. Why reinvent the whole\u00a0<\/span>wheel<\/span>\u00a0in terms of automation when we have learn<\/span>t<\/span>\u00a0the hard way and we can bring in the best of practices<\/span>?\u00a0<\/span>Again<\/span>\u00a0supported by Mark’s views on this subject. From there,\u00a0<\/span>we at Cigniti over<\/span>\u00a0the last five years have significantly seen the\u00a0<\/span>re<\/span>source\u00a0<\/span>profile<\/span>\u00a0within\u00a0<\/span>Cigniti<\/span>\u00a0to move from a traditional testing mindset to now\u00a0<\/span>a\u00a0<\/span>completely<\/span>\u00a0SDET<\/span>\u00a0mindset. So<\/span>,<\/span>\u00a0everybody comes with an automation<\/span>–<\/span>first approach.\u00a0<\/span>So, about five\u00a0<\/span>years ago, everybody was talking about mobile first approach in everything that they do in the development<\/span>. Now, if\u00a0<\/span>a company is still not embarked on the automation journey and is not talking about the automation<\/span>–<\/span>first approach, I think we are left far behind on the\u00a0<\/span>curve<\/span>\u00a0with the Googles of the world, with the\u00a0<\/span>Netflixs<\/span>\u00a0of the world, Amazons of the world, Facebooks of the world<\/span>. They are\u00a0<\/span>benchmarking to what level\u00a0<\/span>test automation<\/span>\u00a0can be taken and leveraged upon.<\/span>\u00a0<\/span>And while not everybody has to be\u00a0<\/span>there at<\/span>\u00a0that mark. But they just proved that the technology is out there for you to leverage and harness your potential for the best things that you could do outside, which are manual\u00a0<\/span>repetitive<\/span>\u00a0tasks<\/span>, right<\/span>.\u00a0<\/span>So<\/span>\u00a0I fully agree with Mark’s views. The trend is slowly getting to a position where you leverage\u00a0<\/span>AI, ML\u00a0<\/span>to do things that you previously thought would never be possible through\u00a0<\/span>test\u00a0<\/span>automation. The tools are out there. The technology is out there<\/span>,<\/span>\u00a0and\u00a0<\/span>they are<\/span>\u00a0maturing by an order of magnitude as we speak.<\/span>\u00a0The pace at which the\u00a0<\/span>technology<\/span>\u00a0is<\/span>\u00a0changing is opening up\u00a0<\/span>a plethora of\u00a0<\/span>opportunities for everybody in the testing community to become smarter, to\u00a0<\/span>add<\/span>\u00a0disproportionate and\u00a0<\/span>geometric-<\/span>proportionate value to our customers<\/span>\u00a0<\/span>as<\/span>, again leaning back to the thought that Mark said,<\/span>\u00a0release\u00a0<\/span>velocity,<\/span>\u00a0time<\/span>–<\/span>to<\/span>–<\/span>market\u00a0<\/span>are<\/span>\u00a0<\/span>so critical<\/span>\u00a0today and the technology as well supports that.\u00a0<\/span>So<\/span>\u00a0if you go wrong, you fail\u00a0<\/span>fast, you roll\u00a0<\/span>back and you keep moving<\/span>,<\/span>\u00a0<\/span>right<\/span>. So<\/span>,<\/span>\u00a0with that mindset coming from a field\u00a0<\/span>of pure\u00a0<\/span>testing\u00a0<\/span>fraternity<\/span>,\u00a0<\/span>for us, quality is paramount.\u00a0<\/span>But at the same time, we have to meet the demands of\u00a0<\/span>the time to market that are out there.<\/span>\u00a0<\/span>So<\/span>\u00a0balancing\u00a0<\/span>these two,<\/span>\u00a0<\/span>leveraging on test automation<\/span>\u00a0and harnessing it to the fullest potential is the only way out for all the enterprises\u00a0<\/span>out there.<\/span>\u00a0<\/span><\/p>\n

Logan:<\/span><\/b>\u00a0Nanda,\u00a0<\/span>thank you so much for that. It was really great context and I love the parallel that you drew there<\/span>\u00a0\u2013 the\u00a0<\/span>connection between the shift that we all needed to make to mobile first in development and seeing a similar shift to automation first in testing. I think those are wise words and I can just tell the passion that both of you have in sharing with the community on the trends, the challenges<\/span>,<\/span>\u00a0and the opportunities that everyone listening to this is really facing.<\/span>\u00a0<\/span>So<\/span>\u00a0I want to give you guys just a quick opportunity to let listeners know how they could reach out or stay connected with both of you, providing, you know, so much wisdom and context from your experience today on the podcast. If\u00a0<\/span>they have follow<\/span>-up<\/span>\u00a0questions or anything like that and would like to reach out<\/span>.\u00a0<\/span>Mark, I’ll start with you. What would be the best way to reach out or stay connected with you, sir?\u00a0<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>Yeah, I think LinkedIn is probably the best way to stay connected with me.<\/span>\u00a0<\/span>I checked that quite regularly.\u00a0<\/span>I keep<\/span>\u00a0in touch with a lot of the testing groups on their networking sites. You can reach me on Twitter<\/span>. That\u2019s<\/span>\u00a0probably about<\/span>\u00a0it on<\/span>\u00a0social media<\/span>\u00a0for me<\/span>. I’m afraid I’m a bit of a dinosaur.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>You<\/span>\u00a0<\/span><\/b>make\u00a0<\/span>it nice and easy for folks. That’s A-okay with us<\/span>,\u00a0<\/span>Mark<\/span>. Nanda, h<\/span>ow about you<\/span>?<\/span>\u00a0<\/span>LinkedIn<\/span>\u00a0the best spot to go for folks, too, that want to follow up and reach out to you<\/span>?<\/span>\u00a0<\/span><\/p>\n

Nanda:<\/span><\/b>\u00a0Yes<\/span>,\u00a0<\/span>Logan<\/span>.\u00a0<\/span>Lin<\/span>ke<\/span>d<\/span>I<\/span>n is the best and most preferred option. Well, I’m also reachable on my e<\/span>mail ID\u00a0<\/span>nanda@cigniti.com<\/span><\/a>.\u00a0<\/span>And on the lighter note, just\u00a0<\/span>to finish off<\/span>. By<\/span>\u00a0touching the<\/span>\u00a0topic of mercury toolsets,<\/span>\u00a0I think\u00a0<\/span>both\u00a0<\/span>Mark and I,\u00a0<\/span>inadvertently gave away our<\/span>\u00a0age<\/span>, how old we are within this community.<\/span>\u00a0<\/span>So\u00a0<\/span>be it. We\u00a0<\/span>are passionate<\/span>\u00a0people within\u00a0<\/span>testing.\u00a0<\/span>It’s a small world out there. We love what we are doing<\/span>,<\/span>\u00a0and we love to share what we’ve learned. We also learn a\u00a0<\/span>love<\/span>\u00a0to learn from others as well. So<\/span>,<\/span>\u00a0keep the community feeling going, going on. I think it will benefit the larger audience.<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>Yeah, yeah. I think what we’ve also done that nowadays we prove that you don’t have to be young to take advantage of the new technologies and methodologies until\u00a0<\/span>you are<\/span>\u00a0passionate about the change in our industry.\u00a0<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Absolutely, Mar<\/span>k.<\/span>\u00a0<\/span><\/p>\n

Logan:\u00a0<\/span><\/b>I love the passion that you guys are bring in and<\/span>.<\/span>\u00a0<\/span>You\u00a0<\/span>know, whether you’d inadvertently, you know, shared your ages or not. I think that what listeners can can say is what I mentioned earlier is that there is a lot of collective wisdom, even just right here and as we’ve mentioned on the\u00a0<\/span>Cigniti<\/span>\u00a0team and the teams that you guys represent. So<\/span>,<\/span>\u00a0I hope that listeners will take next steps, reach out to\u00a0<\/span>you\u00a0<\/span>guys. This has been a great conversation, I think, looking at some of the challenges and some of the opportunities in the years to come.<\/span>\u00a0<\/span>Gentlemen, thank you so much for joining me on the podcast today.<\/span>\u00a0<\/span><\/p>\n

Mark:\u00a0<\/span><\/b>Thank you very much for the opportunity Log<\/span>a<\/span>n\u00a0<\/span>and Nanda. It\u2019s been a pleasure<\/span>\u00a0<\/span><\/p>\n

Nanda:\u00a0<\/span><\/b>Thanks, Logan.<\/span>\u00a0Thank you for having me.<\/span>\u00a0<\/span><\/p>\n

Quality assurance is vital to the success of an organization\u2019s digital transformation. Lack of control can quickly derail a company\u2019s technological presence, costing thousands. At Cigniti, our resolution is to build a better world with better quality software. Renowned for the global quality thought leadership in the industry, we draw expertise from over a decade of test engineering experience across verticals. To learn how we do it, visit cigniti.com.\u00a0<\/span><\/i>\u00a0<\/span><\/p>\n

You have been listening to QA talks. To ensure that you never miss ay episode, subscribe to the show in your favorite podcast player. Thank you so much for listening, until next time.<\/span><\/i>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Speakers:
\u00a0Mark Bland<\/strong>, Sr. Global Test Manager at Premier Farnell;\u00a0
Nanda Padmaraju<\/strong>, Senior Vice President at Cigniti (A Coforge Company)
\n