The Joy of Exploratory Testing

If you’re wondering whether your software is working as well as it could, I’m going to tell you how to use exploratory testing as a tool to find out.

I am Marianne Murray, QA Practice Lead at Robots & Pencils. I’ve been testing software for more years than I care to admit! I am posting here to share some of the things that bring our QA team joy in testing, and why we are so passionate about delivering a quality product.

What is Exploratory Testing?

Exploratory testing is a type of testing where the tester sets a goal or mission and “explores” to experience the product, to learn, and garner information around the state of the product and support planning detailed tests.

“There are no mistakes, just happy accidents.” ¹

Cem Kaner, who coined the term in 1984,² defined exploratory testing as “a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of their work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project.”

In short, exploratory testing is all about discovery, investigation, and learning. It emphasizes personal freedom and responsibility of the individual tester.

“Go out on a limb. That’s where the fruit is.” ¹

When do we use it?

We use exploratory testing when we want to investigate and learn. It is a quick way to probe the features and provide qualitative feedback. We often use exploratory tests as a launching point when we are testing an existing product, or to get up to speed when joining an in-flight project. We can also use this type of testing when time is not on our side and we are looking to provide quick feedback to the team.

“Anytime you learn, you gain.” ¹

What are the benefits?

A challenge that we face in detailed functional testing is that testers can get lost in the weeds. Exploratory testing allows us to view the big picture and to place ourselves in the shoes of our users. We can use it as a jumping off point for other types of testing as well. For example, we can explore negative scenarios around API testing, or explore how an app behaves in a different language and use that information to develop and refine test cases.

“It’s hard to see things when you are too close. Take a step back and look.” ¹

What are the shortcomings?

The results of exploratory testing may be harder to communicate concisely. The testing and interpretation of results are more dependent on domain knowledge and tester skill. Testers also need to take great notes around execution and steps to ensure issues can be replicated.

“If you do too much, it’s going to lose its effectiveness.” ¹

What tools are used?

Testers use the same tools to perform both exploratory and functional testing. The main difference is the level of detail in the test case and results notes. At Robots & Pencils, we use TestRail to capture our test cases. We have a separate template to capture the higher level free-flow format that is used for exploratory testing.

“However you think it should be, that’s exactly how it should be.” ¹

Who can do exploratory testing?

At R&P, our QA Robots are our testers who perform exploratory testing in conjunction with other types of testing. These tests help gather information to highlight areas needing additional testing and focus attention for deep dives.

“Talent is a pursued interest. Anything you’re willing to practice, you can do.” ¹

Each member of our QA team comes from a different background. There is no one path to becoming a tester. But what each of us has in common is the joy we find in testing. We start with the unknown. We research and learn and build our understanding of the product, while providing value and information around the software.

“You can do anything you want. This is your world.” ¹

Exploratory testing is often the right option for companies looking to quickly identify quality concerns, highlight areas for future focus, or investigate the state of a product. Want to learn more? Reach out to us at R&P to help figure out the best test plan for your digital product today at https://www.robotsandpencils.com/#contact.

Marianne Murray, QA Practice Lead at Robots & Pencils

WheelUI: An Alternative to Cross-Platform Development

You know that mobile is important to your business. Maybe you’re considering an idea for a new app or mobile strategy. Or, perhaps your existing app needs a refresh. Either way, you have a limited budget you need to use effectively. As you look to optimize costs, deciding between cross-platform and native app development will be one of the early decisions you need to make. Robots & Pencils has a solution: an alternative to cross-platform development that provides the best of both worlds.

Comparing Native and Cross-Platform Apps

If you’re unfamiliar or need a refresher, native app development uses first-party tools created and provided by Apple and Android. You build one app for Android and another for iOS, each using their own programming language. With native, you can ensure that each app meets UX standards specific to its platform. Natives apps can also access all the features that an Android or iOS device offers.

On the other hand, cross-platform development uses third-party tools as an added layer on top of the native tools. These tools let you build one app that works on both Android and iOS. The premise for using cross-platform is simple. Rather than developing one app for each platform, you build once, deploy on multiple platforms, and save money. Sounds great, right? The issue is that experts widely acknowledge native apps, not cross-platform apps, as providing the best user experience and greatest feature availability. A better user experience means higher user adoption. Higher adoption equals more business value and more return on your investment, which obviously is what you want.

The other concern is that the preferred choice of cross-platform tools changes frequently. This instability can make it hard to maintain cross-platform apps and find skilled cross-platform developers. Also, despite the promise of a single set of code, cross-platform tools often require the use of native code as well. As a result, cross-platform apps can have iOS and Android code in addition to the cross-platform tool. Ultimately, cross-platform apps may be cheaper to build at first. However, they are expensive to maintain and less attractive to users.

WheelUI: Don’t Reinvent the Wheel

So, how can a budget-sensitive company provide the best possible user experience and utilize the full range of features on each platform to get the highest ROI? Enter WheelUI. Created by the mobile team at Robots & Pencils, WheelUI helps you build a native application on each platform for less total cost than cross-platform development. It’s the most affordable cross-platform development alternative out there!

How WheelUI Works as a Cross-Platform Development Alternative

The majority of a mobile app is often a handful of commonly used screens and UI components. Say the login view, menus, and a news feed, to name a few. This is where WheelUI comes in. WheelUI is an in-house R&P framework that provides common UI (user interface) screens and components for our clients.

All WheelUI components use native code. The code is Swift for iOS and Kotlin for Android. Because WheelUI is native, the UX of each screen matches the platform. (Having screens that don’t match user expectations for iOS or Android is a common UX pitfall of cross-platform apps.)

Additionally, each WheelUI screen has already had the Pencil touch, with our talented UX and UI experts leading the design of these UI components. All WheelUI screens are also easily configurable to your color palette, font, and other brand needs, so that your brand still shines through in your app.

The major benefit WheelUI offers clients is that a team no longer needs to design or build each screen anew. This means that you can get the UX and feature benefits of native code for a much lower cost. And by saving money on those common screens, clients can apply a larger portion of the budget to creating custom code and UI for the unique features that makes their app stand out.

WheelUI Time & Cost Savings

Depending on how many of the WheelUI app components you use, we estimate up to 40% cost savings compared to a full custom native project. (Think–you’re saving on design, development, project management, QA, everything. It adds up!)

Many businesses expect cross-platform development to cut costs in half since it (in theory) requires one codebase instead of two. However, costs like design, QA, and project management are relatively equal between cross-platform and full custom native. Plus, because cross-platform apps are built on top of another software layer, oddities sometimes slow down development and increase total project cost. Based on our experience, cross-platform is more likely to save only around 20% from native development. Therefore, even when you add on custom development to a WheelUI project, you can still save money compared to a cross-platform project. You will have the budget to build that killer feature that elevates your app above the rest.

On top of cost savings, WheelUI also cuts your time to release. The WheelUI screens are built, thoroughly tested, and ready to go. All we need to do is load up your data. Using WheelUI as a cross-platform development alternative could cut as much as 40% off your total project timeline.

WheelUI vs Cross-Platform: Talent Availability and Maintainability

Cross-platform tools have shown themselves to be widely adopted for short periods of time. As the desire to use a specific cross-platform tool wanes, companies who built apps in those platforms have to decide whether to keep supporting the tool or rewrite their entire app. That’s a big risk to weigh if you’re considering cross-platform development.

Native code, which WheelUI uses, has shown itself to last. At R&P, we’ve supported native apps for 10 plus years with no signs of support ending. By keeping WheelUI native, we’re looking out for the long-term viability of our clients. On top of maintainability, the ephemeral nature of cross-platform tools has led to a lack of talent availability. Many developers are uninterested in mastering a platform that could end up disappearing within a handful of years. Comparatively, native iOS and Android developers are readily available, so you’ll have a much easier time finding a developer who can work on your native app built with WheelUI.

Getting Started with WheelUI

WheelUI keeps all the strengths of native code, but offers it at less cost than cross-platform or a full custom development project. WheelUI lets you prioritize your app user experience to maximize the business value of your app while also saving money and time. At R&P, we’re already using WheelUI in our own products.

It’s said that cross-platform is built to release and native is built to maintain, but we believe that WheelUI can do both.

To learn more and discuss your mobile strategy and pricing for app development with WheelUI, email us at hello@robotsandpencils.com.