test techniques | TechWell

test techniques

Test pyramid 5 Reasons You Should Have More Unit Tests

The test pyramid is a valuable visual in agile. In particular, it argues that unit tests should make up the majority of tests, and while agile teams recite this principle, it is often not clear why it is so important. Here are five reasons unit tests should make up the majority of tests written for an application.

Jeffery Payne's picture
Jeffery Payne
Rope under stress fraying apart A New Approach to Load Testing with Browser-Level Users

Since the inception of load testing, the approach has been mostly the same: simulate the traffic of an application by creating load at the API level. But there have been market shifts that make load testing with browser-level users more feasible—allowing us to test with real load and measure true user performance.

Kevin Dunne's picture
Kevin Dunne
Gauges on a car's instrument dashboard, photo by Dominik Stötter 5 Strategies for Better, More Reliable Load Testing

As you test your system’s performance, what happens when it fails to meet your requirements? With these five strategies, you can simulate realistic load testing of your system, mitigate your risks, and create reliable, continuous, automated performance testing for a better and more efficient end-user experience.

Israel Rogoza's picture
Israel Rogoza
Image showing a digital wrench as a test tool Lessons Learned in Testing a UI Test Automation Tool

How do you test a tool to be used for automated testing? If a tool executes an automated test that generates keyboard and mouse events to replay user actions, can the test emulate user input and control another instance of the tool to automatically record and play another test? Here's how you test the test tool.

Denis Markovtsev's picture
Denis Markovtsev
Sinking boat Guaranteed Methods to Ruin Your Test Automation

After working to develop the test automation patterns used by experienced practitioners to solve common test automation issues, Seretta Gamba started to consider what can ruin a test automation effort instead. Here she shares two sure-fire methods that can destroy your test automation. Steer clear of these examples!

Seretta Gamba's picture
Seretta Gamba
Developers and testers having a conversation about behavior-driven development A Conversation about Testing within BDD

People using behavior-driven development (BDD) say conversation is the most important part of the process. They use a “given-when-then” format to describe the current state, an action that is supposed to occur, and what results to expect. But if that structure isn't working for your team, don't restrain discussion.

Justin Rohrman's picture
Justin Rohrman
AI traffic light Testing Artificial Intelligence: How Low Can You Go?

Artificial intelligence (AI) is propelling to the forefront once more. With the growing importance of AI comes the question: How do I test it? AI systems do not necessarily behave predictably. This means that traditional test cases of the form "do this, expect that" are not always sufficient.

Hans Buwalda's picture
Hans Buwalda
Four checkboxes with two of them checked Questions to Ask during Test Selection for Automated Tests

We use test design techniques to answer the questions “What do I need to test?” and “What tests should I perform?” We try to ensure test coverage during test automation too, except that choosing poorly creates slower builds and unreliable information about product quality. Here are some guidelines for test selection.

Justin Rohrman's picture
Justin Rohrman