BeFamily

Challenge

BeFamily reached out to QAwerk to ensure the stability, functionality, and overall readiness of their app for the official release.

They wanted to integrate QA from the outset, recognizing the challenges of managing quality in a new mobile app compared to their previous experience with web-based applications.

Given the dynamic nature of the new app, rapid changes were inevitable, raising concerns about additional workload and UI adjustments affecting stability.

They hoped that having QAwerk’s support from the start would help them navigate these challenges and adapt to evolving requirements.

Solution

At the beginning of our testing, we encountered numerous bugs concerning UI, integration with the calendar, event creation within the app, and data validation. Several bugs were related to push notifications, which would either appear unexpectedly without specific need or fail to appear when necessary. Given the potential for confusion and the risk of users missing important information, it was crucial to address these bugs promptly.

We provided a visual guide for the BeFamily developers, outlining the precise steps to reproduce these types of bugs. By analyzing user actions and scrutinizing vulnerable areas of the app, we gained valuable insights into the nature of the errors. Our collaborative efforts with BeFamily’s developers allowed them to implement targeted fixes, ultimately resolving the issue permanently.

Here are the services we delivered:

• Exploratory Testing. Extensive exploratory testing was conducted as the team delved into the functionalities of BeFamily, assuming the role of first-time users. This approach enabled the team to learn and adapt dynamically, receiving real-time feedback.
• Functional Testing. We performed a thorough set of tests to check how well the system functioned according to BeFamily’s specific requirements. This helped us confirm that all the functional features were correctly implemented and that the system met the defined criteria.
• Smoke Testing. Smoke testing was carried out to set up the initial tests after building the system or making any important changes. Smoke tests focused on the most critical features, ensuring the reliability of the core code. Selected functional tests were integrated as smoke tests to optimize the efficiency of the process.
• GUI Testing. We tested BeFamily’s graphical user interface to make sure it matched its written specifications. This meant checking that all the buttons, icons, and other visual elements looked and behaved exactly as they were supposed to. We made sure that the colors, fonts, and overall layout were consistent with the intended design.
• Regression Testing. Regression testing was a crucial phase in the BeFamily project, ensuring that new code changes didn’t disrupt existing functionalities. We conducted tailored regression tests, aligned with the nature and complexity of new components or defect fixes, both manually and through automated tools.
• Test Documentation. We developed 500 test scenarios for BeFamily, managing the test documentation using Qase.io. With each app release, we update the documentation and add new test scenarios to align with changes in the app. This approach ensures thorough regression testing and minimizes the risk of bugs slipping into production.

Test Automation

Test automation was conducted utilizing Playwright framework with JavaScript and Browserstack. BrowserStack provided us with access to an extensive array of real devices for both Android and iOS systems, along with automated reporting capabilities.

Our automation scope comprised 82 test cases covering essential functionalities, including Login, Sign Up, Agenda, and To-Do features. The setup process encompassed 140 hours, during which we established all tests from scratch, automated the designated test cases, configured reporting systems, reported issues identified during initial runs, and documented the test procedures.