unit testing | TechWell

unit testing

Developer performing unit testing A Simple Rule of Thumb for Unit Testing

There's a simple rule for the minimum values testers should explore: “none, one, some”—or, how the software behaves if you send it nothing, one thing, or some set greater than one. It's not comprehensive, but it gives a good feel for how the feature works at the moment. Developers can also use this in unit testing.

Justin Rohrman's picture
Justin Rohrman
Jeff Langr Cultivating Quality Code: A Slack Takeover with Jeff Langr

Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Jeff Langr, author of a number of books about software, hosted this Slack takeover and discussed the pros of unit testing versus end-to-end testing, code reviews, and test-driven development.

Cristy Bird's picture
Cristy Bird
Developers discussing a software product's quality 2 Ways Developers Can Contribute to Better Testing

Testers need to find important information about product quality and present it in a way that can be acted upon. As the people building the software, developers are in a great position to observe the product. By monitoring the test environment and conducting unit testing, they can help inform about product quality.

Justin Rohrman's picture
Justin Rohrman
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
Hand putting together units of Legos Engaging Developers in Unit Testing

Unit testing is key for driving early defect identification, but organizations and teams continue to be challenged when it comes to designing and implementing unit tests. Realizing a culture of sound unit testing is often more a leadership challenge than a developer one. Here's how to instill a culture of unit testing.

Michael Sowers's picture
Michael Sowers
Pipelines, photo by Bernard Hermant Testing Your DevOps Is Just as Important as Testing Your Software

Many DevOps engineers fail to test their automation code in the same way they test the software they deploy. It's crucial for software to have tests, and this should apply to infrastructure-as-code software too, if we plan to change and improve this code with no worries about breaking automation in our DevOps pipeline.

Alan Crouch's picture
Alan Crouch
Unit Testing? Consider Taking a Rain Check

Unit testing is a great way to verify software at an early stage and to ensure that modified functions are still working as specified. However, unit tests are not a magic wand. Rather than making such a big testing effort, consider taking "rain checks" for certain tests.

Hans Buwalda's picture
Hans Buwalda
Scalability of Tests—A Matrix

Hans Buwalda highlights the scalability of unit, functional, and exploratory tests—the three kinds of tests used to verify functionality. Since many automation tools and strategies traditionally focus on functional testing, Hans provides some strategies to make functional testing more manageable.

Hans Buwalda's picture
Hans Buwalda