Listen to Jonathan Lipps, Appium architect and manager of HeadSpin University, talk about the future of mechanisation testing for media/OTT and early specialised devices. https: //soundcloud.com/headspinio/jonathan-lipps

Synopsis

One of the biggest visions for Appium is that it can essentially aid provide mechanisation support for any application platform.

If we call it an coating, usually that means that there ’ s some kind of user interface to tap or click or type into. had create a full model for automation for quiz web browser as most things receive user interface that people interact with. When we started work on Appium, we said, “ Okay, well, why don ’ t we just extend that variety of insight to new platforms? ” Eight years ago, the obvious new program were iOS and Android. Now there ’ s a whole other set of platform out there such as all the TV, like Apple TV, FireTV, Roku, Chromecast, etc.

Remotely run cross browser tests and debug mobile, web, audio and video application on thousands of devices around the world..

Providing automation puppet for application platforms actually helps the platform and ultimately assist the end users by making sure that app developers have the tools they need to release quickly and to turn software that actually act good. Whether you are the Chrome OS team or the Roku team, you are definitely incentivized to give your application developer, who are writing apps for your program, the creature to help make sure that their coating are eminent quality. Some eld ago Microsoft had approached me to make examination automation for Windows applications available as part of Appium. Because they saw a lot of citizenry using Appium, they wanted to get sure that everyone developing apps for the Windows operating system had an easygoing way to test those applications as part of their package development cycle.

Appium has a finish of build out the tools for the vendors that don ’ t necessarily have a real vision for providing full automation for their platform yet and making it available to the world. And then hopefully bringing the program marketer along into the fold, to say “ Yes, this is the way we want to do automation. ”

A lot of the employment that I ’ ve been doing this last year has be on figuring out how to make Appium really easily extensible so that anybody, even if they are not on the Appium nucleus team, can think about creating an Appium driver for a new program and share it with the world. Then everybody can use the same techniques they use to automate web and wandering applications to automate applications on any brand new or bespoke program.

Listen to Brien Colwell, HeadSpin CTO, weigh in on HeadSpin ’ s sight for supporting tryout automation for our customers in the media, entertainment, and gaming space. https: //soundcloud.com/headspinio/brien-colwell

Synopsis

There ’ s a actually interesting historic note hither too, which is, if you look at test framework from 10 years ago to test frameworks that are expend today, there ’ s really one commonness and that ’ s Appium and WebDriver. We ’ ve seen this sort of long term vision of enabling a standard examination program that ’ s easy to learn that act across a broad number of devices, to be the preference of the industry, and platform that do this do see heavy espousal in terms of testers.

Jonathan, evidently, is the seer who is seem five to ten years into the futurity and saying, look, if we can get more device into this platform we will actually have something that has a lot of abide power in the industry. It ’ s also implausibly knock-down from an industriousness viewpoint that we can train people to recycle their skills. If you already get a large workforce of testers who already know, for instance, they can easy expand their attainment set to Roku and KaiOS.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Now there ’ s also the little term consideration which is thatnot every device can reasonably support Appium.In the next one to five years thither ’ s always proceed to be devices, especially legacy devices, that don ’ t genuinely support Appium. For many of these devices the HeadSpin solution go lots deeper on the media side, try more from what the user see and hears, use more cameras, using more audio, particularly with our AV box, to drive these test cases. To support these devices, we ’ re partner with companies who specialize in compose support for this long tail of covering.

There are a few eccentric of applications that are interesting for us. For example, punt applications. Gaming is historically something that ’ s been very hard to test generically. In the gambling diligence, there ’ s a direction where developers build tryout model now into their code. And so the QA team works very closely with the development team to progress out these sort of, as part of the application itself. That ’ s something that right now there really is no vision for in the industry—it ’ s deal on a case by suit basis. So we ’ re having the conversation with the development team on what are the best practices for their game. They might not be capable to test everything with Appium. They might involve to really qualify their coating to allow it to be tested fully. And we ’ re find the same direction with media applications, that this is a partnership between the maturation team and the testing team.

So we ’ re looking at working with spouse who build specialised examination hardware, with HeadSpin take in the user experience analytics, and ultimately the infrastructure and API ’ s to motor automation from the end exploiter view. There ’ s a partner we ’ re working with where (rattling similar to games) they hold an SDK that you embed in your application. You essentially issue commands through this SDK and it automate your application, so the development squad really has to write code as piece of their test application to drive the mechanization.

Right now this is a little term thing, but I think there ’ s really a long term vision where Appium can also facilitate this sort of embedded testing. Right now Appium really much has this philosophy that you do not necessitate to modify your coating. But as we ’ re seeing in games and media, it seems the norm flop now in the diligence is that you do need to modify your application to fully.

In Jonathan ’ s ten year vision, these modification can be include as part of a mutual fungible framework for Appium. If you have a QA engineer who ’ s specialized in gaming, and they ’ ve built up a very specific skill set that does not translate to, for example, medium try, HeadSpin ’ s vision is that even this can can be fold under a consistent fabric that they can be condition on. And I believe that part of the five to ten twelvemonth vision of Appium is getting the gimmick vendors on board, and too identifying constituent of the industry that do testing differently and start to address those.

is our vehicle where we ’ re assay to train engineers to a standard so that they can become skilled at essay any character of application, whether it ’ s roving browser, medium, or play, giving them a set of testing skills that hold broadly across the industry. We ’ re seem at Appium as the vehicle that will enable this kind of standardization of science.

To summarize, in the little term there are these exceptions right now, like gambling and medium, and for these exceptions, we approach them with our audio visual engineering, as well as with mate. So those are the two early point I desire to bring into the discussion.

Overall, I opine there is a great vision here. We ’ re seeing a long condition vision and we ’ re seeing short term what doesn ’ t fit into that sight. And I think it ’ s interesting to guide a sight of the industriousness flop now.

Curious about the?

Contact us to.

FAQs

1. How should testers name trial cases that are appropriate for mechanization?

Identifying suitable test event for automation is all-important to the effectiveness of mechanisation examination. Some examination cases that can be automated are:

• Tests that are do for several builds
• Tests that result in human errors
• Tests that need numerous data sets.
• Tests with higher danger.
• Tests that can not be performed manually
• Tests that are time-consuming and labor-intensive to run manually
• Tests that are to be performed on various hardware or package platform configurations.

2. What are the various types of prove framework technique?

Automation testing frameworks are of four types:

• Data-Driven Testing framework
• Modular Testing fabric
• Keyword-Driven Testing framework
• Hybrid Testing framework

3. What are the indispensable modules of automated testing framework?

The indispensable modules of an automation essay framework are:

• Test Assertion Tool
• Data Setup
• Build Management Tool
• Continuous integrating tool
• Reporting tool
• Logging tool

4. What is the standard for scripting for perform automatise testing?

Testers must take the postdate scripting standards for perform automation testing:

• Uniform identify convention
• Three lines of comments for every ten lines of codification
• Adequate roughness
• Full-bodied recovery scenario and error-handling
• Usage of fabric wherever workable

4 Parts

Connet Now