For those who are actively involved in the industry and software application development, I will note that the new progressive web app (PWA) is gaining momentum.
Latest round of support includes Microsoft and Google working together to bring more PWA into the Play Store. Microsoft PWABuilder (make PWAs from existing websites and publish them in app stores) is now working together with Google Bubblewrap tool (used to generate and sign Google Play Store packages from PWAs) to accelerate this happen. For the app maker now able to make shortcuts defined in web manifests to work in their Google Play Store APK versions without any extra tweaking.
With Microsoft now adopting a join force mentality to Google proposed PWA, to create a new generation of web apps, with the expectation to be the future of mobile web, we can expect more accelerated adoption of the PWA for time to come.
In case you are not yet aware of PWA, download Microsoft Outlook and use it in your mobile, that is PWA, it loads like a web page but functions like a mobile app are easier to develop and offer a superior user experience (UX) compared to traditional web apps.
PWA promises to attract users, drive engagement and improve user experience (UX), that is why it is now being under the accelerated growth and adoption to become the new standard in web development.
Progressive web apps (PWA) are the future of technology, combining the best of web and native apps. Below is the progressive web apps (PWA) testing checklist:
When it comes to web or mobile application, it’s not just about writing the code—you also need to give equal importance testing before it’s released for users. Progressive Web Apps Testing requires both manual and automated testing techniques. There will be additional tests to measure both online and offline performance and presentation.
- Creating a PWA ultimately is all about writing a manifest file.
- Write a service worker for caching pages and handling offline data.
- Integrating the service worker into your application. This requires writing code that registers and downloads the service worker.
- Make use of an online service.
PWAs are excellent for visual testing. If a test identifies and detects differences between the expected/baseline image and the actual image that’s detected in the test, the test is not successful. Very often the difference doesn’t come from an issue or a defect but caused by a newly introduced feature or superficial changes.
Site is served over HTTPS? verify Served over HTTPS, as well as verify that Design is mobile-friendly. Manual checking can be helpful. Conduct the Mobile Friendly Test. It is important to look at implementing a responsive design, or adaptively serve a viewport-friendly site.
Offline Loading? All or some of the web pages must work even when your app is offline. As a result, it is important to ensure that your web app responds with a 200 when it is offline. Again, since Google heavily emphasizing on PWA ecosystem, they have best tools for testing PWA apps.
Metadata for ‘Add to Homescreen’? Test if the web app provides metadata for ‘Add to Homescreen.’ You can test for metadata for ‘Add to Homescreen’ functionality.
Page transitions should be smooth. Transitions play an important role in high-end performance. Hence, transitions should not feel slow as you move around. This high-end and seamless performance is important even if you are working on slow internet connection. This should be done manually on a slow network. When you click on any button or link it should immediately respond either by transitioning immediately to the next screen and, while waiting for the app to respond, show a placeholder loading screen or a loading indicator.
Each page must have a URL? Every page on your web app must have a URL and all the URLs must be unique. Test it by checking that every page is linkable by a URL and can be shared on social media or other platforms. The URLs can also be opened directly in new browsers.
As from the above application security testing (AST) progressive web apps (PWA), for experienced testers already know it makes sense to adopt both automated web scanners and manual testing tools to accomplish the PWA security testing requirement.
E-SPIN has been active in the application security testing (AST) since 2005. E-SPIN being active in supply, conduct training and help customer to maintain various application security testing (AST) technologies, from dynamic, static, interactive, mobile, manual (DAST, SAST, IAST, Mobile AST, MAST) to software composition analysis (SCA) and run-time self protection (RASP), web application firewall (WAF). Feel free to contact E-SPIN for the project and operation requirements.