When a software development team switches its approach to an Agile framework like Scrum, the place of software testing changes. In his book Scrum Product Ownership, Robert Galen describes the new role of software testers in Agile teams and their relationships with the product owners.

In classical (waterfall) project management approaches, the requirements review is an essential gate before starting the actual software development phase. If you participate to these meetings as a software tester, your role is to make sure that the software requirements are testable during the acceptance testing process. In this article, Richard Ellison provides advice on how to handle the requirements validation process from a software testing perspective.

Arquillian is an open source testing platform for the JVM that enables to easily create automated integration, functional and acceptance tests for Java middleware. In this article, Alex Soto presents three options to use Arquillian Cube to manager Docker containers from Arquillian.

This article discusses the alternative to acceptance testing in software development. There’s always the option not to write acceptance tests. If you genuinely don’t have a customer or if you are your own customer, it’s worth thinking carefully about whether there’s value in following the story delivery lifecycle in full.

There is nothing worse than building right the wrong software. Acceptance testing is the activity that allows the customer to validate that the delivered software meets their needs and specifications. If acceptance testing play an important role in validating software delivery, it can also cause some issues as Toby Weston explains it in his book “Essential Acceptance Testing”.

Usability testing has been around so long that it’s the most well-known and most frequently practiced user research method. So I find it amazing that there are still so many misconceptions about usability testing. In this column, I’ll debunk the most common myths and misconceptions that I’ve encountered over the years.

If you are a good software tester, but if you can’t communicate well what you find, you provide little value and are not very useful to your project team. This article gives you some hints specific to mobile applications testing on how to become a great bug reporter. Your teammates will love you for this and you will prove your value as a skilled team member.

Besides usability specialists, all design team members should observe usability. It's also good to invite executives. Although biased conclusions are possible, they're far outweighed by the benefits of increased buy-in and empathy.

This article will be useful for those specialists who are not indifferent to the GUI problems and are interested in getting good GUI. It’s hard to give clear and full definition for the good GUI. So let’s at the moment agree that we’ll understand good GUI as the GUI which helps user to perform his tasks effectively and provide software product with commercial success.

If you are entering into the cloud, testing becomes even more critical for your applications to be reliable. Learn to master automated, functional testing using the open source tools, Selenium, Windmill, and twill. The techniques covered in this article work on Google App Engine, blogging software, or your own home grown application.