testing | TechWell

testing

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
View from above of five coworkers fist-bumping over their computers 4 Ways to Increase Software Quality and Decrease Test Time

Software testers are continually under pressure to test faster without sacrificing quality. By taking the perspective that quality is the responsibility of the entire team, not just the testers, shorter test cycles with higher quality software are possible. Here are four ways the whole team can improve releases.

Richard Estra's picture
Richard Estra
Image of a person's face made out of code Designing a Smart QA Strategy

With increasingly complex and sophisticated technologies being used in testing, quality has to become a smart activity. A smart QA strategy is both about building smart models and making smart choices. We must keep in mind the balance between manual and automated solutions and which are needed to accomplish our goals.

Mukesh Sharma's picture
Mukesh Sharma
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
Hand holding a camera lens focusing on faraway mountains Agile and DevOps Bring the Focus Back on Quality

As companies move to agile and DevOps, silos are coming down and there is more interaction and collaboration among teams. Quality is also becoming everyone's responsibility for the entire software development lifecycle. Quality is more than just testing: Consider a quality value stream along the overall value chain.

Michael Sowers's picture
Michael Sowers
Row of bottles lined up, photo by Andrew Seaman The Cost of Software Testing

Testing is regarded as the number one bottleneck in the software delivery process. Most people simply conclude that developers are value centers, and testers are cost centers. But developers' work also brings cost, and—more importantly—testers' work also brings value. It's time to reframe our thinking about testing.

Ingo Philipp's picture
Ingo Philipp
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
Icon showing the phases of continuous testing Continuous Testing Is Not Automation

Many people confuse continuous testing with test automation. That makes sense, because you cannot do continuous testing without automated tests. But it is much more. Continuous testing has a higher-level maturity that could require a totally different way of working—but it also gives a faster path to production.

Adam Auerbach's picture
Adam Auerbach