How App Quality is Now Everyone’s Responsibility – Neotys Testing Roundup

1. Quality in Quantity: How App Quality is Now Everyone’s Responsibility

As software development teams and practices evolve, the idea that application quality is solely the responsibility of a small group of testers is getting replaced. Application quality is now everyone’s responsibility as making use of continuous quality speeds up the development process, engages more people and gives you a greater chance of catching bugs earlier in development.

We recently wrote about how performance can be a part of everyone’s job and not just rest on the shoulders of a lone performance engineer or isolated team. Producing applications that offer end users a seamless experience is of the utmost importance. There are too many competitors who are more than willing to take frustrated visitors off your hands should they encounter performance issues with your application. Check out this article for a closer look at why continuous quality should be an integral part of your software development lifecycle.

2. Testing Usability for Mobile Applications

Usability is an incredibly important attribute to account for when developing mobile applications. While some apps may fail due to poor content, many often fail due to another issue entirely—they’re just too difficult to use on a mobile device. Again, customers will not hesitate to abandon your application if they are provided with a poor mobile experience.

Mobile usability goes a long way in enhancing end-user app acceptance. But usability starts with the user, and users differ in terms of knowledge, interests, goals, and so on. This article discusses some core usability characteristics that matter to customers, and how test engineers can understand and achieve them. Read it here.

3. The Art of Bug Reporting: How to Market and Get Your Bugs Fixed?

As a software tester, one of the last things you may consider yourself is a marketer—but you do more marketing than you think, especially when it comes to bug reporting. Plain and simple, it’s the duty of the test engineer to get bugs fixed than might have a negative impact on product quality. To do this successfully, testers must prioritize bugs in a way that gives management confidence in the performance of the application.

You have to market the bugs. According to this Software Testing Help article, this involves two steps: writing/recording bugs correctly and knowing everything about the bug so any further details can be explained better. Check out the full post here to learn how better bug reporting can improve the quality of software while also significantly reducing the cost of testing and developing an application.

4. Discussion: Where/How to Obtain Automated Testing Training?

Automated testing has quickly become commonplace in software development. It offers unmatched benefits like allowing for precise and consistent executions on all iterations, for teams to save time and make ideal use of resources with constant and ongoing test executions, and for teams to execute a wide range of tests that negate human error. It’s clear why so many organizations have adopted the practice, however, it does present a learning curve for trained manual testers.

Tina Zylman posted to the Software Testing Club forum wondering how she, as an experienced manual tester, could expand her skills into automated testing. To help bridge this gap, she is looking for classes or any other relevant resources.

Leave a Reply

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