How do you ensure software quality across platforms and devices?

As per my experience, we can define quality criteria based on below parameters 1: Clear functional requirement 2: Well documented testing process 3: Client feedback 4: Code Quality Metrics 5: Industry Standards and Best Practices of SQA 6: Usability Guidelines Quality in software development extends beyond just the codebase; it encompasses a holistic approach that includes various aspects such as design, application flow, infrastructure, and software architecture.

There are different ways to & on which you can define quality criteria. * Process * Tools * Code Review * Code coverage * Unit Testing * Testing * Performance testing * Load testing * Automation testing * Functional Testing * NFR testing When it comes to quality, it does not always limited to code, but also applies to UI/UX, Application flow, Infrastructure, software design.

Unless the software being developed is subject to regulatory approval and thus needs to follow GxP standards then the quality criteria are pretty simple: the acceptance criteria defined for every backlog item (be it a user story or a business epic) must be rigorously evaluated and appropriate evidence collected that they are met. This is far easier said than done because defining robust acceptance criteria is the real challenge for the following reasons: 1. The end user community is typically underrepresented and personas are ill defined. 2. The quality assurance team (not just the QA manager) is rarely involved in backlog creation and refinement let alone following the three amigos approach. 3. Key stakeholders are impatient.

ISO-25010 defines 8 quality characteristics of which 6 are mentioned in the article. However, I would call 'ensuring software quality across platforms and devices' not 'compatibility', but ' portability' (one of the characteristics of ISO-25010). According to ISO-25010, ' compatibility' is the 'degree to which a product can exchange information with other...'. Further on in this article 'compatibility' is described as 'this means that it can run smoothly and consistently on different platforms and devices' which is described in ISO-25010 as 'portability'.

By following below procedures we can ensure software quality across devices and platforms. 1. Cross-Platform Testing 2. A round of smoke testing on Device Emulators/Simulators to test across multiple device 3. Real Device Testing 4. Responsive Design Testing 5. Usability Testing 6. Performance Testing 7. Documentation 8. Feedback Loops

Without defining compatibility we are left with a limited view. we don't know if we invested in native development in the App or if it will be webview (responsive).

investing on analytics such as firebase is also helpful to give the data/product team a proper insight on which line of code the crashes (fatal or not) happened and what type of devices that their users are using when the app crashed. this can help to identify which devices/platforms that need to be focused on so that the product team can make the app compatible in most devices and also prevent future breaks.

It is important to take time to analyze the target demographics and common viewport sizes for the product. A point of sale system that ships with only two different types of equipment, for instance, should be designed to work on only those two different screen dimensions. That being said, the designs should be forward thinking, allowing the product design to be relatively easily accommodated to a different size, as needed. Use of meaningful naming conventions for variables that refer to the device type or size are valuable towards the maintainability of the product design.

Imagine your favorite outfit – it's versatile, comfy, and stylish for any occasion. That's what compatibility design does for software! Here's the lowdown: Compatibility design ensures your software looks stunning on any device, whether it's a giant desktop screen or a tiny smartphone. It's like tailoring the perfect fit for every gadget.

Some of things to consider are 1) Make it automatic / OOB as part of platform product 2) Make it part of overall operational excellence opmech you measure 3) Create a community within your organization to define and evangelize it

Implementing quality assurance is the process of ensuring that software meets specific quality standards and criteria. For example, a software development team might conduct code reviews, testing, and documentation to verify that the software meets functional and non-functional requirements. The software testing team have to conduct system testing, integration testing, and performance testing to identify and address any errors or vulnerabilities. This helps to ensure that the software is of high quality and meets the needs of the end-users.

Many ways to implement code quality and not limited to * Set important quality in Team's mindset, let them take the ownership of it * Peer Review * Lead Review * Unit Testing * Set Review process and without it, code can't be checked in * Lint tools like ESLint, HTMLLint, PythonLint etc * SonarQube Integration - We can defined/get quality rules (incl. duplicate, security), quality gates, Maintainability check * Set Code coverage expectation * Automation testing using Selenium, Cypress, NightWatch, * Black box testing * UI/UX checklist * Regression testing * Accessibility * Responsive check based on devices compatibility * Periodically surprise quality check “Quality means doing it right when no one is looking.” -Henry Ford

even if the feature has been released to the end users, regression testing and smoke testing still and always need to be done to ensure that any new features/fixes are not messing up the released ones

Periodic quality audits can add value to a product design by being more proactive and can often catch potentially costly issues as industry standards for devices and browsers change.

- if possible, always test the product from user/consumer’s perspective - test an issue atleast 3 times before reporting it - understand not just the user scenarios but also the designs & the flows (ui & ux) - test steps & expected results/behaviours are crucial when reporting a bug - retest & regression testing are not the same thing

The software Quality is tested by various devices and platforms to ensure that quality in every software level beyond the regression testing on the platforms to ensure that the software isn't affected by the new deployments.

Users today interact with applications using different devices, operating systems, and browsers and hence has elevated the importance of cross-platform testing in the app development lifecycle Cross platform testing is a type of testing method that verifies whether an application or product functions as intended across multiple platforms that include but are not limited to, different operating systems, browsers and devices. This form of testing is aimed at assessing various aspects of the application, including its functionality, usability, and user interface, under diverse environments. It helps to ensure that all users experience the application seamlessly, regardless of the platform they are using.