Eric Coleman: Hello everyone and welcome. My name is Eric Coleman with IIST and I will be the moderator for today’s webinar, Accelerate Digital Transformation with Mobile Test Automation. We’re excited you’re able to join us today and set aside an hour to attend this webinar. This webinar is hosted by IIST, the leaders in education-based certifications and training. For more information on how IIST can help you or your organization, please visit Testinginstitute.com. This webinar is sponsored by Apexon, a digital-first professional services firm. The company helps enterprises get digital rights the first time by combining ready-made tools, framework, technologies, and partnerships with their in-depth experience.
We will have time for a short Q&A at the end of today’s session. You may submit your questions at any time by using your question box in you GoToWebinar window. Please identify the instructor whom the questions are to be addressed to. Today’s presenters will answer as many questions within the time allowed at the end of today’s session. If you have any technical problems or issues during the webinar, please email online admin at iist.org and someone will be with you and help you right away. This webinar is being recorded and will be made available for viewing within 48 hours at Testinginstitute.com. At the end of today’s webinar, you’ll be asked to complete a short survey. At IIST, we strive to provide the highest quality educational resources for the public and would appreciate it if you could take a few minutes to complete this short survey.
Today’s webinar, we’ll have three presenters, Amir Rozenberg. Amir is the Director of Product Management responsible for core product strategy at Perfecto, the leading digital cloud and test automation company. Gail Gallegos is the Director of DexYP, responsible for application delivery, and digital and enterprise application. Gail has been a Driver at DexYP in moving automation and DevOps processes forward to allow the company to move quickly with quality throughout the software development lifecycle. Kedar Apte. Kedar is the QA Manager at Apexon. He has over 18 years’ experience in engineering digital and enterprise applications, specifically in test automation and mobile testing.
We’ll go over today’s agenda. The first section of the webinar, Amir from Perfecto will discuss the landscape of mobile testing in the digital age. Next, Gail from DexYP will share about their digital transformation journey, the challenges they faced, and the role of mobile. Lastly, we’ll hear from Kedar, from Apexon, who will reveal steps to success and the pitfalls to avoid in mobile test automation. I will now turn the webinar over to today’s first presenter, Amir. Amir?
Amir Rozenberg: Good morning, everybody. Good morning. Good Afternoon. Good evening to everybody on the line. I’m very excited to be here with you talking about digital transformation and the opportunities and challenges that it brings with it, as well as how to address those from a quality perspective, what are the tools, processes and how do you organize the team to be ready for those challenges. I’m very excited to be joined today by Apexon and DexYP. This holistic story, I think, brings together three parties who are all tuned into the success of DexYP and overall success in the marketplace, so, very, very exciting story today. Definitely looking forward to the discussion and the Q&A that will come afterward.
I wanted to take a step back and describe what’s happening before our eyes in this landscape of delivering services and content over the web interfaces, the digital interfaces. We see more and more bank services, healthcare services, retail and so forth virtualizing onto digital delivery channels. Those could be on multiple different screens and multiple different touchpoints at different times of the day according to the user preference of the screen and time and their mode of operation and so forth. It really does bring forward the best of the interaction with the brand, between the user and the brand to achieve their goal in a streamline engaging and even fun way that really enriches our day-to-day life whether we’re trying to achieve a chore or we’re trying to go through an enjoyable experience.
What we’re seeing across all of these organizations is that digital transformation should be the leading strategy of all organizations because what we see in the brick-and-mortar businesses, if they are being bypassed by those who are successful and know how to execute in digital strategy. In each of those verticals, whether you look at retail, healthcare insurance, search, banking, financial services, those who are fluent and executing well in digital platforms are those who are gaining more market share with the users and are taking over the market. Unfortunately, the reality of it is we’re seeing the brick-and-mortar businesses actually shutting down, taking down staff, taking down branches and so forth. Whether you’re looking at check deposits, exciting new biometrics, conversational virtual assistants in the terms of chatbots and so forth.
All of these things really come together to create a cohesive streamlined experience that is really engaging. What we see is really innovation across the different platforms really helps every single brand and every single brand engages with these different technologies in order to accelerate their digital innovation. We’re suddenly seeing in front of our eyes a really accelerated evolution of conversational interfaces. It could be through your application. For example, recently, Bank of America launched the Erica virtual assistant inside the app, where you can ask for ‘what is my account balance’, or transfer money, or things of that nature. That also expands to Alexa, and Google Home, and even converting over the big screen at your home through Fire TV, and Alexa, and the likes. Really streamlining instead of text-entry, streamlining the experience.
In the same token of trying to streamline experiences and elevate security inside the engagement is the entire set of new authentication methods, such as face ID, touch ID, and so forth. Where you can imagine in-app transaction, such as an award game or building a castle, prior to this, trying to enter credentials would not have been an acceptable transaction, but just putting you or someone, it really streamlines and enables the user. And then, of course, on both sensors in terms of check scanning, in terms of healthcare location and so forth. Lastly, of course, augmented reality that is now really expanding in the marketplace.
What does that mean to the team lead? The team lead, they are being pushed to increase the coverage of the scope of the application, while at the same time, they push to bring the application much faster to market. What that really means is the quality– even though the expectation for many users really goes higher, the quality usually suffers, and it stays out. From the team lead perspective, when they come into the launch of the sprints, in reality, what they find is that all of the capacity that they are planning towards innovation, all of the capacity actually ends up in bug fixes, technical death, fixing the latent feedback from users in production and so forth.
Your innovation goes down, you don’t have time to innovate and provide quality. It takes the longest time and you need sometimes to delay the launch or you actually need to falsely launch the product with no risk, no defects, and also your cost goes up. While the organization is placing a significant investment into innovation and velocity, the quality isn’t there and you end up late to market with a lot of risk. That’s not a good composition, it’s not a good position for the team lead.
What we’re trying to show here in this webinar is that there are ways to embed efficiently quality activities into the sprint such that the developers you have will be happier, you would be more efficient, and your users would get a much better product. You can see here, for example, it’s an interesting chart. It shows when do defects get introduced, when are they found, and its staggering stats around the cost of finding defects in production. Because finding defects in production means that the developer needs to stop, they need to do the root cause analysis, they need to undo code and then redo the code. Very, very expensive exercise.
We want to change the game dramatically. We want to really transform the game. And one of the things to control the game is think about quality in DevOps. Quality in DevOps, like many other things in DevOps, consists of process, people, and technology change. The main mantra is that everything needs to work all the time. For example, all teams, all squads are working at the same rhythm. You can take real-time decisions and correct defects. Developers do participate in the quality process. There’s a focus on coding, so everything has to be stable. Green is green. Three strikes for a tested field means that that test isn’t being executed again in smart retry. From people’s perspective, we need to elevate the skills of the manual testers so that they can participate in the sprint itself and so forth. I’ll come back to people a bit later.
Lastly, from a technology perspective, you need a reliable lab, reliable, it’s scalable, it’s stable, and you can really rely on. You need this framework that will enable your staff to create scalable, reliable automation, and you need a solution for big data reporting because once you have a lot of executions, a lot of coverage, finding that needle from the haystack, if you don’t have a big data reporting, is a very difficult task.
What are the components of a solution that would allow you to embed quality activities endeavors? The first one is maximized the test coverage. Think about the basic scenario, but also think about all the scenarios, all the platforms and all the scenarios that would expand. So the different platforms and the different mobile platforms and sensors, same-day support for new platforms, such as iPhone X and so forth. Then also providing coverage for realistic, real user scenarios, not just testing in a lab. Similarly, a high degree of test automation. What’s happening manually at the end of the sprint would lead to late defect finding. If you can automate all kinds of scenarios, such as check scanning, location, different networks and so on and so forth, rotation and so on and so forth, then you can really achieve in-sprint quality in non-human manner.
Fast feedback. The ability to provide the developers inside about a defect that was found minutes after you did the commit. From a developer’s perspective, if you tell me that two minutes after commit that I can now introduce the bug, I won’t even bother entering that bug into JIRA, I’ll go straight ahead and add it. What you’ll find is that the steps ran, and indeed I can provide that developer feedback about a defect two minutes after I coded, the satisfaction and efficiency of developers rises tremendously. Lastly, the same tool integrated across the process, across the SPLC. There’s no over-the-wall attitude, all the teams are using the same tool across the lifecycle of the features or your Jenkins job, and this way, we can really get visibility across teams, as well as executives into the health of the application all over the building cycle
If we now tie this to the concept of the lab, you can see at the bottom, a lab consists of all the devices and the platforms that you would need, and the ability to automate all the scenarios that you need, whether it’s different browsers or IoT devices or mobile devices or desktops, whether it’s different network and different location, and so on and so forth. The ability to connect a new iPhone almost immediately, that’s the lab.
Then when we talk about elevating the skills of people, we talk about frameworks that support BDD, English-like scripting, such that testers can come to the sprint initiation, they can understand the committed requirement, and indeed, from the get-go of the sprint, they can already write test cases. At that point when the developer develops some functionality, they can already start testing, the test is ready for them. Clearly, a strong, big data digital reporting solution and largely their DevOps reach that open API connector to Jenkins, to your reporting solution, to various different problems and connectors throughout your CI, such that when you do a commit, automatically, Jenkins builds a software, deploys the IPA, APK, and server technology runs a couple of tests, and automatically, within two minutes, again, you’ve got results for test cases that show you the defect that just happened.
This is really solution that emphasizes both the lab, the people, and the process. The unique thing that we in Perfecto pride ourselves in is, yes, you can do this yourself using open-source. There are multiple different solutions in the marketplace, but there is one solution that really brings it all together, such that you as a team lead can stop worrying about managing the lab, and managing frameworks, and managing reporting, and managing all these things. The quality in DevOps solution is in your hands through Perfecto. It’s one solution that gives you all the tooling that you need. Throughout this, you’ll see inside the screen. This is what we call quality DevOps. With that, I hope that makes sense. Looking forward to the questions later. I am going to hand it over to Gail. Gail?
Gail Gallegos: Yes. Thank you, Amir, I appreciate that. As Amir told you about Perfecto, I am going to take you through the journey of a transition that DexYP traveled through when we had to move from our printed directory into the digital space. At DexYP, we believe in the American Dream. Our mission is to help America’s local independent business owners thrive, as we have for decades. Because they represent the backbone of America’s economy and the heart of its community. In the past, we’ve had directories which some of you probably don’t even know what those are. In today’s world, where you would look up a person or a business, you would look those up on your phone or your desktop. In the past, our company produced what we call the yellow pages and directories for the telephone companies where people would look up those listings and find those businesses.
We believe in free enterprise, a diverse dynamic economy and the American Dream of owning an independent local business. Local businesses like the plumbers, the local restaurants, the landscapers, the florists, they don’t have the big marketing companies that manage their advertising for them. Our company strives to make sure that we get them out in the open and let people find them very easily. We believe consumers should have choices other than the chains and the global e-commerce. I know a lot of times when folks go on vacations, they like to go eat at the local restaurant. In order to find them, we have to make sure our clients get out there in the sights and the spaces, on the mobile devices and on the desktops so that people can find those locations and they can go visit those locations and use those local consumers.
We believe devotion to supporting independent business owners is a worthy, noble calling. With the independent businesses, the small businesses, a lot of folks talk about those, that’s the American Dream, to be able to be your own boss and handle your own destiny. I talked about how we got to the digital space. In today’s mobile on-demand economy, consumers expect instant communication service. The local independent business owners must use the tool their customers use or risk losing business to the national chains. Venture back startups and sophisticated regional players.
In the past, you were able to if you needed to find a plumber, you went to the phone book, you looked underneath the category of a plumber. Your phone book was local to your area, so you would go to the listing and depending on the size of the ad or where that person fell on the page, that would be the person that you called. In today’s world, our clients, our advertisers for the small businesses, we want to make sure that people are going to find them, so we have to get to that next level and start to utilize more of the mobile devices and the desktops. In doing so, we had to find new technology and ways to keep our consumers out there and make sure that people can find them. A lot of folks, like I said, don’t use the phone book anymore so hence the transition for DexYP to move away from that technology and into the mobile space and allow folks to find our clients through the mobile space.
Some of the digital customer offerings that we have for our clients is online listings. Those are allowing our clients to get out on the browsers and the mobile devices so that if
somebody is looking to get their air conditioning fixed, that they can go out to their browser and they can find air conditioning vendors that are located in the Dallas, Texas area.
That will allow them to find these businesses that advertise with our company. Another way that we help through the digital customer offerings for our clients is Thryv. Thryv manages the advertising. Unlike the big companies, the chili restaurants, and the Sears and Roebuck and some of those other companies, we manage those advertising for the small businesses. So, we’re their marketing department.
We make sure that they get out to the sites they need to, that they have a website that folks can get to, that their website is easy to understand and get through. That they’re found in all of the different types of places like Google and Yahoo and that they’re visible to people when they are needed. We also do a lot of display and social, easily drive traffic to our business’s website. Some other places would be some Facebook advertising. We allow our customers to get out to Facebook. So if folks are out on Facebook, you see some trigger ads. Sometimes if you look something up, all of a sudden, you go to Facebook and all of a sudden, you’re given an ad for a customer that shows something that you were looking up on in Google.
We try and make sure that for our clients that they’re able to be seen in the social area. Then also search engine marketing. Show up in more places where more people search. Like I said before, when you’re out there in Google and you’re doing your searches, if Google doesn’t have that information, that it will send it to the places that do. We have three online IYT sites St.com, Yp.com and Dex Knows, and those are areas that you can find a local business by just searching on the category of a florist or a plumber and the area that you’re in and it will bring up all of the listings and advertising for our clients that advertised either on our site, or on a Google site, or on a Facebook site. Any one of those and it will show that to the clients so that they can find the right place that they want to do business with.
There’s many means of social media, ensuring when you launch new products to test for advertising validation. One of the chores that we had in this transition was making sure that our clients, when they advertise with us, consumers that would bring them up on a mobile device versus a desktop, that the website would come up cleanly and visible and be easy to use or their ad that they may be showing on Google, whether they’re bringing it up on their mobile device or an iPad, that it was going to show up correctly and be visible to the consumer that’s looking for that business.
In this ever-changing, automation was very, very important. We changed devices, we changed operating systems, so we knew at that point, it was very, very important to make sure that we had the technology available to us, that we can do that validation quickly and make sure that it was going to be correct when we launch to production. Some of the challenges that we faced when we got into this space and that has gotten a lot easier for us but it’s still ever-changing is, and I know Amir mentioned this a little while ago, about moving quickly with quality.
In today’s world, we can’t just sit back and wait six months to release a new product or to release some changes to some of our sites. We want to make sure that we can release quickly but also to make sure that when we do release that it’s got quality. We wouldn’t want to release a new version of our IYP site and then all of a sudden, a customer’s ad is not showing up correctly. They are paying us for this advertising, so we need to make sure that we’re doing the best job that we can for them.
Multiple devices and browsers was another challenge. Initially, when we got into the mobile space, we were trying to do a lot of the testing internally and we thought, “Okay, we can just buy some devices and have different operating systems for them, and we can also have different PCs that had the different browsers and different browser versions on them and do it manually.” It was very time-consuming, it took forever, it was not utilizing our resources efficiently. Of course, with the ever-changing software updates, we all know whenever you have to upgrade a device or a new operating system, it’s time-consuming to get all those devices upgraded, you also have to go ahead and sign new contracts with the service provider in order to upgrade your devices.
This was very costly to us, and being a company transitioning from one form of technology into another, you want to manage your expenses and make sure that you can handle the expenses that you’re incurring with keeping up with the technology that was going on. So these are some of the areas that we had to be aggressive, we had to stay up with the competition and frequently, the new contracts with the service providers, and this is when we stepped in to finding new automation tool and trying to help get through all of this quickly and have the tools available that we can test multiple browsers and we can test multiple devices, of course managing those expenses at that time.
These are some of the challenges that occurred to us, and with rolling over to utilizing some of the automation tools in Perfecto, we were able to handle those expenses and those challenges and continue to give our clients what they needed as we moved into the digital workspace. Now, I’m going to turn it over to Kedar and he’s going to talk about Apexon and their role in the automation.
Kedar Apte: Hey, thanks Gail. Hi, everyone. This is Kedar Apte, I’m QA Manager at Apexon. Just now, we heard the challenges Gail has mentioned, what we are doing? We heard all her challenges and we went back to the table on the drawing board and we started understanding what the challenge is, what is the strategy we have to come up, and how we can help our client. While doing that, first of all, we come up with five points. Number one point was, identifying the right framework, then selecting the right tool for the execution. Third is what is our strategy, how we can help a client, how we can meet the demand of the client. Fourth is constructing the right team, and the fifth is the execution.
The first point was the framework, after hearing all the challenges, we said, “Okay, what framework we have to consider which will help us long term?” We started with considering our own framework which is QMetry Automation Framework, we also tried to compare it with other framework like normal testing engineering and we said, “Okay, we want a framework which can–” We know we didn’t expect to debate seamlessly with all the open-source tools and be integrated with test management platforms and the mobile devices.
Our framework, as you can see, it can be integrated to work with Selenium, with Appium. On the test management tool, it can be integrated with HP ALM, currently, we’re integrating it with Rally, it also can be integrated with QMetry out of the box. When it comes to the continuous integration, it can be integrated well with Hudson, Jenkins, Bamboo, and so on and so forth. Now, coming up to the tool, we compare various mobile device cloud solutions like Perfecto and Sauce Labs. We have various points which will give us the outcome, “Okay, what is the right platform which we can help us?”
Moving on to the framework, earlier, as Gail was saying, we were trying to execute all the test cases using simulator, emulator, but when it comes to the local executions, you have tremendous problems. One of the problems is if you want to execute on the iOS device, then you have to have Mac with you, then only the execution is seamless, same with Android. Then, we decided, “Okay, we’ll go with Perfecto.” And then our biggest challenge was how we can deliver the test cases that pursuit faster. That’s why we started a bit with the Perfecto on the parallel execution. I can show you the slide where you can see the timing of the execution when we are doing without Perfecto and with Perfecto.
My third point was strategy. Now, coming again to framework, we were looking for a framework who can actually support mobile web, mobile native, including HTML5. We also want our framework built-in who can also support all kinds of APIs. While building our strip, our main intention was, “How I can write my sprint which has low maintenance, and which has the maximum output and optimization?” We are also looking for a framework which can support, as we said, believability or a keyword-driven or code-driven. Good part about delivery, this is that we have experience that once you create your steps in the vidity, then the actually product manager also can take those steps and he can write his scenarios, he can write his output or acceptance criteria, that will give a lot of help to your manual team or to your automation team how to go with the story and what kind of testing has to be done. That was a great, great, great example how we can go beyond our team and how we can help the business.
We were also looking for the reporting. There are tons of framework, there are tons of execution but when it comes to the reporting after the execution, you have to have a report, or you have to have a framework which can spell out the detail analysis that can have a checkpoint, that can have the raw, that can have the trend reporting. The trend reporting is one of the main features because as a team lead, as a team test manager, you can see, “Okay, this particular execution is going on for last two weeks.” And how is the trend, whether it is bad at the beginning of the execution and it is getting better and better at the end, or it’s this other way around. Looking at the trend, you actually can understand where your project is going, how the stories are being delivered, and what is your next path, that was our major concerning area, how I can make it better. We are able to complete our task within the given time.
We also did one more thing here is when the execution is going on, we actually capture the entire clip and that can be shown to a developer rather than giving them the test data. We generally give them the report, they can see the execution as a clip and they can understand, “Okay, what are the steps before the defect has happened?” Which actually helps them to fix it end to end. Then, it comes to the CI integration. Here we are using Jenkins and it is pretty out of the box. We have solidity hub and mode so we can execute the test cases even though we want to execute on the web. On the mobile, we can do it seamlessly, no issues. After we define our framework, we went to select the tool. As I said earlier, we were actually selecting the tool and really comparing that with various computers and we came up with Perfecto because they’re the right partner for us.
Now, coming back to the next point, which is the team. Here, what we have done, we have divided our team into two pieces. We have one team who actually, they are only there to create the common function, pages, object depositories. And once they create the whole stuff, they can handle it to the functional team. Using that steps, the functional teams can actually start writing their test cases in form of BDD. My core team is actually doing the technical stuff and my other team, which I call as a functional team plus automation team, they can write the test cases, they can execute it, they can see the reports and if they have any issues of which in between of the test case, if they want within any API, they can come back to my team of the whole team.
Whole team then help them up and they can come up with a better solution. Here, what is happening, before we get any stories, we take all the required components. We, as a technical team, we decide, “Okay, what are the different components we have to create, what are the different components we have to modify, and what are the different components which we can eliminate?” With these three things, we come up with a plan for the release. That’s why when it comes to the execution, we start our execution literally from day one or day two of the release. Why? Because we have done all the homework before even the screen starts.
We work very closely with developers. Before the court is ready on the environment, we get all the optic IDs from the developer and we start actually building our skeleton which we can give it to our test team and they can start writing their BDDs. In terms of the execution, here you can see that earlier the execution was literally taking 40 minutes. This was the smoke test. When we start in our parallel execution, when we start executing with multiple OS– when I say parallel execution, it is not the execution only on various devices of the same family, but I can execute a few test cases on iOS, again on different versions, and some testing items execute on Android, again on different versions.
Now imagine your one execution is actually happening on four different devices or five different devices. We can say within a day that, “Okay, whether you are able to execute or whether you are able to complete the coverage of your mobile devices–” And yes, we can complete in a day. Here, I’m just giving an example of one of our smoke tests. Now we have around 500-600 test cases. We can give the result in the maximum in one day. Why? Because our execution and our reporting is so clean that it will take hardly any time for our testers as well as our developers to understand.
That makes us pretty fast in terms of our execution. Here you can see the difference of how I started before I start the parallel execution or before I start with my actual device. then with my multiple devices. Here you can see, I’m just giving you one example. Like that, there are multiple devices, multiple examples which we can give you. With this kind of our strategy, we are able to get control of few of the challenges, what Gail has mentioned. Now, we are able to solve through different teams. All the teams are actually coming back to us saying that, “Okay, what you implemented into one group, we want to implement the same thing into the other group.” We are really helping all the groups. Whenever Gail has challenges, we are able to solve it. That’s my end. Back to you.
Eric: Thank you. Thank you very much. We do have time for some questions now. We’re moving to the question parts. The first question is for Amir. Amir, I’m going to ask this question to you. Amir, what are some best practices in managing quality and expanding application scope in architecture?
Amir: Yes, it’s a good question. I think that we touched on a lot of these things in this webinar. I would suggest to the team leads who are dealing with this expansion, this rapid expansion and shortening of the sprint, is really to think about, again, the construct of DevOps. In terms of the tooling, naturally, they need a lab that is ideally in the cloud, that they don’t need to manage that encompasses all the platforms that they’re responsible for, as well as it enables their team to be efficient in Sprint.
In other words, those who are skilled at development, so experiment that enabled Java or JavaScript, etc, coding but also BDD in terms of the English-like scripting that really brings the contribution from less skilled, typically manual testers into the sprint itself from the initiation. One thing is lab, on the topic of people, we spoke about it, but really, looking at your QA team, identifying leading people who can enable the rest of them, that are more skilled and then embedding the typical traditional QA team into the different squads.
Lastly, thinking about it as a process. You have your lab, now think about enabling the transactions that are happening around the lab, the build process, the deployment process, the test process, the reporting process. Enabling all of those to be automated and orchestrated via Jenkins or team city or your build server such that activities are automated and are immediate. When I do a commit, a build happens, it deploys the build on the devices and servers, a test happens, and I get the results. This way you really close the loop between the coding and the defect realization or finding.
In terms of the process, now you cannot zoom out from the concept of coding to finding a defect and you find that this can happen all the time in a scalable manner. In other words, it can have eight different squads or 50 different squad all running at their own pace independently and running very frequent and accelerated integration such that you don’t end up at the end of the sprint and you’re seeing the things don’t integrate. Frequent integration, frequent test cycles in sprint, I think are really the secret to embedding quality in DevOps and bringing a quality product that keeps expanding incrementally in its scope.
Eric: Great, thank you, Amir. Our next question is for Gail. Gail, what has been your biggest struggle throughout the transition to digital platforms to overcome?
Gail: I think the biggest struggle is keeping up with change. Change affects us in a lot of ways in DexYP, we have change from other third-party vendors that we use. So if Google makes changes, we have to quickly react to those changes. If our marketing department decides to launch new products, we have to be able to react to those types of changes very quickly. The other types of things that I talked about in my presentation was the devices and the technology changes and what’s the proper tools to use and will the tools keep up with some of the changes that we have.
It’s always looking for how to make us better and keep up with what we got on our plate. Myself and several other leads in my organization, we try and always keep up with the technologies that are out there, what other companies are using, what our competition is doing so that we can make sure that we’re ahead of the game and we’re more in a proactive mode for change than a reactive mode for change.
I think that’s probably the hardest thing because, not only do you have to keep up with the deadlines that we have from our company leadership on what we want to launch but also to make sure that we’re keeping up with the technologies that are out there and making sure that with the resources we have and the budget that we have, that we’re able to keep up with the amount of change quickly. Again, with the quality, we always want to make sure that we’re adding that quality in there because people have a choice nowadays. They don’t always have to come back to our site or clients don’t always have to utilize us for our advertising. It’s very important to make sure that we give them what they need, and the quality is there so that they do come back, and they enjoy when they come visiting our sites and utilizing what we’ve put out there.
Eric: Great, thank you, Gail. Our next question is for Kedar. Kedar, how would you support different devices, OS, and languages?
Kedar: This is a good question. We encounter this question almost every client every place. As I was talking about my presentation, these key factors about framework, tool and the team, that actually helps us a lot. They determine, in terms of this question, are we changing the world. That if you see Android, Android has various versions right now in the market. I like iOS, iOS actually, if you see, most of the people will go to the latest version. But on the Android side, there are a lot of people still using the KitKat which is the oldest version.
As a service provider, we have to make sure that my framework, my tool is actually able to cater all kind of OS, all kind of devices, which will also make sure that I’m able to support the APIs. With this framework, the robust framework, I would say you are definitely able to solve your problem along with the good partner like Perfecto to get the challenges from your clients and then solve it as soon as possible.
Eric: Wonderful. Thank you, Kedar. That is all the time we have today. That’s all the questions that we have right now. I would like to thank today’s webinar sponsor Apexon. If you’re interested in learning more about Apexon’s services, please email info@apexon.com. I’d also like to thank our three speakers, Amir, Gail, and Kedar for the outstanding and very informative webinar today. Thank you all for your time today and thank you, everyone, for joining us for today’s webinar hosted by IIST, the leaders in education-based certifications and training. For more information on how IIST can help you or your organization, please visit Testinginstitute.com. Again, if you’re interested in learning more about Apexon’s services please email info@apexon.com. Thank you all again for joining us today and have a great day.
