The Latest

Java Performance Testing with Your Own Tool[article]

Performance testing is an important procedure to be carried out before approving any software product for shipment. You’ve probably heard some horror stories from senior colleagues about a time when the system was shipped without any performance testing. So now, it is an essential part of your testing. There are various tools for implementing performance testing for non-GUI middleware systems, but there are times we don't have the liberty to choose from an existing set of tools for performance testing

5 Steps to Get to Test Driven Development [article]

TDD is a software development approach in which a test is written before writing the code. When TDD is properly set up, it can bring numerous advantages and become a cost-saver, providing true value to the business. When TDD is not properly set up or without understanding how it should be used, it can be a waste of time and money. Quality comes not from inspection but from the improvement of the production process

Evgeny Tkachenko's picture Evgeny Tkachenko
Most Common QA Myths[article]

One of my mentors, whom I admire, once told me, "Quality is not only QA's responsibility; everyone- from development engineers to technical architects, to product managers need to share the responsibilities. In a QA role, if you want to be successful, you have to know the right amount of information from everyone and always ask questions." I took my mentor's advice very seriously. 

Dilruba Malik's picture Dilruba Malik
Man looking at mountains through binoculars The Art of Exploratory Testing[article]

Some people assume that exploratory testing is a task with low-effort thinking, where the tester simply goes through the application and sees what comes up. While we shouldn't discount doing just that, because sometimes it does reveal some interesting bugs, there are techniques and patterns that testers can follow when exploring an application. Let's look at a two-step process to use in exploratory testing.

Sanjugtha Shoba's picture Sanjugtha Shoba
Tester looking at theories posted on a wall Wish-List Ideas for Software Testing Research[article]

There are many established ideas for ways to test software, but the industry is changing every day, and there's plenty of room for growth of new ideas—or challenges to traditional ones. Here are three ideas for "wish-list" research to conduct in order to shake up some of the conventional notions you may have about software testing techniques.

Michael Stahl's picture Michael Stahl
A Primer on Continuous Testing[article]

Continuous testing shortens feedback loops through automated testing that occurs throughout the development lifecycle—hence "continuous." Testing and QA become the responsibility of everyone working on the software, not just testers. Let's look at some proven practices from organizations that have used continuous testing effectively to realize tangible benefits.

Vasudevan Swaminathan's picture Vasudevan Swaminathan
Testing as a Craft: A Conversation with Greg Paskal[interview]
Podcast

Greg Paskal, evangelist in testing sciences and lead author for RealWorldTestAutomation.com, chats with TechWell community manager Owen Gotimer about testing as a craft, choosing the right test automation tools, and current testing trends around the world.

Owen Gotimer's picture Owen Gotimer
Colorful gears 5 Reasons Enterprise Test Automation Is So Challenging[article]

Most organizations understand that test automation is essential for modern application delivery processes. They’re just not sure how to make it a reality in an enterprise environment without exorbitant overhead and massive disruption. Enterprise organizations typically achieve small victories, but the process ultimately decays due to challenges in five main areas. Understanding these challenges will help us overcome them.

Wolfgang Platz's picture Wolfgang Platz
Automation Software Is Production Software[article]

When it comes to testing, there tends to be a differentiation between “production software” and everything else. But our ideas and principles about testing software are true for all software, not merely the code that will run in front of customers or the APIs that make things happen. Any software built for a purpose needs to be tested against that purpose, including the software running our test automation.

Peter Walen's picture Peter Walen
Computer showing fire on the screen Strengthening System Resilience with Chaos Engineering[article]

Testing continuous technological change can seem like chaos. There are many challenges that need to be managed, such as unavailability of power, excessive temperature, incorrect configuration, unexpected behavior of services, network downtime, and processing slowdown in production. By deliberately engineering chaos, we’ll be able to discover many of our systems’ weaknesses before our users do.

Hand placing block in row of blocks with left arrows Fitting In Regression Testing by Shifting QA Left[article]

Fixing a bug in one area of the software may break something in another area. To detect whether defects have been introduced, we need to perform regression testing—executing certain test cases again to see whether a change has affected other existing features. But how do you make time for another testing cycle prior to every production release? You need to get QA involved earlier in the software development lifecycle.

Shuja Naqvi's picture Shuja Naqvi
Talia Nassi Testing in Production: A Conversation with Talia Nassi[interview]
Podcast

Talia Nassi, developer advocate at Split Software, chats with TechWell community manager Owen Gotimer about the fears, myths, and benefits of testing in production and how to get your stakeholders on board. Continue the conversation with Talia (@Talia Nassi) and Owen (@owen) on the TechWell Hub (hub.techwell.com)!

Owen Gotimer's picture Owen Gotimer
Smartphone showing the word "ERROR" False Errors in Test Tooling[article]

Traditional GUI automation is linear; it follows a set of steps. The first time you run it, it can't add any value, as the feature isn't done until the automation runs. Once test automation runs a second time, it effectively becomes change detection. This leads to a large number of "failures" that are not actually failures. Whether they are false positives or false negatives, we need a way to fix the automation tooling.

Matthew Heusser's picture Matthew Heusser
Person parasailing 5 Steps to Getting Started with Risk-Based Testing[article]

Risk-based testing is an approach to testing that helps us handle our limited resources. It’s also a valid model for years to come because it focuses testing resources where they can have the most impact—regardless of whether limitations are due to budget, tight schedules, or even the uncertainty of an unexpected situation like COVID-19. Here are some practical tips, examples, and steps you can use to adopt risk-based testing.

Shawn Jaques's picture Shawn Jaques
Bug on a leaf How to Respond to Retest Requests without a Clear Bug Fix[article]

After finding and reporting a bug, a tester may get this response from a developer: "Please rerun the test on the latest version of the code and check if the bug still reproduces." This seems like a rational request; just as a change can cause a bug to appear, it can also fix a bug. But is following up the responsibility of the tester or the developer? And if the bug is no longer there, how do you classify and close it?

Michael Stahl's picture Michael Stahl

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.