Continuous Testing is a phrase used a lot these days, but what does it mean? On the surface, one definition could be “test all the time” - but that doesn’t really quite cover it. If you were to ask a developer, a QA engineer, or a CIO, you might get somewhat different definitions based on their particular perspective. The gurus at Gartner describe it as:
In a recent webinar, Perfecto CTO Uzi Eilon and I took a look at some of the issues related to PWA testing; we offered a full testing strategy consisting of 6 pillars: Validate PWA Manifest, Validate PWA Service Workers, Validate PWA Specific Capabilities, Properly Test Across Platforms (Responsive Web Design), Object Identification Strategy, Google's PWA Checklist Compliance
Last year, Apple CEO Tim Cook expressed the growing need to make all types of applications – web and mobile – accessible to everyone: “We’ve always viewed accessibility as a human right, and just like human rights are for everyone, we want our products to be accessible to everyone.” ~Tim Cook Websites frequently have been targets of disability discrimination and, unfortunately, this trend is making its way into the domain of mobile applications. [
OK, it’s not exactly a corporate doomsday scenario. Still, a recent story from the BBC is a perfect illustration of why testing real-world scenarios needs to be a part of your testing strategy. The sample size might be too small to draw any definitive conclusions about humanity but, if this group is any indication, you might want to keep an extra eye on your 11-year-old. So, what happened? In a nutshell, some students (aged 5-15 years old) were given a standardized spelling test - on their laptops - online. Have you guessed where this is headed? Well, it appears that some of the students in primary 7 (roughly 6th grade for us Americans) were touched by the light of inspiration. They turned on their online spell checkers.
Why is Tricentis creating a cloud execution partner program? Tricentis’ customers are doing mobile testing in various ways – they do full mobile automation and exploratory testing, some of them prefer simulators or emulators while others want to use real devices. They also can be divided based on the location of devices – some prefer to have them locally, while others want to use device cloud of their choice. Tricentis wants to fulfill all that
FaceID, TouchID, location, camera, and conversational interfaces are offered on such a wide array of devices that it’s enough to make a testing professional dizzy. There’s a constant question buzzing in our testing minds: which device supports which feature?
If you aren’t already talking to your watch, your car, or your smartphone, you will be soon. Users love interacting with services and content on their own devices, at their convenience and on their terms- doing so in a more “human” way frees them inconvenient and tedious text entry. Voice interfaces can make commutes more productive, let you quickly find a TV show, or find great recipes without having to juggle a keyboard and mouse with messy baking hands. As a result of this trend, brands are adopting conversational interfaces as a key element of their digital strategy, expanding their presence beyond web browsers and native mobile applications. Ally Bank, for example, already offers a set of “Alexa skills”, including balance checking, money transfers, recent transactions, etc. The growth in developing Alexa skills has been remarkable; they are becoming an increasingly ubiquitous tool.
More Upgrades Than You Can Shake a Stick At Don’t be fooled by the version number. Appium 1.8 is a major release and it packs the new features to prove it. If you use Appium and you haven’t already upgraded, you’re going to want to. Our own Eran Kinsbruner hosted a webinar with Jonathan Lipps, Appium project lead and founder of Cloud Grey, to give us the low-down on this awesome new release.
If you’re a regular reader of this blog, or if you work in DevOps, you’ve probably already spent a fair amount of time considering which devices you need in your lab. Testing on the right platforms is key to ensuring a great experience for your users. However, in the scramble to make sure your lab is up to date today, you might overlook another critical component of a successful testing strategy: planning. Planning for future changes in the market makes the difference between success today and ongoing success.
App performance can be a killer problem for any digital company, especially when the performance issues take too long to identify. What I have found by working with many of our customers is that the answer can be hiding in the HAR file data- which is why you should always check your HAR files.
2018 has officially arrived! Before we jump head first into the New Year, let’s review some of the most impactful events, trends and changes that took place this past year. When I reflect back, there are a few changes and challenges that stand out in the mobile, browser & IOT testing world. If you want to stay ahead of the ball (drop) in 2018, here are a few topics that took off this past year and are sure to continue in the upward trend for 2018:
How many times have you heard this phrase while watching a game on your phone: “Touchdown!!” (or GOAL!!) but all you can see is the loading dial? How about this: you are sitting on an airplane, trying to watch a video on the flight WiFi and it just stops or pauses constantly. Maybe you’ve tried to watch some home improvement or recipe video that was impossible to watch because it just kept stalling?
More and more markets are moving towards digital channels as their main means of engaging with customers. A majority of companies in North America and Europe have embraced the agile philosophy; close behind and coming up fast is the move towards DevOps practices, which allow teams to release higher quality software at a faster pace.
There’s no doubt that most of the organizations across multiple verticals are aiming toward advanced agile practices, DevOps and continuous deployment. They don’t really have a choice, due to the digital transformation that forces more frequent releases and appealing functionality to continuously be released. Software Automation Reality The reality, however, shows that the industry stands today on average ~20% test automation (The Broken Promise of Test Automation). Source: WQR 2017-2018 There are common reasons that
These days, many brands are finding new ways of streamlining the user experience in order to drive higher adoption rates, increased security, and user satisfaction. Onboard sensors offer a great alternative to tedious manual data entry; in many cases, this not only enhances and simplifies the user experience, but also can allow for the creation of new and compelling flows. Indeed, the successes which have followed the addition of fingerprint ID- and soon, face ID-
The adoption of DevOps methodology has increased and the need to release to production in shorter cycles is driving teams to accelerate process and embed early test automation. Teams operating in this release velocity need fast & reliable feedback for every code change to ensure app quality. Is this new process forcing teams to choose between automation frameworks? Espresso (Android) and XCUITest (iOS) are UI automation frameworks that fit very well with this new development
With a plethora of testing solutions, whether commercial or open-source, some are selenium WebDriver based, some are proprietary, organizations are finding it hard to match the right tools for their cross-browser testing needs. Bryan Osterkamp, Lead Technical Architect, Dev and Ops Infrastructure Architecture Division at USAA, made a very nice analogy for this selection process referring this as an infrastructure as a freeway. “There are a few things about a freeway. For instance, once a freeway
Why Agile Teams Need Continuous Testing What is Continuous Testing and Why Is It Important to Agile? Before we explain why agile teams need continuous testing, let’s offer a definition. Continuous Testing has several meanings. But, when applied within the context of Agile, Continuous Testing refers to the practice that testing activities happen continuously throughout development rather than as a periodic activity or even worse a “stage” in the life of a project/release. As agile
The DevOps era is here, and with it comes the need for testing on many platforms- mobile, desktop web, IoT, chatbots- and many more. With the current pace of innovation, it’s difficult for automated testing to keep up, whether for mobile, cross-browser, or desktop apps. Two or three years ago, organizations were releasing applications a few times a year; today, organizations are releasing a few times a week- or even a few times a day!
We love open source. Who doesn’t? Sadly, it sometimes has its limitations when implementing at the enterprise level. Lucky for us, Wim Selles, a passionate test automation engineer at deTesters, lends us the playbook on his tactical approach to using Protractor to help Rabobank perfect their hybrid app. Over the last few years, there has been tremendous growth in the quantity and quality of open source software testing tools available to DevOps teams. Any test
In his section of The Digital Quality Handbook, Uzi Eilon gives a great overview of one of the keys to test automation: proper object identification. He shares his insights about how objects fit into a healthy test automation strategy and explains how the proper use of XPath expressions contribute to this strategy- something which is often overlooked by developers. The following are 4 key points taken from his explanation of techniques for object identification in
After gathering feedback from customers, we have found the main problem companies usually face when building and sustaining a mobile device lab is the size of their lab- matching the device list to their organization's requirements and sizing the lab accordingly. If the lab size is not accurate, improving test cycle velocity and overall quality will be difficult. In this post, we'll highlight one approach to sizing a mobile device lab based on specific requirements. To help with your
If you're an Android developer, you're probably familiar with Google's Espresso UI test automation framework. Espresso is more lightweight compared to UIAutomator and it’s newer. It supports 2.2 Froyo and up, and it’s also a fluent API with powerful hamcrest ( https://github.com/hamcrest ) integration that helps make code more readable and extensible. Espresso is useful for Hybrid app testing, or webview heavy testing, but it does not have access to system integration tests, therefore, it
Travel back with me… to late September 2016. It’s the Jewish New Year, and I am in Boston, MA. As I celebrate the passing of another great year, I think to myself, “After being in the software quality space for nearly 20 years, isn’t it about time that I reach out to the community of thought leaders and influencers and create an asset that can fill a gap in the market that we can give