UnitTest EmbeddedC

This is an example of doing a UnitTest project using googltest.

Build status	Systems / Compilers
	Linux (gcc7)
	Windows (Visual Studio 2017)

Info

CMake is the chosen build system using ctest.

VSCode is the chosen development IDE.

Library used

• googltest for unit test system. (as submodule)

Project Structure

UnitTestEmbeddedC/
├── CMakeLists.txt
├── README.md
├── doc
├── .vscode
├── googletest
│   ├── CMakeLists.txt
│   └── ...
├── src
│   ├── Array.c
│   ├── Array.h
│   └── ...
│── test
│   ├── UnitTestFiles
│   │   └── ...
│   ├── MockFiles
│   │   └── ...
│   ├── Main.cpp
│   └── ...

Directory structure:

• src : Directory for source code under test.
• test : Directory for test code, including unit test and mock files.
• doc : Directory for documents.
• .vscode: Directory for VSCode configuration.
• googletest: Directory for submodule googletest.
• CMakeLists.txt: CMake file.
• README.md: This file.

How to start

Clone the repository recursively

  mkdir my_project
  cd my_project
  git clone https://github.com/ProgmaticProgrammer/UnitTestEmbeddedC.git --recursive --progress -v

Open the repository in VSCode

• Open a Developer Command Prompt (VS 2017)

• Open the VSCode from the Command Prompt

  cd my_project\UnitTestEmbeddedC
  code .

Build/Run/Test in VSCode

• Choose the cmake configure to confgure cmake

• Choose the cmake build to build vs2017 target

• Choose the ctest run to configure/build/test as one go

  

Develop

Click Explorer or (Ctrl+Shift+E) to browser source code

Click Source Control or (Ctrl+Shift+G) to browser source control

Click Run or (Ctrl+Shift+D) to debug source code

If GoogleTest Adapter is installed, unittests can be viewed in a tree graph as well

Todos

• Integrate with Circleci
• Make it running under GNU/Linux

References

• https://cognitivewaves.wordpress.com/cmake-and-visual-studio/#visual-studio-to-cmake-mapping

License

MIT