unit-testing - w3toppers.com

How to start working with GTest and CMake

The solution involved putting the gtest source directory as a subdirectory of your project. I’ve included the working CMakeLists.txt below if it is helpful to anyone. cmake_minimum_required(VERSION 2.6) project(basic_test) ################################ # GTest ################################ ADD_SUBDIRECTORY (gtest-1.6.0) enable_testing() include_directories(${gtest_SOURCE_DIR}/include ${gtest_SOURCE_DIR}) ################################ # Unit Tests ################################ # Add test cpp file add_executable( runUnitTests testgtest.cpp ) # Link test … Read more

Unit test naming best practices [closed]

Update (Jul 2021) It’s been quite a while since my original answer (almost 12 years) and best practices have been changing a lot during this time. So I feel inclined to update my own answer and offer different naming strategies to the readers. Many comments and answers point out that the naming strategy I propose … Read more

Mock functions in Go

What is unit testing? [closed]

Unit testing is, roughly speaking, testing bits of your code in isolation with test code. The immediate advantages that come to mind are: Running the tests becomes automate-able and repeatable You can test at a much more granular level than point-and-click testing via a GUI Note that if your test code writes to a file, … Read more

NUnit vs. MbUnit vs. MSTest vs. xUnit.net [closed]

I know this is an old thread, but I thought I’d post a vote for xUnit.NET. While most of the other testing frameworks mentioned are all pretty much the same, xUnit.NET has taken a pretty unique, modern, and flexible approach to unit testing. It changes terminology, so you no longer define TestFixtures and Tests…you specify … Read more

What is unit testing and how do you do it? [duplicate]

What is unit testing? Unit testing simply verifies that individual units of code (mostly functions) work as expected. Usually you write the test cases yourself, but some can be automatically generated. The output from a test can be as simple as a console output, to a “green light” in a GUI such as NUnit, or … Read more

Should one test internal implementation, or only test public behaviour?

The answer is very simple: you are describing functional testing, which is an important part of software QA. Testing internal implementation is unit-testing, which is another part of software QA with a different goal. That’s why you are feeling that people disagree with your approach. Functional testing is important to validate that the system or … Read more

What is the purpose of mock objects?

Since you say you are new to unit testing and asked for mock objects in “layman’s terms”, I’ll try a layman’s example. Unit Testing Imagine unit testing for this system: cook <- waiter <- customer It’s generally easy to envision testing a low-level component like the cook: cook <- test driver The test driver simply … Read more

Should unit tests be written for getter and setters?

I would say no. @Will said you should aim for 100% code coverage, but in my opinion that’s a dangerous distraction. You can write unit tests that have 100% coverage, and yet test absolutely nothing. Unit tests are there to test the behaviour of your code, in an expressive and meaningful way, and getters/setters are … Read more

How to run only one unit test class using Gradle

To run a single test class Airborn’s answer is good. With using some command line options, which found here, you can simply do something like this. gradle test –tests org.gradle.SomeTest.someSpecificFeature gradle test –tests *SomeTest.someSpecificFeature gradle test –tests *SomeSpecificTest gradle test –tests all.in.specific.package* gradle test –tests *IntegTest gradle test –tests *IntegTest*ui* gradle test –tests *IntegTest.singleMethod gradle … Read more