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.
Mobile devices are now one of the major market for software. This article discusses the four main challenges of software testing concerning mobile applications: the variety of devices and operating systems; the performance of networks, the user interfaces; the limited amount of software testing tools targeting this area.
Managers play a critical role in the success or failure of test automation. Although most testers and some test managers have a realistic view of what automation can and cannot do, many senior managers have firm ideas about automation that are misguided—or downright wrong.
Unit testing seems to be the most natural way for programmers to test their own code. In this small blog post, Henrik Warne shares some of the issues that people have when they switch from manual testing to a unit testing framework like JUnit.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates