Menu Sheet Overlay
Search Sheet

Manual Testing: Best Practices

    This guide outlines some best practices and tips for manually testing Mobify PWAs. After reading this, you’ll have a preliminary understanding of the following topics:

    Desktop Business Logic #

    A Mobify PWA often leverages existing desktop business logic. Developers do this by methods such as page parsing or using the existing desktop’s backend API. Because of this, it’s important to verify functionality on the desktop page when assessing the functionality of your PWA.

    When manually testing a new feature, it’s good practice to have the PWA and the desktop site in separate windows side by side for easy reference.

    QA Tips:

    It’s important to note that because of this dependency with Desktop that there’s a butterfly effect risk. The PWA relies upon existing functionality on desktop and any changes to the desktop will in turn affect the mobile site. We need to be proactively testing and be aware of desktop changes.

    Devices #

    Ecommerce customers are not viewing our mobile application on Desktop computers, nor are they using Chrome DevTools in mobile mode. They’re viewing our sites on physical devices such as iPhones, Androids and Samsungs etc. When testing we want to have an environment that closely simulates an end user experience. It’s thus important to be testing on physical devices with scrutiny to give us the confidence of quality.

    QA Tips:

    Performance #

    Progressive Web Apps boast a reliable, fast and engaging user experience. To test this, we must assess the quality of speed and positive user-experience of the site in all aspects.

    For more information about designing for performance, check out our article on visual design best practices that can convey a sense of speed.

    Key Elements:

    Network #

    With the goal of testing using the end user’s environment, we need to simulate mobile connection speeds in which the user is not connected to fast Wi-Fi.

    There are ways to throttle your connection using Chrome DevTools in the Network Tab. More information can be found here.

    Having throttling enabled also makes it easier to see how content, such as the page transitions, load into place. This allows you to verify whether the experience is positive. We recommend using regular 3G (750 kb/s download, 250 kb/s upload, 100ms RTT).

    We also have the following tools that can give us a lot of performance metrics: