Quality Assurance
Protractor – Automated Testing with Angular
Critical errors that become evident only in live operation constitute a major financial risk, and they also mean negative publicity both for the product and the companies involved. This is why testing is a fundamental, integral part of modern software development.
Recipes for Test Automation (Part 2) – Data Salad
The test data always pose a particular challenge in manual testing, and even more so with respect to test automation.
Recipes for Test Automation (Part 1) – Soup
A colleague recently approached me and asked me whether I know a recipe for good test automation. I told him that, just like with a good soup, it takes more than a recipe: The kitchen appliances, ingredients, and the cook are important as well.
“Heisenberg’s” Test Uncertainty with Automated Test Tools
Critical errors that become evident only in live operation mean negative publicity for both the product and the companies involved. To prevent this, test automation is a fundamental, integral part of modern software development. However, the technical implementation with test automation tools gives rise to problems that we need to be aware of.
The Independence of the Testers in an Agile Team
Whenever I talk about testing in agile teams, and I emphasize that the testers and developers work closely together, I am asked the same question: What about the independence of the testers?
The Life of a Tester
Sometimes, during your daily project routine, you ask yourself, what am I doing here, and do the others on the team know what I’m actually doing?
The Agile Test Manager – An Oxymoron? (Part 3)
Do we still need a test manager in an agile development process like scrum? And if not, who was supposed to assume his responsibilities in the sprint?
The Agile Test Manager – An Oxymoron? (Part 2)
Do we still need a test manager in an agile development process like scrum? And if not, who was supposed to assume his responsibilities in the sprint?
The Agile Test Manager – An Oxymoron? (Part 1)
Some time ago, a colleague of mine asked me whether we still needed a test manager in an agile development process like scrum. My first response was no because the Agile Manifesto and the scrum framework only know three roles: product owner, development team, and scrum master. But on second thought, I wondered who among the scrum team was supposed to assume the test manager’s responsibilities in and around the sprint?
Test-driven Development
Usually traditional testing is only done when there is something to test. What is the benefit of the test-driven development method for agile projects?