It is always interesting to get an inside view on the software testing approach of software development teams that work on large or popular applications. In this blog post, Lou Kosak discusses some changes in practices to improve software quality at Airbnb.
Creating an effective data migration testing strategy is critical to reducing risk and delivering a successful migration. This article offers thoughts and recommendations on how to create a more consistent data migration testing methodology using either a black box or a white box approach.
With Selenium and Jenkins, you can extend Selenium processes to include screenshot comparisons, enabling automatic UX compliance at the speed of your Continuous Integration workflow. Learn how to compare screenshots from one Jenkins run to a repository of known quality, in order to insure that not only does your website work well, it also looks well.
Finding common naming conventions for software development items (variables, classes, etc.) is a major factor to help people collaborate in software development projects. Finding good names is also good if you work on your own and have to revisit your code some months after you wrote it. In this blog post Frank Appel discusses his experience with naming JUnit tests.
Any developer who cares about software quality should be committed to writing unit tests. Used well it can be a vital tool in every developer’s toolbox, but unfortunately the theory and practice don’t always match up. Easily-made mistakes can lead to brittle, unmaintainable and ‘write-only’ tests that not only become difficult to work on, but can lead to a hatred of unit testing in general. Presented here are examples of these mistakes with code samples, why you’re making them and how to avoid them in future.
2Q2U (Quality, Quality in use, actual Usability and User experience) is a specific model used to evaluate the quality of the User Experience (UX) of a mobile application. This article presents a way to use the model and step through the process of doing a real evaluation on the road to improving a mobile application’s usability and UX.
Test driven development follow this pattern: Setup – Execute – Verify the new state. Asking the system under test for its new state has traditionally been done to check the new state. This can create problems with the Law of Demeter. The system under test knows unnecessary much about the objects it is collaborating with.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates