The Rise of Progressive Web Apps and The Impact on Cross-Browser Testing

PWAs have the ability to transform the way people experience the web.

There are a few things we can agree we have seen happen. The first being that we figured out the digital market from an application type perspective. Secondly, we have seen the rise of mobile, and lastly, the incredible transformation of web to responsive web. In response, now we should all start getting used to a whole new type of application that should change the entire user experience and offer new web functionality–let us take this moment to introduce PWAs.

Google.com is a very clear example of such an app. You have to begin to understand them as at the time this article was written, Apple was about to introduce PWA capabilities* in its upcoming WebKit engine. 

What are Progressive Web Apps?

If you were to refer to the Google official website dedicated to PWAs, PWAs are defined as “A new way to deliver amazing user experiences on the web.”

Going into more detail, David Rubinstein from SD Times, added even more insights into these new app types.

PWAs can use device features like cameras, data storage, GPS, motion sensors, face detection, push notifications, and more. This will pave the way for AR and VR experiences, right on the web. Imagine being able to redecorate your home virtually using nothing but your phone and a PWA. Pan your camera around a room, then use tools on a website to change wall colors, try out furniture, hang new artwork, and more. It may feel like a futuristic fantasy, but it’s becoming close to turning into a reality.

The key behind PWA apps is to provide a rich end-user alternative to native apps. These apps can be launched from the device home screen adding layers of performance, reliability, and functionality to a web application without the need to install anything from the app store. In addition, the apps are still JavaScript based and with additional specific API’s, they can work even when there’s no internet connection, and that’s a huge advantage.

PWAs leverage 2 main architectural features:

Service Workers – give developers the ability to manually manage the caching of assets and control the experience when there is no network connectivity.

Web App Manifest – the file within the PWA that describes the app, provides metadata specific to the app like icons, splash screens, and more. See image below for an example Google offers for such a descriptor file (Json).

In order to check the correctness of your PWA checklist and the entire app, Google offers some tools as part of their documentation, like this Progressive Web Apps checklist and their chrome built-in DevTools (see below visual).

As deeply covered in this great DZone article, good PWAs also implement the PRPL pattern recommended by Google to enhance performance.

What Are the Implications of PWAs for Cross-Browser Sites and Mobile Apps?

To understand the implications, I recommend dividing the question into the impacted Personas.

  1. Developers
  2. Testers
  3. Business
  4. End-Users

Each of the above Personas will have different benefits and implications when adopting this kind of app.

Developers

For existing web developers, this new app type should present a whole new world of innovative opportunities. Since PWAs are still JavaScript based apps, developers do not need to gain new skills, but rather learn the new APIs offered through the Service Workers  and see how they can be leveraged by their websites. 

Since the PWA app runs on a mobile device and can be launched without a network connection and without any installation, it obviously needs to be validated by developers through unit and integration tests.

Going forward, the market envisions these apps impacting the native apps architecture in a way that results in only 1 type of app that can seamlessly run on both browsers and mobile devices with one single implementation that will require a heavier lift and re-work.

Testers

</span style>

For testers, as in every new implementation, new tests (manual/automated) need to be developed, executed, and fit into the overall pipeline.

PWAs, in particular, introduce unique use cases:

  • No network operation
  • High performance 
  • Sensors-based functionality (Location, Camera for AR/VR, and more)
  • Cross-device functionality (like in Responsive, the experience should be the same regardless of the screen size/HW etc.)
  • Adhering to the design and checklist required by Google and (soon) Apple*
  • Accessibility is always a need
  • Security of these apps (with and without being connected to the network)
Business

</span style>

For the business, the new app types shall help increase the end-user engagement with the business. When having a web application that is richer in functionality, performs fast, and can be “always on” through an easy launch from the customers’ device home screen, this by definition, should increase usage and move the needle to the business.

Our assumption is that large enterprises are already looking into these types of apps as the next-gen RWD apps.

End-Users

</span style>

At the end of the day, all products are aiming to get greater engagements with the customers and beat the competition. Obviously, if the end users understand the value in these apps and “feel” it in their day by day activities, this will be a clear Win-Win situation to both the organization as well as the customer.

