About Windows 10 Surface Windows 10 Surface machines are becoming popular laptops, so many enterprises are developing Windows applications for this platform. The default browser on these machines is Microsoft Edge, which has several form factors and can behave as a laptop or a tablet. In short, there’s a lot that’s new and different on these machines that can go wrong. Naturally, test automation is the appropriate direction for ensuring high quality of applications and
Out-of-window user interaction is fairly common these days with desktop websites. Popups can be used to grab users’ attention or to serve a specific function that one may not want to deliver in the body of the page, etc. Some examples include login popup, and the ability to save or refresh a password in the browser. Recently, HTML5 added common popups which request access to user location, microphone, and memory. The latter, for example, allows
Drive Faster Quality Analysis Through Tags and Customized Test Code Quality visibility is all about logic. It should be fast, easy and mostly effective – if the dashboard or report that you’re using gives you the right ‘hint’ of what is the next move – then you’re all set. When it comes to gaining fast and efficient quality analysis, these are usually the pains we hear: Test executions - length as well as context-driven test
Last week, we hosted a webinar on Espresso, the UI testing framework for Android native apps. As an introductory, it was great to see a mix of experiences and skill sets in the audience We chose this topic because we see many customers interested in using Espresso, migrating from other frameworks, and combining testing technologies to include more testing in every build cycle. Questions: Daniel: “What's your opinion about using UIAutomator with Espresso? It's a
Communicating quality for your digital products across the organization is becoming a MUST. Having the ability to take data-driven decisions in real-time enables organizations to move faster and assure their customer digital experience. As activities are growing and teams become hybrid (as part of the move to agile workflows), it is hard to keep everyone on the same page. In most cases, team communications are increasingly noisy and overwhelmed by the large amount of data that
One of the key pillars of Agile is to drive effective interactions between the right individuals. We want to structure teams that are able to deliver value in a complex environment. Since we believe face-to-face interaction amongst co-located individuals is the best medium of communication, we strive to create co-located teams in which all participants are delivering value, especially for our tough features/initiatives, if not all of our work. We believe in focusing development
Responsive web development requires detailed attention when incorporating testing practices; the same (hopefully) code is intended to render on many screen sizes and operating systems/versions. In addition, HTML5 functionality may assume access to local sensors to drive a richer and streamlined experience, for example, automatic location detection, further complicating the responsive web test strategy. The testing matrix becomes sizable, while the time-to-test shrinks from increasing competitive pressure and the transition to agile. In this article I'll
Software teams aspire to work fast, adapt to their market’s needs, and to have a sense of pride in their work. Defects can crush those aspirations, which means they need to be addressed as early as possible. Testing as part of every build improves quality and velocity by reducing re-work through fast feedback on code changes, but there’s far more to it than automated testing. "Quality is more important than quantity, and in the end,
As a part of our weeklong series on “Getting Started with Mobile App Testing” today we look at mobile test automation, and specifically, automation that works. And that’s an important differentiator. When apps fail, close to 50% of developers site a lack of reliable automation as the primary reason (read the report). The pace of modern mobile development coupled with the variety of tests required to ensure delivery of a quality product have driven development
Many organizations are adopting agile practices to speed up their development pace and release apps to production in shorter cycles. But in many cases, especially in large organizations, the continuous integration testing activity is still performed by a centralized QA team late in the development cycle. This makes it hard to thoroughly test the "true" digital experience, even if there is significant test automation in place, and still have enough time to fix issues before
In the spirit of #30daysofmobiletesting, (which you should check out if you haven't already) I recorded a cool test automation video to show you. The video checks off challenge number 8, "write automated checks with a tool like Espresso, Calabash or Appium." I did it with iOS and Android, so I guess that checks off number 10 also, which is "perform an update test on iOS or Android." :) Day 8 Challenge: Test Automation with a tool like
With 60% of the industry still functioning at 30% mobile test automation it's clear that manual testing is taking a major chunk of a testing team's time. As we acknowledge the need for both manual and automation testing, and without drilling down into the caveats of manual testing, let's understand how can teams can reduce the time it takes, and even transition to an automated approach to testing. 1. Manual and Automation Testing: Analyze Your Existing Test
Do you suffer from low test automation coverage for code or devices? Even skilled app development teams hit a wall when trying to improve their delivery speed and app quality. Swamped with an existing backlog of defects from the last release, development teams have no time to deal with broken automated tests, so they often disable the tests so they can move on. Good news though: resilient automated tests can help improve speed and quality.
Developers and testers typically look for speed and agility. Over the past few years the concept of continuousness in mobile testing has been added to that mix. DevTest teams are seeking continuous capabilities in development, testing and management. Software Testing News this week analyzed how the mobile testing space is being defined by this term, "continuous." More and more, mobile app capabilities can be achieved through continuous integration, testing and quality. Ultimately, the article states,
All companies making the transition to digital share one common goal: release high-quality mobile apps more quickly. Whether they're introducing new app functionality, fixing a production issue or supporting a new operating system, time (or the lack of it) is always a factor. If you're relying on manual testing over test automation, get ready to lose the race against time. The consequences can be rough if you don't deliver a good working app in a
Google has just released its new major platform code name "Nougat" (7.0). Along with the excitement of a new platform introduction, there are important implications on existing apps, test scenarios and Android product release schedules. First, let's clarify that most of the Nexus devices such as 6, 9, 5X, 6P and the Pixel C tablet (older devices like Nexus 5 and Nexus 7 won't get this update) are eligible to get an upgrade through the Beta program enrollment.
When it comes to improving the speed of app releases, it's critical to have a reliable build process. Broken builds, missing files and failed unit testing are symptoms of a more fundamental problem: the engine that keeps your team rolling needs maintenance. But before we try to fight one fire at a time, let's consider what got us here in the first place. Continuous integration is not a nanny With a continuous integration (CI) server,
If you're an Android developer, you're probably familiar with Google's Espresso test automation framework. As an open-source tool, it's very easy for developers to use and extend within their working environment (Android Studio IDE). But before discussing the benefits of Espresso, let's understand the motivations and pains developers and test automation engineers face today while trying to validate their Android application (APK) throughout the build/dev/test workflow. Each build needs to be validated after code changes
When was the last time you locked your keys in your car? Personally, I've done this half a dozen times. And getting a locksmith out to your car is time-consuming and frustrating. Now imagine a world where you can remotely lock/unlock your car or more, all from your phone or even through a web portal. The connected care is not a future scenario -- it's happening today. Will a connected car be in your driveway?
There's a shift to open-source mobile test automation tools happening today among developers and QA. And it's not just happening in mobile testing. Many mature technology sectors are adopting lightweight, vendor-transparent tools to fulfill the need for speed and integration. As with many free and open-source software markets however, a plethora of tools complicates the selection process. How do you know what to spend time learning, integrating and deploying in your own environment? This post
Figuring out the best test automation plan is one of the biggest frustrations for today's digital teams. Organizations struggle to develop cross-platform
When building an agile testing team, there are assumptions and then there's reality. Below are some questions to consider as you assess your company's agile progress. Are your developer and QA teams really working together in an agile way to deliver great digital experiences? Does your agile team have the right skills to be successful? Who's actually in charge of your agile strategy? See which mobile devices to test on and create a test coverage
Today we're excited to announce that Perfecto was among the select companies that Forrester invited to participate in "The Forrester Wave™: Mobile Front-End Test Automation Tools, Q2 2016." And even better than that, Perfecto was cited as a "Leader." In the report, Forrester identified the 10 most significant vendors in the market. Each company was evaluated based on a set of 40 criteria, categorized into three groups: Current offering, strategy and market presence. Also, Forrester
Developing a mobile test automation scenario isn't that complicated because developers and testers can use a variety of commercial automation frameworks or open source tools such as Selenium and Appium to automate their testing processes. However, when trying to execute these tests on real devices, or integrate them into an Agile or CI (continuous integration) workflow, things get a little more complicated. What are the major challenges around mobile test automation? The benefit of developing an automated