test execution | TechWell

test execution

Tester logging an issue in a defect-tracking system Don’t Let “Try It Now” Impede Your Test Initiative

Sometimes environmentally based issues arise that impede your ability to access or test the software. Rather than addressing the problem methodically, as with defects, testers often attempt to solve it on their own. Here's why entering the problem into the defect-tracking database is a more efficient way to solve it.

Richard Estra's picture
Richard Estra
Left arrow painted on a wall 5 Ways to Shift Performance Testing Left

Performance testing is often a barrier to accelerating software delivery. Because you need a production-like environment, performance testing often waits until the entire application is complete. But you shouldn't wait until then to get started. You can begin testing earlier to reduce rework and address issues sooner.

Jeffery Payne's picture
Jeffery Payne
"No code" typed inside brackets Merging New Codeless Test Automation with Your Existing Code-Based Test Scripts

Adopting a codeless solution can be an amazing boost to quality, productivity, and tester career growth, but in most organizations, such test suites will have to be merged into existing code-based test scripts. To succeed, developers, testers, and management all should consider the differences between the two options.

Eran Kinsbruner's picture
Eran Kinsbruner
Janna Loeffler Is Testing Just Looking for Bugs? A Slack Takeover with Janna Loeffler

Thought leaders from the software community are taking over the TechWell Hub for a day to answer questions and engage in conversations. Janna Loeffler, a software engineer with a variety of quality and testing roles, hosted this Slack takeover, which led to discussions about tools, automation, and what testing is.

Owen Gotimer's picture
Owen Gotimer
Test plan written out Rebuilding Your Test Strategy

If testing is taking awhile and a lot of bugs are getting into production, it's a good idea to review your entire test strategy. Spend some time understanding the current process and what testing is happening through the dev process—not what is outlined in a process wiki, but the work that actually happens.

Justin Rohrman's picture
Justin Rohrman
People applauding near a medal saying "2018" Top 10 TechWell Insights Stories of 2018

Many teams are embracing new practices, and several of last year's most-read stories reflect that, with topics such as AI, DevOps, and continuous testing. But it looks like lots of teams also want to get back to basics, because guides to tried-and-true agile and testing methods also ranked high. Check out the roundup.

Beth Romanik's picture
Beth Romanik
Magnifying glass looking at the words "Software testing" on a computer screen Making Testing Visible

Most testing work is invisible—something that happens inside your head and leaves no artifacts behind. This generally leaves testers feeling like no one understands what they do all day. Here are some ideas for collaborating with your coworkers so they can see—and start to understand—your testing work.

Justin Rohrman's picture
Justin Rohrman
Drawing of a digital brain made of circuitboards How AI Is Transforming Software Testing

At our modern pace of rapid software delivery, manual testing alone is simply inadequate. AI will soon be a necessity to keep pace and equip QA and test teams with augmented efficiencies. But don't fear the future; just like automation tools already have, AI is going to complement—not replace—your testing efforts.

Raj Subramanian's picture
Raj Subramanian