To assure end-user experience, as Google envisioned when first launching this technology 3 years ago, which is the time when this article was written (2015), Dev and Test teams should continue their Continuous Testing activities and make sure they are covering sufficient platform, features, use cases between each release, and each new release of a platform or device.

To conclude this article, I highly recommend watching the short video and reading the blog from Mozilla on how PWAs live within Firefox and how different the experience each users get from such apps (see below Firefox Wego app within Firefox browser in the background and a PWA Wego app in the foreground).

Happy PWA Testing!

*Things in this article may be outdated

Eran Kinsbruner
Eran Kinsbruner is the mobile evangelist at Perfecto and the author of The Digital Quality Handbook, as well as a monthly columnist at InfoWorld.com. He is a software engineering professional with nearly twenty years of experience at companies such as Matrix, Sun Microsystems, General Electric, Texas Instruments and NeuStar. He holds various industry certifications from ISTQB, CMMI, and others. Eran is a recognized mobile testing influencer and thought leader, as well as an experienced speaker in the major software engineering conferences. He is also a patent-holding inventor for a test exclusion automated mechanism for mobile J2ME testing, public speaker, researcher, and blogger. He can be found all over social media, including on Facebook, Twitter (@ek121268), LinkedIn, and his professional mobile testing blog.

The Related Post

Are you looking for the best books on software testing methods? Here are 4 books that should be on your reading list! The Way of the Web Tester: A Beginner’s Guide to Automating Tests By Jonathan Rasmusson Whether you’re a traditional software tester, a developer, or a team lead, this is the book for you! It ...
This article was adapted from a presentation titled “How to Optimize Your Web Testing Strategy” to be presented by Hung Q. Nguyen, CEO and founder of LogiGear Corporation, at the Software Test & Performance Conference 2006 at the Hyatt Regency Cambridge, Massachusetts (November 7 – 9, 2006). Click here to jump to more information on ...
Experience-based recommendations to test the brains that drive the devices In essentially every embedded system there is some sort of product testing. Typically there is a list of product-level requirements (what the product does), and a set of tests designed to make sure the product works correctly. For many products there is also a set ...
David S. Janzen – Associate Professor of Computer Science Department California Polytechnic State University, San Luis Obispo – homepage LogiGear: How did you get into software testing and what do you find interesting about it? Professor Janzen: The thing I enjoy most about computing is creating something that helps people. Since my first real job ...
From cross-device testing, to regression testing, to load testing, to data-driven testing, check out the types of testing that are suitable for Test Automation. Scene: Interior QA Department. Engineering is preparing for a final product launch with a deadline that is 12 weeks away. In 6 weeks, there will be a 1 week quality gate, ...
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Introduction Many look upon Software Testing as a cost. While it is true that Software Testing does cost money, in many cases significant amounts of money, it is also an activity that helps an organization to ...
Dr. Cem Kaner – Director, Center for Software Testing Education & Research, Florida Institute of Technology PC World Vietnam: What did you think of VISTACON 2010? Dr. Kaner: I am very impressed that the event was very professionally organized and happy to meet my old colleagues to share and exchange more about our area of ...
Most have probably heard the expression ‘less is more‘, or know of the ‘keep it simple and stupid‘ principle. These are general and well-accepted principles for design and architecture in general, and something that any software architect should aspire to. Similarly, Richard P. Gabriel (a major figure in the world of Lisp programming language, accomplished poet, and currently ...
Internet-based per-use service models are turning things upside down in the software development industry, prompting rapid expansion in the development of some products and measurable reduction in others. (Gartner, August 2008) This global transition toward computing “in the Cloud” introduces a whole new level of challenge when it comes to software testing.
Introduction Software Testing 3.0 is a strategic end-to-end framework for change based upon a strategy to drive testing activities, tool selection, and people development that finally delivers on the promise of software testing. For more details on the evolution of software testing and Software Testing 3.0 see: Software Testing 3.0: Delivering on the Promise of ...
Think you’re up for a challenge? Print this word search out! See if you can find all the words and learn a few new software testing terms in the process. To see how you’ve done, check your answers in the answer key below. *You can check the answer key here.
LogiGear Magazine – May 2011 – The Test Process Improvement Issue

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe