In software test automation like in programming, the creation phase is always the easier. Then the application is delivered and starts his “maintenance” life, sometimes being tagged with the infamous “legacy” adjective. During this period the code evolve and so should be maintained. This is the same for the code that automate the software testing activity. In his article, Gojko Adzic proposes five ways to reduce the cost of large test suites.
Atlassian JIRA is one of the most popular tool for Agile project management. Many add-ons exist for test case management with this tool. In this article, Vladimir Belorusets presents a set of requirements for an efficient test case management process in JIRA that should help you select the best solution for the software testing needs of your organization.
Most of us have had to deal with red builds blocking our testing or have been told to test on flaky environments where half the issues you find would ‘never happen in production’. As a tester, I used to think this wasn’t my problem. What happens though when a thinking tester decides this is her problem and wants to be part of the solution?
One of the famous concept in software testing is the testing pyramid defined by Martin Fowler that is based on strong unit tests and has less user interface (UI) tests at the top. Sometimes organizations have a different view of software tests and the pyramid is not a pyramid anymore. In this blog post, Fabio Pereira discusses the case where the pyramid looks like a cupcake.
This video shows how Selenium, integrated into a FitNesse framework can extend an organization’s ability to create more automated test cases without the need for Selenium programming while expanding the ability to test across all popular browsers.