Your team has just finished a major refactor of a service and all your unit and integration tests pass. Nice work! But you are not done just yet. Now you need to make extra sure that you didn’t break anything and that there are not any lurking bugs that you have not caught yet. It’s time to put Diffy to work.
Root Cause Analysis (RCA) is an approach used in software quality to identify the root causes of bugs or issues and address them instead of treating the symptoms. In this article, Mush Honda explains that RCA can be applied to end user feedback as well as software defects during software testing and provides some tips on how to apply RCA.
Writing maintainable test automation code is as important as being able to design good customer-facing systems, yet very few teams do it well. If you think that your test automation often costs too much, takes too long and does not give you the return on investment you expected, this is a talk for you. Learn five key design patterns that will make the pain go away and allow you to get the most out of your automated tests.
The Belgium Testing Days (BTD) is a conference dedicated to software testing that takes place in Brussels. The BTD event aims to be the best software testing conference with leading experts on Testing, QA, DevOps, Mobile Testing, Test Automation and Continuous Delivery.
The debate is always active in the software testing community about the usage of manual or automated testing. In this article, Art Trevethan explains that both have their value. He guides you on how to choose the test items to automate and proposes an approach to integrate test automation smoothly in your test plans without abandoning the benefits of manual testing.
Test-Driven Development (TDD) is a game changer for developers, but Behavior-Driven Development (BDD) is a game changer for the whole team. More than just a testing technique, BDD is both a collaboration and a verification tool—and a vital step on the road to continuous delivery.
James Christie argues that software testing standards are produced by bodies with a commercial interest in seeing them adopted. He analyses the economic forces behind the creation of standards. They should be viewed as optional methods that companies can buy or reject as they see fit. Selling them as standards distorts the market by creating the impression amongst senior managers, lawyers and regulators that there is no valid, responsible alternative.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates