Using a Model Based Approach to Evaluate and Improve Mobile User Experience

March 17, 2014 0

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.

TDD: Tell, Don’t Ask

March 13, 2014 0

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.

Overcoming 4 Challenges of Mobile App Testing

March 10, 2014 0

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.

What Managers Think They Know about Test Automation

March 6, 2014 0

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 Mistakes

March 4, 2014 0

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.

Transition to Agile Testing – Part 3 The New Processes

February 24, 2014 0

Software testing during the transition to Agile is not easy. This third part explains how your software quality assurance processes should change. It discusses how to cope with rapid development cycle and frequent code changes that are at the heart of the Agile approaches.

Using a Debugger or a Log to Find Bugs

February 18, 2014 0

When you have a bug in your software, you cannot always just read the code to find the cause of the bug. Two techniques are used for further investigation: the debugger allow to follow the execution of the code, while writing logs allow write multiple snapshots of contexts. In this article, Henrik Warne explains why you cannot rely only on a debugger to find bugs.

1 106 107 108 109 110 171