In the classic movie, Monty Python and the Holy Grail, King Arthur has an encounter with “Dennis” regarding their form of government. At one point, Dennis exclaims “Ah, now we see the violence inherent in the system!” While there will be no violence, I hope to contrast the benefits of Tosca (elaborated in a separate…
The Tosca Difference
When I first joined Tricentis, Tosca had the reputation for being an excellent test automation solution, but I honestly assumed that under the covers, it was pretty much the same as all the other test automation tools I had seen over the years. I was wrong. Tosca is truly unique…but I have found it can…
Why do Test Automation projects fail?
Test automation initiatives can fail for various reasons, often due to a combination of factors. Some of the common reasons for test automation failures include: To avoid these pitfalls and ensure the success of test automation initiatives, organizations should invest in planning, training, and collaboration. They should also set realistic expectations, choose the right tools…
The Impact of Test Coverage
Several factors can lead to less than 100% test coverage with manual testing teams: While it’s desirable to achieve 100% test coverage, in practice, it’s often not feasible, especially with manual testing. Teams should focus on prioritizing high-risk areas and critical functionality to ensure that the most important aspects of the application are tested thoroughly….
Quantifying the Benefits of Test Automation
Quantifying the benefits of test automation in hard dollars can be challenging, but it is possible by considering various factors that contribute to cost savings and improved efficiency. Here are some key factors to consider when calculating the financial benefits of test automation: To calculate the overall financial benefits of test automation, add up the…
Test Team Composition
The ideal distribution of responsibilities within a testing team depends on various factors, including the size of the team, the complexity of the application being tested, the development methodology, and the overall testing strategy. There is no one-size-fits-all answer to the percentage of team members creating test cases versus executing tests. However, a typical approach…
Test Case Creation
The time it takes to document a test case can vary significantly depending on several factors, such as the complexity of the test case, the experience of the test case writer, the level of detail required, and the specific domain or application being tested. On average, it can take anywhere from 30 minutes to 2…
What CIOs Really Think About Software Testing
Jennifer starts off by asking the audience (of testers), “How many of you think your CIOs care about testing?” About 5 people replied in the affirmative. She goes on to ensure the audience that they do. A key takeaway here is that speed and agility is important, not necessarily cost. “I don’t care about the…
The CIO’s Perspective
While this may be a bit dated (2017), I found this panel discussion to be quite informative, especially regarding how the participants articulate the CIO’s concerns when it comes to software testing. This link provides access to the full transcript and you can click on the image above to see the video on YouTube. The…
Types of testing
On Reddit today, someone asked “What is the best kind of testing?” That’s a loaded question. I replied: There are layers of software testing (unit, component, system, end to end, user acceptance, etc) and various types (manual, guided, exploratory, crowd sourced, scripted automation, no-code automation). Where you start depends on the scope of the application…