Page MenuHome

Testing C API (how to go about it)
Closed, ResolvedPublicDESIGN

Description

Currently most of the tests in source/tests rely on Python scripts, this is fine, but there are areas of our C api we probably wont expose to python and we still want to be able to test them.

eg: https://developer.blender.org/diffusion/B/browse/master/source/blender/blenlib/BLI_path_util.h

An example of where testing would be useful is for checking UNC paths, (ms-windows \\network\paths). don't break other use cases when the patch is applied. [0].

This task is to evaluate how best to manage testing C API (Mostly BLI and BKE functions)

[0] https://developer.blender.org/D298

Note, exactly how C/C++ tests are compiled and setup should be done with some care, since it should work across many different modules.

Event Timeline

Campbell Barton (campbellbarton) raised the priority of this task from to 90.
Campbell Barton (campbellbarton) updated the task description. (Show Details)
Campbell Barton (campbellbarton) added a project: Restricted Project.
Campbell Barton (campbellbarton) edited a custom field.
Bastien Montagne (mont29) lowered the priority of this task from 90 to Normal.Apr 11 2014, 6:06 PM

Note that Sergey and Campbell have made a start at this using the gtest (GoogleTest) testing framework that was already being used in Blender to for unit tests in the external libmv.

Initial tests in the gtest-testing branch, in source/tests/blenlib_tests

Aaron Carlisle (Blendify) closed this task as Resolved.Feb 13 2020, 1:34 AM
Aaron Carlisle (Blendify) claimed this task.