Versions Compared

Version Old Version 7 New Version 8
Changes made by

Jess Douglas Muir (Deactivated)

Ryan Dancy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Here’s an example of a unit test from the tests for our GPIO library. It sets up the pin, asserts that it was set up correctly, then ensures checking the state returns the value it was initially set to (notice that in the init settings the state is HIGH).

Info

Our testing framework is Unity (not the game engine). Every test file has three parts:

  • A setup_test function, which is run before every test. It initializes all the libraries the tests need.

  • A teardown_test function, which is run after every test. Usually it’s empty, but it still has to be there.

  • Test functions, which is any function that starts with test_. They can use assertions like TEST_ASSERT_EQUAL to test conditions.

  • Hardware testing: running the project on the actual hardware. Also, creating validation projects that test specific parts of the hardware, but not necessarily implementing the logic. We call these smoke tests. More documentation can be found here: Smoke Tests .

  • Integration testing: Wiring a bunch of boards together and making sure they play nice. Hopefully by this stage our code is well tested and the logic is bullet proof, but there’s always something that comes up here.

...