bartvdbraak/blender
1
0
Fork 4
Code Issues 4 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity
5f7f6b65f3
blender/tests/python/CMakeLists.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

994 lines
29 KiB
CMake
Raw Normal View History

License Headers: Set copyright to "Blender Authors", add AUTHORS Listing the "Blender Foundation" as copyright holder implied the Blender Foundation holds copyright to files which may include work from many developers. While keeping copyright on headers makes sense for isolated libraries, Blender's own code may be refactored or moved between files in a way that makes the per file copyright holders less meaningful. Copyright references to the "Blender Foundation" have been replaced with "Blender Authors", with the exception of `./extern/` since these this contains libraries which are more isolated, any changed to license headers there can be handled on a case-by-case basis. Some directories in `./intern/` have also been excluded: - `./intern/cycles/` it's own `AUTHORS` file is planned. - `./intern/opensubdiv/`. An "AUTHORS" file has been added, using the chromium projects authors file as a template. Design task: #110784 Ref !110783.
2023-08-15 14:20:26 +00:00
# SPDX-FileCopyrightText: 2011-2023 Blender Authors
License headers: use SPDX-FileCopyrightText for CMake files
2023-06-14 12:49:59 +00:00
#
File headers: SPDX License migration Use a shorter/simpler license convention, stops the header taking so much space. Follow the SPDX license specification: https://spdx.org/licenses - C/C++/objc/objc++ - Python - Shell Scripts - CMake, GNUmakefile While most of the source tree has been included - `./extern/` was left out. - `./intern/cycles` & `./intern/atomic` are also excluded because they use different header conventions. doc/license/SPDX-license-identifiers.txt has been added to list SPDX all used identifiers. See P2788 for the script that automated these edits. Reviewed By: brecht, mont29, sergey Ref D14069
2022-02-10 22:07:11 +00:00
# SPDX-License-Identifier: GPL-2.0-or-later
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
# Use '--write-blend=/tmp/test.blend' to view output
CTest: disable bl_run_operators.py, fun for finding crashes, takes a long time
2014-03-26 20:30:22 +00:00
# Some tests are interesting but take too long to run
# and don't give deterministic results
set(USE_EXPERIMENTAL_TESTS FALSE)
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
set(TEST_SRC_DIR ${CMAKE_SOURCE_DIR}/../lib/tests)
Accepting patch D5357: Modifiers and operators automated testing. Patch from Habib Gahbiche (zazizizou) moves the "run operator and compare mesh to a golden" paradigm used in bevel and boolean tests into a general framework that separates the test specs from the blend files. Then adds some other operator and modifier tests using the new framework. Diff D5357.id20724.diff was applied. New .blend files, modifiers.blend and operators.blend are needed in the tests/modeling svn directory; those were separately committed.
2020-01-13 12:11:45 +00:00
set(TEST_PYTHON_DIR ${CMAKE_SOURCE_DIR}/tests/python)
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
set(TEST_OUT_DIR ${CMAKE_BINARY_DIR}/tests)
update x3d test md5s for recent changes, also ensure directory is created or export tests fail.
2011-03-16 12:06:12 +00:00
# ugh, any better way to do this on testing only?
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
file(MAKE_DIRECTORY ${TEST_OUT_DIR})
file(MAKE_DIRECTORY ${TEST_OUT_DIR}/io_tests)
Cleanup: Deduplicate some code in new blenfile io/linking tests.
2020-02-14 10:02:22 +00:00
file(MAKE_DIRECTORY ${TEST_OUT_DIR}/blendfile_io)
update x3d test md5s for recent changes, also ensure directory is created or export tests fail.
2011-03-16 12:06:12 +00:00
CMake: add missing headers, use space before comments
2019-10-28 14:32:33 +00:00
# if(NOT IS_DIRECTORY ${TEST_SRC_DIR})
# message(FATAL_ERROR "CMake test directory not found!")
# endif()
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
# Run Blender command with parameters.
Fix broken add_python_test after recent changes
2019-08-02 13:19:59 +00:00
function(add_blender_test testname)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_test(
Fix broken add_python_test after recent changes
2019-08-02 13:19:59 +00:00
NAME ${testname}
Tests: run tests from install path Blender can only be run correctly from the install path since it requires Python scripts, dynamic libraries and other files to be present. By default the install path is the same as the build path, so it works anyway. But on the buildbot it isn't. There was a workaround but it failed on Windows and macOS. Now tests run from the install path. Detecting that path for ctest is more complicated than I would like, but I couldn't find a better solution. Ref T69541.
2019-09-07 12:03:39 +00:00
COMMAND "${TEST_BLENDER_EXE}" ${TEST_BLENDER_EXE_PARAMS} ${ARGN}
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
)
Tests: don't fail on leaks detected by leak sanitizer These often happen in external libraries that we can't fix. The leaks are still printed in the logs.
2019-08-02 12:29:53 +00:00
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
# Don't fail tests on leaks since these often happen in external libraries that we can't fix.
set(_lsan_options "exitcode=0")
if(DEFINED ENV{LSAN_OPTIONS})
set(_lsan_options "${_lsan_options}:$ENV{LSAN_OPTIONS}")
endif()
set_tests_properties(${testname} PROPERTIES ENVIRONMENT "LSAN_OPTIONS=${_lsan_options}")
unset(_lsan_options)
Build: make running executables as part of build/tests work with shared libs Ensure the environment is set up for blender_test, idiff and oslc so that they can find the required shared libraries. Also deduplicate add_bundled_libraries() between Linux and macOS. Includes contributions by Ray Molenkamp and Brecht Van Lommel. Ref T99618
2022-12-05 22:05:25 +00:00
if(PLATFORM_ENV_INSTALL)
set_tests_properties(${testname} PROPERTIES ENVIRONMENT "${PLATFORM_ENV_INSTALL}")
endif()
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
endfunction()
# Run Python script outside Blender.
function(add_python_test testname testscript)
Tests: use explicit Python to run unit tests CentOS on the buildbot still runs Python 3.6, which is also used for the unit tests. This means that the tests can't use language features that are available to Blender itself. And testing with a different version of Python than will be used by the actual code seems like a bad idea to me. This commit adds `TEST_PYTHON_EXECUTABLE` as advanced CMake option. This will allow us to set a specific Python executable when we need it. When not set, a platform-specific default will be used: - On Windows, the `python….exe` from the installation directory. This is just like before this patch, except that this patch adds the overridability. - On macOS/Linux, the `${PYTHON_EXECUTABLE}` as found by CMake. Every platform should now have a value (configured by the user or detected by CMake) for `TEST_PYTHON_EXE`, so there is no need to allow running without. This also removes the need to have some Python files marked as executable. If `TEST_PYTHON_EXE` is not user-configured, and thus the above default is used, a status message is logged by CMake. I've seen this a lot in other projects, and I like that it shows which values are auto-detected. However, it's not common in Blender, so if we want we can either remove it now, or remove it after the buildbot has been set up correctly. Differential Revision: https://developer.blender.org/D7395 Reviewed by: campbellbarton, mont29, sergey
2020-04-10 08:35:17 +00:00
if(NOT TEST_PYTHON_EXE)
message(FATAL_ERROR "No Python configured for running tests, set TEST_PYTHON_EXE.")
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
endif()
Fix broken add_python_test after recent changes
2019-08-02 13:19:59 +00:00
Tests: use explicit Python to run unit tests CentOS on the buildbot still runs Python 3.6, which is also used for the unit tests. This means that the tests can't use language features that are available to Blender itself. And testing with a different version of Python than will be used by the actual code seems like a bad idea to me. This commit adds `TEST_PYTHON_EXECUTABLE` as advanced CMake option. This will allow us to set a specific Python executable when we need it. When not set, a platform-specific default will be used: - On Windows, the `python….exe` from the installation directory. This is just like before this patch, except that this patch adds the overridability. - On macOS/Linux, the `${PYTHON_EXECUTABLE}` as found by CMake. Every platform should now have a value (configured by the user or detected by CMake) for `TEST_PYTHON_EXE`, so there is no need to allow running without. This also removes the need to have some Python files marked as executable. If `TEST_PYTHON_EXE` is not user-configured, and thus the above default is used, a status message is logged by CMake. I've seen this a lot in other projects, and I like that it shows which values are auto-detected. However, it's not common in Blender, so if we want we can either remove it now, or remove it after the buildbot has been set up correctly. Differential Revision: https://developer.blender.org/D7395 Reviewed by: campbellbarton, mont29, sergey
2020-04-10 08:35:17 +00:00
add_test(
NAME ${testname}
Tests: don't create byte-code cache when calling Python from SVN Creating `__pycache__` directories in SVN's lib/ directory can cause updating SVN to fail. Add the -B flag when TEST_PYTHON_EXE from LIBDIR is used so so Python doesn't generate this cache.
2022-11-03 00:48:47 +00:00
COMMAND ${TEST_PYTHON_EXE} ${TEST_PYTHON_EXE_EXTRA_ARGS} ${testscript} ${ARGN}
Build: make running executables as part of build/tests work with shared libs Ensure the environment is set up for blender_test, idiff and oslc so that they can find the required shared libraries. Also deduplicate add_bundled_libraries() between Linux and macOS. Includes contributions by Ray Molenkamp and Brecht Van Lommel. Ref T99618
2022-12-05 22:05:25 +00:00
WORKING_DIRECTORY $<TARGET_FILE_DIR:blender>
Tests: use explicit Python to run unit tests CentOS on the buildbot still runs Python 3.6, which is also used for the unit tests. This means that the tests can't use language features that are available to Blender itself. And testing with a different version of Python than will be used by the actual code seems like a bad idea to me. This commit adds `TEST_PYTHON_EXECUTABLE` as advanced CMake option. This will allow us to set a specific Python executable when we need it. When not set, a platform-specific default will be used: - On Windows, the `python….exe` from the installation directory. This is just like before this patch, except that this patch adds the overridability. - On macOS/Linux, the `${PYTHON_EXECUTABLE}` as found by CMake. Every platform should now have a value (configured by the user or detected by CMake) for `TEST_PYTHON_EXE`, so there is no need to allow running without. This also removes the need to have some Python files marked as executable. If `TEST_PYTHON_EXE` is not user-configured, and thus the above default is used, a status message is logged by CMake. I've seen this a lot in other projects, and I like that it shows which values are auto-detected. However, it's not common in Blender, so if we want we can either remove it now, or remove it after the buildbot has been set up correctly. Differential Revision: https://developer.blender.org/D7395 Reviewed by: campbellbarton, mont29, sergey
2020-04-10 08:35:17 +00:00
)
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
set(_lsan_options "exitcode=0")
if(DEFINED ENV{LSAN_OPTIONS})
set(_lsan_options "${_lsan_options}:$ENV{LSAN_OPTIONS}")
endif()
set_tests_properties(${testname} PROPERTIES ENVIRONMENT "LSAN_OPTIONS=${_lsan_options}")
unset(_lsan_options)
Build: make running executables as part of build/tests work with shared libs Ensure the environment is set up for blender_test, idiff and oslc so that they can find the required shared libraries. Also deduplicate add_bundled_libraries() between Linux and macOS. Includes contributions by Ray Molenkamp and Brecht Van Lommel. Ref T99618
2022-12-05 22:05:25 +00:00
if(PLATFORM_ENV_INSTALL)
set_tests_properties(${testname} PROPERTIES ENVIRONMENT "${PLATFORM_ENV_INSTALL}")
endif()
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
endfunction()
2 tests for ctest. - script_load_addons: loads and onloads all addons, error if any cant be enabled or disabled. - script_load_modules: loads all blenders modules, error if any modules raise an exception or if any modules in the scripts dir are not tested (except for presets and templates). These are useful because lazy module loading means a module can have an error which isnt raised until the tools used. This gives a way to detect basic errors that used to happen on startup or when enabling the addon.
2011-03-18 23:58:13 +00:00
# ------------------------------------------------------------------------------
# GENERAL PYTHON CORRECTNESS TESTS
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_load_keymap
add ctest for keyconfig_utils to check for missing items.
2013-02-26 04:48:16 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_keymap_completeness.py
)
Tests: add script_validate_keymap This checks the generated key-map data matches the result of re-exporting and re-importing. This shows up various inconsistencies, including: - Unused keymaps. - Unknown/unused data in the keymap. - Event arguments that don't make sense. - Event values that don't match the event type (tweak direction on keyboard event for example).
2021-03-14 08:06:48 +00:00
add_blender_test(
script_validate_keymap
--python ${CMAKE_CURRENT_LIST_DIR}/bl_keymap_validate.py
-- --relaxed # Disable minor things that should not cause tests to break.
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_load_addons
2 tests for ctest. - script_load_addons: loads and onloads all addons, error if any cant be enabled or disabled. - script_load_modules: loads all blenders modules, error if any modules raise an exception or if any modules in the scripts dir are not tested (except for presets and templates). These are useful because lazy module loading means a module can have an error which isnt raised until the tools used. This gives a way to detect basic errors that used to happen on startup or when enabling the addon.
2011-03-18 23:58:13 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_load_addons.py
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_load_modules
2 tests for ctest. - script_load_addons: loads and onloads all addons, error if any cant be enabled or disabled. - script_load_modules: loads all blenders modules, error if any modules raise an exception or if any modules in the scripts dir are not tested (except for presets and templates). These are useful because lazy module loading means a module can have an error which isnt raised until the tools used. This gives a way to detect basic errors that used to happen on startup or when enabling the addon.
2011-03-18 23:58:13 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_load_py_modules.py
)
Fix T68243: Python sqlite module not working on macOS
2020-02-11 09:15:31 +00:00
add_blender_test(
script_bundled_modules
Tests: test availability of new bundled Python libraries Differential Revision: https://developer.blender.org/D16733
2023-01-09 12:15:20 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_bundled_modules.py -- --inside-blender
Fix T68243: Python sqlite module not working on macOS
2020-02-11 09:15:31 +00:00
)
Added CTest to run most operators in background mode under various conditions to see if any crash. used this to find quite a many errors already.
2011-03-22 14:09:07 +00:00
# test running operators doesn't segfault under various conditions
CTest: disable bl_run_operators.py, fun for finding crashes, takes a long time
2014-03-26 20:30:22 +00:00
if(USE_EXPERIMENTAL_TESTS)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_run_operators
CTest: disable bl_run_operators.py, fun for finding crashes, takes a long time
2014-03-26 20:30:22 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_run_operators.py
)
endif()
Added CTest to run most operators in background mode under various conditions to see if any crash. used this to find quite a many errors already.
2011-03-22 14:09:07 +00:00
Add test scripts to ctest & rename
2015-09-24 10:49:44 +00:00
# ------------------------------------------------------------------------------
# PY API TESTS
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_pyapi_bpy_path
Add test scripts to ctest & rename
2015-09-24 10:49:44 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_bpy_path.py
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_pyapi_bpy_utils_units
Add test scripts to ctest & rename
2015-09-24 10:49:44 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_bpy_utils_units.py
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_pyapi_mathutils
unit test for mathutils python module from Andrew Hale, runs in CTest too
2011-12-20 01:49:24 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_mathutils.py
)
Tests: add test to ensure restricted py-driver execution is working Add internal function (only used for testing at the moment) `_bpy._driver_secure_code_test`. Add test `script_pyapi_bpy_driver_secure_eval` to serves two purposes: - Ensure expressions that should be insecure remain so when upgrading Python or making any changes in this area. - Ensure new versions of Python don't introduce new byte-codes that prevent existing expressions from being executed (happened when upgrading from 3.7, see [0]). [0]: dfa52017638abdf59791e5588c439d3a558a191d
2022-07-12 06:05:15 +00:00
add_blender_test(
script_pyapi_bpy_driver_secure_eval
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_bpy_driver_secure_eval.py
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_pyapi_idprop
PyAPI: ID Property tests
2017-03-18 16:37:22 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_idprop.py
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
script_pyapi_idprop_datablock
Datablock ID Properties The absence of datablock properties "will certainly be resolved soon as the need for them is becoming obvious" said the [[http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.67/Python_Nodes|Python Nodes release notes]]. So this patch allows Python scripts to create ID Properties which reference datablocks. This functionality is implemented for `PointerProperty` and now such properties can be created with Python. In addition to the standard update callback, `PointerProperty` can have a `poll` callback (standard RNA) which is useful for search menus. For details see the test included in this patch. Original author: @artfunkel Alexander (Blend4Web Team) Reviewers: brecht, artfunkel, mont29, campbellbarton Reviewed By: mont29, campbellbarton Subscribers: jta, sergey, campbellbarton, wisaac, poseidon4o, mont29, homyachetser, Evgeny_Rodygin, AlexKowel, yurikovelenov, fjuhec, sharlybg, cardboard, duarteframos, blueprintrandom, a.romanov, BYOB, disnel, aditiapratama, bliblubli, dfelinto, lukastoenne Maniphest Tasks: T37754 Differential Revision: https://developer.blender.org/D113
2017-04-13 09:30:03 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_idprop_datablock.py
)
Python: add foreach_get and foreach_set methods to pyrna_prop_array This allows fast access to various arrays in the Python API. Most notably, `image.pixels` can be accessed much more efficiently now. **Benchmark** Below are the results of a benchmark that compares different ways to set/get all pixel values. I do the tests on 2048x2048 rgba images. The benchmark tests the following dimensions: - Byte vs. float per color channel - Python list vs. numpy array containing floats - `foreach_set` (new) vs. `image.pixels = ...` (old) ``` Pixel amount: 2048 * 2048 = 4.194.304 Byte buffer size: 16.8 mb Float buffer size: 67.1 mb Set pixel colors: byte - new - list: 271 ms byte - new - buffer: 29 ms byte - old - list: 350 ms byte - old - buffer: 2900 ms float - new - list: 249 ms float - new - buffer: 8 ms float - old - list: 330 ms float - old - buffer: 2880 ms Get pixel colors: byte - list: 128 ms byte - buffer: 9 ms float - list: 125 ms float - buffer: 8 ms ``` **Observations** The best set and get speed can be achieved with buffers and a float image, at the cost of higher memory consumption. Furthermore, using buffers when using `pixels = ...` is incredibly slow, because it is not optimized. Optimizing this is possible, but might not be trivial (there were multiple attempts afaik). Float images are faster due to overhead introduced by the api for byte images. If I profiled it correctly, a lot of time is spend in the `[0, 1] -> {0, ..., 255}` conversion. The functions doing that conversion is `unit_float_to_uchar_clamp`. While I have an idea on how it can be optimized, I do not know if it can be done without changing its functionality slightly. Performance wise the best solution would be to not do this conversion at all and accept byte input from the api user directly, but that seems to be a more involved task as well. Differential Revision: https://developer.blender.org/D7053 Reviewers: JacquesLucke, mont29
2020-03-13 11:57:12 +00:00
add_blender_test(
script_pyapi_prop_array
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_prop_array.py
)
Text Editor: Get/Set region text API Add the ability to get/set the selected text. **Calling the new methods:** - `bpy.data.texts["Text"].region_as_string()` - `bpy.data.texts["Text"].region_from_string("Replacement")`
2022-04-07 04:32:21 +00:00
add_blender_test(
script_pyapi_text
--python ${CMAKE_CURRENT_LIST_DIR}/bl_pyapi_text.py
)
ID Management: Add some basic tests regarding name handling. Those tests are here mostsly to ensure ID name management is working as expected (the code ensuring we never have two ilocal data-blocks of the same type with the same name in a .blend file). Note: Currently fails in some cases, fixes are incoming. Note: Ideally this would be in C, but we already have too many tests linking the whole Blender and its libraries, this is becoming a real pain to link debug + ASAN + tests build these days... So until we find a better way to handle those dependencies, sticking to simple python scripts.
2019-12-18 15:09:47 +00:00
# ------------------------------------------------------------------------------
# DATA MANAGEMENT TESTS
add_blender_test(
id_management
--python ${CMAKE_CURRENT_LIST_DIR}/bl_id_management.py
)
Added bevel regression test to tests. Goes with companion files bevel_regression.blend and mesh_ops_test.py just added to svn lib/tests/modeling. Also changed the blender executable path for Apple case: needed either 'Debug' or 'Release' in the path. I chose 'Debug', because not sure how to add otherwise. At any rate, what was currently there didn't work at all.
2014-02-02 18:29:08 +00:00
# ------------------------------------------------------------------------------
Add initial, very basic save/open & library linking blendfile tests. Do not do much for now, but would have been enough to catch the crash introduced the other day in linking code...
2020-02-13 16:48:00 +00:00
# BLEND IO & LINKING
add_blender_test(
blendfile_io
--python ${CMAKE_CURRENT_LIST_DIR}/bl_blendfile_io.py --
--output-dir ${TEST_OUT_DIR}/blendfile_io/
)
Tests: Add test to open all blendfiles in current `/lib/tests/` repository. This is fairly brute force and rough, but there are quite a few old files in there, helps a bit with versioning and readfile code testing. Note: Five files are currently excluded since failing in debug builds at least, most of the time for memleaks issues. The two other 'errors' may also not be actual issues, but this needs to be investigated further. Also, in the future, when time allows, it may be better to generate a set of dedicated testing files, with as many official releases versions as possible? Re. #112649.
2023-10-04 09:28:43 +00:00
add_blender_test(
blendfile_versioning
--log "*blendfile*"
--debug-memory
--debug
--python ${CMAKE_CURRENT_LIST_DIR}/bl_blendfile_versioning.py --
--src-test-dir ${TEST_SRC_DIR}/
)
Add initial, very basic save/open & library linking blendfile tests. Do not do much for now, but would have been enough to catch the crash introduced the other day in linking code...
2020-02-13 16:48:00 +00:00
add_blender_test(
blendfile_liblink
Fix missing output dir for blendfile_liblink test.
2020-02-18 08:52:29 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_blendfile_liblink.py --
--output-dir ${TEST_OUT_DIR}/blendfile_io/
Add initial, very basic save/open & library linking blendfile tests. Do not do much for now, but would have been enough to catch the crash introduced the other day in linking code...
2020-02-13 16:48:00 +00:00
)
LibraryOverrides: Initial Test Case. Added a first test case for review. This will be the base for future test cases. The current API is sufficient for what is expected for such a low level API. One concern is that you need to trigger a save in order to update the library overrides structure. Not expected from TD/Dev point of view. Test cases are very important when implementing restrictive mode as it is a second evaluation mode that has impact on the (current) permissive mode. Reviewed By: Sebastián Barschkis, Bastien Montagne Differential Revision: https://developer.blender.org/D10747
2021-03-22 10:33:48 +00:00
add_blender_test(
blendfile_library_overrides
--python ${CMAKE_CURRENT_LIST_DIR}/bl_blendfile_library_overrides.py --
--output-dir ${TEST_OUT_DIR}/blendfile_io/
Unittest: Add very basic 'old file loading' test. Use existing `lib/tests/libraries_and_linking/library_test_scene.blend` essentially as 'file loads without error' test. Also does very basic proxy -> liboverrides conversion check. This test could be extended a lot, but just opening this file already allowed to identify three bugs in current 3.6/main code, and an issue in an upcoming refactor of the readfile code...
2023-05-26 16:37:22 +00:00
--test-dir "${TEST_SRC_DIR}/libraries_and_linking"
LibraryOverrides: Initial Test Case. Added a first test case for review. This will be the base for future test cases. The current API is sufficient for what is expected for such a low level API. One concern is that you need to trigger a save in order to update the library overrides structure. Not expected from TD/Dev point of view. Test cases are very important when implementing restrictive mode as it is a second evaluation mode that has impact on the (current) permissive mode. Reviewed By: Sebastián Barschkis, Bastien Montagne Differential Revision: https://developer.blender.org/D10747
2021-03-22 10:33:48 +00:00
)
Add initial, very basic save/open & library linking blendfile tests. Do not do much for now, but would have been enough to catch the crash introduced the other day in linking code...
2020-02-13 16:48:00 +00:00
# ------------------------------------------------------------------------------
Added bevel regression test to tests. Goes with companion files bevel_regression.blend and mesh_ops_test.py just added to svn lib/tests/modeling. Also changed the blender executable path for Apple case: needed either 'Debug' or 'Release' in the path. I chose 'Debug', because not sure how to add otherwise. At any rate, what was currently there didn't work at all.
2014-02-02 18:29:08 +00:00
# MODELING TESTS
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
bmesh_bevel
Added bevel regression test to tests. Goes with companion files bevel_regression.blend and mesh_ops_test.py just added to svn lib/tests/modeling. Also changed the blender executable path for Apple case: needed either 'Debug' or 'Release' in the path. I chose 'Debug', because not sure how to add otherwise. At any rate, what was currently there didn't work at all.
2014-02-02 18:29:08 +00:00
${TEST_SRC_DIR}/modeling/bevel_regression.blend
Accepting patch D5357: Modifiers and operators automated testing. Patch from Habib Gahbiche (zazizizou) moves the "run operator and compare mesh to a golden" paradigm used in bevel and boolean tests into a general framework that separates the test specs from the blend files. Then adds some other operator and modifier tests using the new framework. Diff D5357.id20724.diff was applied. New .blend files, modifiers.blend and operators.blend are needed in the tests/modeling svn directory; those were separately committed.
2020-01-13 12:11:45 +00:00
--python ${TEST_PYTHON_DIR}/bevel_operator.py
--
--run-all-tests
Added bevel regression test to tests. Goes with companion files bevel_regression.blend and mesh_ops_test.py just added to svn lib/tests/modeling. Also changed the blender executable path for Apple case: needed either 'Debug' or 'Release' in the path. I chose 'Debug', because not sure how to add otherwise. At any rate, what was currently there didn't work at all.
2014-02-02 18:29:08 +00:00
)
Re-enable modifer and bmesh_boolean tests. These were disabled in the newboolean merge commit. This commit renables them, using the original 'FAST' solver so that the result objects need not change. A TODO to add more tests using the 'EXACT' solver, though most functionality there is now covered by unit gtests.
2020-08-30 12:31:40 +00:00
add_blender_test(
bmesh_boolean
${TEST_SRC_DIR}/modeling/bool_regression.blend
--python ${TEST_PYTHON_DIR}/boolean_operator.py
--
--run-all-tests
)
Add boolean regression test.
2018-02-12 12:23:23 +00:00
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
bmesh_split_faces
Cleanup: cmake indentation, missing include
2017-06-08 20:45:21 +00:00
${TEST_SRC_DIR}/modeling/split_faces_test.blend
--python-text run_tests
Register test for mesh.split_faces()
2017-02-16 14:36:00 +00:00
)
Add regression tests for curve conversion to mesh This adds a basic set of tests for curve sampling and bevel generation. At the moment there are basic test cases for bevels, caps, and the filling of 2D curves, but more tests can be added in the future. Curves are actually converted to "DispLists" for displaying them in the viewport, so it's much simpler to rely on the mesh conversion operator instead of building a new test framework for another data structure. Differential Revision: https://developer.blender.org/D9958
2020-12-30 19:12:29 +00:00
add_blender_test(
curve_to_mesh
${TEST_SRC_DIR}/modeling/curve_to_mesh.blend
--python ${TEST_PYTHON_DIR}/curve_to_mesh.py
--
--run-all-tests
)
Add automated ctest for complex merge in Array modifier. See also T50851.
2017-05-26 19:57:45 +00:00
# ------------------------------------------------------------------------------
# MODIFIERS TESTS
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
object_modifier_array
Cleanup: cmake indentation, missing include
2017-06-08 20:45:21 +00:00
${TEST_SRC_DIR}/modifier_stack/array_test.blend
Fix: test object_modifier_array is passing when it shouldn't. From D5253.
2019-07-31 16:29:58 +00:00
--python-text run_tests.py
Add automated ctest for complex merge in Array modifier. See also T50851.
2017-05-26 19:57:45 +00:00
)
Re-enable modifer and bmesh_boolean tests. These were disabled in the newboolean merge commit. This commit renables them, using the original 'FAST' solver so that the result objects need not change. A TODO to add more tests using the 'EXACT' solver, though most functionality there is now covered by unit gtests.
2020-08-30 12:31:40 +00:00
add_blender_test(
modifiers
${TEST_SRC_DIR}/modeling/modifiers.blend
--python ${TEST_PYTHON_DIR}/modifiers.py
--
--run-all-tests
)
Accepting patch D5357: Modifiers and operators automated testing. Patch from Habib Gahbiche (zazizizou) moves the "run operator and compare mesh to a golden" paradigm used in bevel and boolean tests into a general framework that separates the test specs from the blend files. Then adds some other operator and modifier tests using the new framework. Diff D5357.id20724.diff was applied. New .blend files, modifiers.blend and operators.blend are needed in the tests/modeling svn directory; those were separately committed.
2020-01-13 12:11:45 +00:00
Tests: add physics tests cloth and softybody This uses the same framework as automated modifier tests. It adds a physics modifier, bakes and compares vertex coordinates on the end frame. Differential Revision: https://developer.blender.org/D7017
2020-04-27 14:47:07 +00:00
add_blender_test(
physics_cloth
${TEST_SRC_DIR}/physics/cloth_test.blend
--python ${TEST_PYTHON_DIR}/physics_cloth.py
--
--run-all-tests
)
add_blender_test(
physics_softbody
${TEST_SRC_DIR}/physics/softbody_test.blend
--python ${TEST_PYTHON_DIR}/physics_softbody.py
--
--run-all-tests
)
Updated and extended Regression Testing frameworks (Gsoc 2020) This revision contains the following changes- - Updated the existing testing framework for Modifiers for Regression Testing. - Tests for Physics modifiers and remaining Generate and Deform modifiers are added. - The existing `ModifierSpec` is updated with backward compatibility to support Physics Modifiers. - Now there is support for frame number and giving nested parameters for attributes. - Some Deform modifiers required Object Operators, e.g. "Bind" in Mesh Deform, so a new class was added to support that functionality. - A separate class for holding Particles System, they are tested by converting all the particles to mesh and joining it to the mesh they were added. - Updated the format to add tests for Bevel, Boolean and Operators as well. Reviewed By: zazizizou, mont29, campbellbarton Differential Revision: https://developer.blender.org/D8507
2020-12-17 15:14:55 +00:00
add_blender_test(
physics_dynamic_paint
${TEST_SRC_DIR}/physics/dynamic_paint_test.blend
--python ${TEST_PYTHON_DIR}/physics_dynamic_paint.py
--
--run-all-tests
)
add_blender_test(
deform_modifiers
${TEST_SRC_DIR}/modeling/deform_modifiers.blend
--python ${TEST_PYTHON_DIR}/deform_modifiers.py
--
--run-all-tests
)
Fix ocean modifier giving different result on Arm than x86 And re-enable the test on macOS Arm. Ref T78710
2021-05-18 12:02:41 +00:00
if(WITH_MOD_OCEANSIM)
add_blender_test(
physics_ocean
${TEST_SRC_DIR}/physics/ocean_test.blend
--python ${TEST_PYTHON_DIR}/physics_ocean.py
--
--run-all-tests
)
Tests: skip unit test if built without ocean sim modifier Disable the Ocean Sim test when building with `WITH_MOD_OCEANSIM=OFF`.
2021-01-12 12:49:40 +00:00
endif()
Updated and extended Regression Testing frameworks (Gsoc 2020) This revision contains the following changes- - Updated the existing testing framework for Modifiers for Regression Testing. - Tests for Physics modifiers and remaining Generate and Deform modifiers are added. - The existing `ModifierSpec` is updated with backward compatibility to support Physics Modifiers. - Now there is support for frame number and giving nested parameters for attributes. - Some Deform modifiers required Object Operators, e.g. "Bind" in Mesh Deform, so a new class was added to support that functionality. - A separate class for holding Particles System, they are tested by converting all the particles to mesh and joining it to the mesh they were added. - Updated the format to add tests for Bevel, Boolean and Operators as well. Reviewed By: zazizizou, mont29, campbellbarton Differential Revision: https://developer.blender.org/D8507
2020-12-17 15:14:55 +00:00
add_blender_test(
physics_particle_system
${TEST_SRC_DIR}/physics/physics_particle_test.blend
--python ${TEST_PYTHON_DIR}/physics_particle_system.py
--
--run-all-tests
)
Enabled Physics Particle Instance test
2021-01-05 10:46:08 +00:00
add_blender_test(
physics_particle_instance
${TEST_SRC_DIR}/physics/physics_particle_instance.blend
--python ${TEST_PYTHON_DIR}/physics_particle_instance.py
--
--run-all-tests
)
Updated and extended Regression Testing frameworks (Gsoc 2020) This revision contains the following changes- - Updated the existing testing framework for Modifiers for Regression Testing. - Tests for Physics modifiers and remaining Generate and Deform modifiers are added. - The existing `ModifierSpec` is updated with backward compatibility to support Physics Modifiers. - Now there is support for frame number and giving nested parameters for attributes. - Some Deform modifiers required Object Operators, e.g. "Bind" in Mesh Deform, so a new class was added to support that functionality. - A separate class for holding Particles System, they are tested by converting all the particles to mesh and joining it to the mesh they were added. - Updated the format to add tests for Bevel, Boolean and Operators as well. Reviewed By: zazizizou, mont29, campbellbarton Differential Revision: https://developer.blender.org/D8507
2020-12-17 15:14:55 +00:00
Start of unit test framework for constraints Currently this only tests the Child Of constraint. My aim is to cover constraints with tests before they are refactored/altered. No functional changes.
2020-02-25 11:16:34 +00:00
add_blender_test(
constraints
--python ${CMAKE_CURRENT_LIST_DIR}/bl_constraints.py
--
--testdir "${TEST_SRC_DIR}/constraints"
)
Accepting patch D5357: Modifiers and operators automated testing. Patch from Habib Gahbiche (zazizizou) moves the "run operator and compare mesh to a golden" paradigm used in bevel and boolean tests into a general framework that separates the test specs from the blend files. Then adds some other operator and modifier tests using the new framework. Diff D5357.id20724.diff was applied. New .blend files, modifiers.blend and operators.blend are needed in the tests/modeling svn directory; those were separately committed.
2020-01-13 12:11:45 +00:00
# ------------------------------------------------------------------------------
# OPERATORS TESTS
add_blender_test(
operators
${TEST_SRC_DIR}/modeling/operators.blend
--python ${TEST_PYTHON_DIR}/operators.py
--
--run-all-tests
)
Fix T75881: Animation, limitation of Bézier Handles Relax limits of FCurve Bézier handles during evaluation. FCurve handles can be scaled down to avoid the curve looping backward in time. This scaling was done correctly but over-carefully, posing unnecessary limitations on the possible slope of FCurves. This commit changes the scaling approach such that the FCurve can become near-vertical. Bump Blender's subversion from 291.0.1 to 291.0.2 to ensure that older animation files are correctly updated. Reviewed By: sybren Differential Revision: https://developer.blender.org/D8752
2020-09-15 08:41:08 +00:00
# ------------------------------------------------------------------------------
# ANIMATION TESTS
add_blender_test(
bl_animation_fcurves
--python ${CMAKE_CURRENT_LIST_DIR}/bl_animation_fcurves.py
--
--testdir "${TEST_SRC_DIR}/animation"
)
Fix T81541: Symmetrize Transform Constraint, Y rotational axis unexpected results The case where Y rotation is mapped to Y rotation was not handled. This is now fixed. Also added an automated test to make sure that the symmetrize operator functions as intended. Reviewed By: Sybren Differential Revision: http://developer.blender.org/D9214
2022-02-04 13:19:44 +00:00
add_blender_test(
bl_rigging_symmetrize
--python ${CMAKE_CURRENT_LIST_DIR}/bl_rigging_symmetrize.py
--
--testdir "${TEST_SRC_DIR}/animation"
)
Nodes: Panels integration with blend files and UI Part 3/3 of #109135, #110272 Switch to new node group interfaces and deprecate old DNA and API. This completes support for panels in node drawing and in node group interface declarations in particular. The new node group interface DNA and RNA code has been added in parts 1 and 2 (#110885, #110952) but has not be enabled yet. This commit completes the integration by * enabling the new RNA API * using the new API in UI * read/write new interfaces from blend files * add versioning for backward compatibility * add forward-compatible writing code to reconstruct old interfaces All places accessing node group interface declarations should now be using the new API. A runtime cache has been added that allows simple linear access to socket inputs and outputs even when a panel hierarchy is used. Old DNA has been deprecated and should only be accessed for versioning (inputs/outputs renamed to inputs_legacy/outputs_legacy to catch errors). Versioning code ensures both backward and forward compatibility of existing files. The API for old interfaces is removed. The new API is very similar but is defined on the `ntree.interface` instead of the `ntree` directly. Breaking change notifications and detailed instructions for migrating will be added. A python test has been added for the node group API functions. This includes new functionality such as creating panels and moving items between different levels. This patch does not yet contain panel representations in the modifier UI. This has been tested in a separate branch and will be added with a later PR (#108565). Pull Request: https://projects.blender.org/blender/blender/pulls/111348
2023-08-30 10:37:21 +00:00
# ------------------------------------------------------------------------------
Nodes: New test for node group versioning This simply loads a blend file and tests that the node group interface as well as a node group instance have all the expected sockets and default values. Pull Request: https://projects.blender.org/blender/blender/pulls/111800
2023-09-05 12:27:20 +00:00
# NODE GROUP TESTS
add_blender_test(
bl_node_group_compat
--python ${CMAKE_CURRENT_LIST_DIR}/bl_node_group_compat.py
--
--testdir "${TEST_SRC_DIR}/node_group"
)
Nodes: Panels integration with blend files and UI Part 3/3 of #109135, #110272 Switch to new node group interfaces and deprecate old DNA and API. This completes support for panels in node drawing and in node group interface declarations in particular. The new node group interface DNA and RNA code has been added in parts 1 and 2 (#110885, #110952) but has not be enabled yet. This commit completes the integration by * enabling the new RNA API * using the new API in UI * read/write new interfaces from blend files * add versioning for backward compatibility * add forward-compatible writing code to reconstruct old interfaces All places accessing node group interface declarations should now be using the new API. A runtime cache has been added that allows simple linear access to socket inputs and outputs even when a panel hierarchy is used. Old DNA has been deprecated and should only be accessed for versioning (inputs/outputs renamed to inputs_legacy/outputs_legacy to catch errors). Versioning code ensures both backward and forward compatibility of existing files. The API for old interfaces is removed. The new API is very similar but is defined on the `ntree.interface` instead of the `ntree` directly. Breaking change notifications and detailed instructions for migrating will be added. A python test has been added for the node group API functions. This includes new functionality such as creating panels and moving items between different levels. This patch does not yet contain panel representations in the modifier UI. This has been tested in a separate branch and will be added with a later PR (#108565). Pull Request: https://projects.blender.org/blender/blender/pulls/111348
2023-08-30 10:37:21 +00:00
add_blender_test(
bl_node_group_interface
--python ${CMAKE_CURRENT_LIST_DIR}/bl_node_group_interface.py
--
--testdir "${TEST_SRC_DIR}/node_group"
)
2 tests for ctest. - script_load_addons: loads and onloads all addons, error if any cant be enabled or disabled. - script_load_modules: loads all blenders modules, error if any modules raise an exception or if any modules in the scripts dir are not tested (except for presets and templates). These are useful because lazy module loading means a module can have an error which isnt raised until the tools used. This gives a way to detect basic errors that used to happen on startup or when enabling the addon.
2011-03-18 23:58:13 +00:00
# ------------------------------------------------------------------------------
# IO TESTS
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
# STL Import tests
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
# disabled until updated & working
if(FALSE)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_stl_cube
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_mesh.stl\(filepath='${TEST_SRC_DIR}/io_tests/stl/cube.stl'\)
--md5=8ceb5bb7e1cb5f4342fa1669988c66b4 --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_stl_cube.blend
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_stl_conrod
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_mesh.stl\(filepath='${TEST_SRC_DIR}/io_tests/stl/conrod.stl'\)
--md5=690a4b8eb9002dcd8631c5a575ea7348 --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_stl_conrod.blend
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_stl_knot_max_simplified
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_mesh.stl\(filepath='${TEST_SRC_DIR}/io_tests/stl/knot_max_simplified.stl'\)
--md5=baf82803f45a84ec4ddbad9cef57dd3e --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_stl_knot_max_simplified.blend
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
)
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
endif()
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
# STL Export
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
# disabled until updated & working
if(FALSE)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_stl_cube_all_data
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/cube_all_data.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_mesh.stl\(filepath='${TEST_OUT_DIR}/io_tests/export_stl_cube_all_data.stl'\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_stl_cube_all_data.stl
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=64cb97c0cabb015e1c3f76369835075a --md5_method=FILE
)
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_stl_suzanne_all_data
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/suzanne_all_data.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_mesh.stl\(filepath='${TEST_OUT_DIR}/io_tests/export_stl_suzanne_all_data.stl'\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_stl_suzanne_all_data.stl
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=e9b23c97c139ad64961c635105bb9192 --md5_method=FILE
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_stl_vertices # lame, add a better one
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/vertices.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_mesh.stl\(filepath='${TEST_OUT_DIR}/io_tests/export_stl_vertices.stl'\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_stl_vertices.stl
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=3fd3c877e573beeebc782532cc005820 --md5_method=FILE
)
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
endif()
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
# X3D Import
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
# disabled until updated & working
if(FALSE)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_x3d_cube
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_scene.x3d\(filepath='${TEST_SRC_DIR}/io_tests/x3d/color_cube.x3d'\)
update checksums for x3d tests
2011-07-01 13:39:35 +00:00
--md5=3fae9be004199c145941cd3f9f80ad7b --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_x3d_cube.blend
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_x3d_teapot
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_scene.x3d\(filepath='${TEST_SRC_DIR}/io_tests/x3d/teapot.x3d'\)
update checksums for x3d tests
2011-07-01 13:39:35 +00:00
--md5=8ee196c71947dce4199d55698501691e --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_x3d_teapot.blend
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_x3d_suzanne_material
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_scene.x3d\(filepath='${TEST_SRC_DIR}/io_tests/x3d/suzanne_material.x3d'\)
update checksums for x3d tests
2011-07-01 13:39:35 +00:00
--md5=3edea1353257d8b5a5f071942f417be6 --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_x3d_suzanne_material.blend
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
# X3D Export
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_x3d_cube
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/all_quads.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.x3d\(filepath='${TEST_OUT_DIR}/io_tests/export_x3d_cube.x3d',use_selection=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_x3d_cube.x3d
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=05312d278fe41da33560fdfb9bdb268f --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_x3d_nurbs
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/nurbs.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.x3d\(filepath='${TEST_OUT_DIR}/io_tests/export_x3d_nurbs.x3d',use_selection=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_x3d_nurbs.x3d
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=4286d4a2aa507ef78b22ddcbdcc88481 --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_x3d_all_objects
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_scene/all_objects.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.x3d\(filepath='${TEST_OUT_DIR}/io_tests/export_x3d_all_objects.x3d',use_selection=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_x3d_all_objects.x3d
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=f5f9fa4c5619a0eeab66685aafd2f7f0 --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
endif()
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
# 3DS Import
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
# disabled until updated & working
if(FALSE)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_3ds_cube
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_scene.autodesk_3ds\(filepath='${TEST_SRC_DIR}/io_tests/3ds/cube.3ds'\)
--md5=cb5a45c35a343c3f5beca2a918472951 --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_3ds_cube.blend
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_3ds_hierarchy_lara
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_scene.autodesk_3ds\(filepath='${TEST_SRC_DIR}/io_tests/3ds/hierarchy_lara.3ds'\)
update ctest md5sums for import/export to match changes to the scripts, also some minor formatting change for bpy_props.c
2011-06-07 08:47:33 +00:00
--md5=766c873d9fdb5f190e43796cfbae63b6 --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_3ds_hierarchy_lara.blend
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
import_3ds_hierarchy_greek_trireme
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
--run={'FINISHED'}&bpy.ops.import_scene.autodesk_3ds\(filepath='${TEST_SRC_DIR}/io_tests/3ds/hierarchy_greek_trireme.3ds'\)
update ctest md5sums for import/export to match changes to the scripts, also some minor formatting change for bpy_props.c
2011-06-07 08:47:33 +00:00
--md5=b62ee30101e8999cb91ef4f8a8760056 --md5_method=SCENE
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--write-blend=${TEST_OUT_DIR}/io_tests/import_3ds_hierarchy_greek_trireme.blend
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
endif()
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
# 3DS Export
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
# disabled until updated & working
if(FALSE)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_3ds_cube
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/all_quads.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.autodesk_3ds\(filepath='${TEST_OUT_DIR}/io_tests/export_3ds_cube.3ds',use_selection=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_3ds_cube.3ds
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=a31f5071b6c6dc7445b9099cdc7f63b3 --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_3ds_nurbs
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/nurbs.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.autodesk_3ds\(filepath='${TEST_OUT_DIR}/io_tests/export_3ds_nurbs.3ds',use_selection=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_3ds_nurbs.3ds
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=5bdd21be3c80d814fbc83cb25edb08c2 --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_3ds_all_objects
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_scene/all_objects.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.autodesk_3ds\(filepath='${TEST_OUT_DIR}/io_tests/export_3ds_all_objects.3ds',use_selection=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_3ds_all_objects.3ds
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=68447761ab0ca38e1e22e7c177ed48a8 --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
endif()
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
PLY and STL importer tests.
2011-01-21 10:49:39 +00:00
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
# FBX Export
# 'use_metadata=False' for reliable md5's
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
# disabled until updated & working
if(FALSE)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_fbx_cube
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/all_quads.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.fbx\(filepath='${TEST_OUT_DIR}/io_tests/export_fbx_cube.fbx',use_selection=False,use_metadata=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_fbx_cube.fbx
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=59a35577462f95f9a0b4e6035226ce9b --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_fbx_nurbs
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_geometry/nurbs.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.fbx\(filepath='${TEST_OUT_DIR}/io_tests/export_fbx_nurbs.fbx',use_selection=False,use_metadata=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_fbx_nurbs.fbx
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=d31875f18f613fa0c3b16e978f87f6f8 --md5_method=FILE
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
)
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
export_fbx_all_objects
import/export automated testing using CMake's CTest Will need to write full docs on this on the wiki. basic info. - 21 tests, OBJ/3DS/X3D/FBX, 3 tests per format import export. STL, PLY, BVH are TODO. - uses files in ../lib/tests (checkout separate) - run with CMake Makefiles "make test" or "ctest" - currently checks against basic MD5 hash on scene import and file MD5 hash on export (realize this wont work predictably on binary formats *TODO*). - currently uses a generic script for all tests with arguments to specify command to run, expected output, testing method, files to check against etc. Has already proved useful, found a number of bugs in import export and some in blender too.
2011-01-21 00:06:30 +00:00
${TEST_SRC_DIR}/io_tests/blend_scene/all_objects.blend
--python ${CMAKE_CURRENT_LIST_DIR}/bl_test.py --
Tests: put output of IO tests in subdirectory
2019-06-25 17:52:37 +00:00
--run={'FINISHED'}&bpy.ops.export_scene.fbx\(filepath='${TEST_OUT_DIR}/io_tests/export_fbx_all_objects.fbx',use_selection=False,use_metadata=False\)
--md5_source=${TEST_OUT_DIR}/io_tests/export_fbx_all_objects.fbx
add 3 PLY and STL export tests.
2011-10-10 00:29:23 +00:00
--md5=b35eb2a9d0e73762ecae2278c25a38ac --md5_method=FILE
SVN maintenance.
2011-01-21 00:33:37 +00:00
)
Tests: Disable failing import/export tests for until they're fixed
2015-02-10 14:29:18 +00:00
endif()
CTests: Add render tests for Cycles The idea is to use the set of really small images from the lib folder and run Cycles render on them comparing render output to reference images in the tests repository. For sure same thing could become more generic for BI or Freestyle render engines. Thanks Campbell for review and code tweaks!
2015-01-22 10:53:49 +00:00
Beginning of automated SVG regression test This commit contains the CTest integration. Starting with the very simple tests for the recent fixes in the io_corve_svg addon which were related on closing path. The idea is to use same framework as what we use for render tests to make it easily visible what aspect of SVG changed or broke. In order to achieve this both .blend and .svg files are used. The .svg file defines the exact subject of test, and the .blend file defines camera, and possibly material. The longer term idea is to have a number of atomic tests for a specific SVG features to help isolating problematic areas, as well as a more comprehensive tests to perform QA.
2022-10-11 13:02:40 +00:00
# SVG Import
Cleanup: sort file, uppercase booleans, add missing headers Also update files to ignore for check_cmake.
2023-05-17 03:07:43 +00:00
if(TRUE)
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
if(NOT OPENIMAGEIO_IDIFF)
message(WARNING "Disabling SVG tests because OIIO idiff does not exist")
else()
set(_svg_render_tests complex path)
foreach(render_test ${_svg_render_tests})
add_python_test(
io_curve_svg_${render_test}
${CMAKE_CURRENT_LIST_DIR}/bl_io_curve_svg_test.py
-blender "${TEST_BLENDER_EXE}"
-testdir "${TEST_SRC_DIR}/io_tests/svg/${render_test}"
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/io_curve_svg"
)
endforeach()
Beginning of automated SVG regression test This commit contains the CTest integration. Starting with the very simple tests for the recent fixes in the io_corve_svg addon which were related on closing path. The idea is to use same framework as what we use for render tests to make it easily visible what aspect of SVG changed or broke. In order to achieve this both .blend and .svg files are used. The .svg file defines the exact subject of test, and the .blend file defines camera, and possibly material. The longer term idea is to have a number of atomic tests for a specific SVG features to help isolating problematic areas, as well as a more comprehensive tests to perform QA.
2022-10-11 13:02:40 +00:00
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
unset(_svg_render_tests)
endif()
Beginning of automated SVG regression test This commit contains the CTest integration. Starting with the very simple tests for the recent fixes in the io_corve_svg addon which were related on closing path. The idea is to use same framework as what we use for render tests to make it easily visible what aspect of SVG changed or broke. In order to achieve this both .blend and .svg files are used. The .svg file defines the exact subject of test, and the .blend file defines camera, and possibly material. The longer term idea is to have a number of atomic tests for a specific SVG features to help isolating problematic areas, as well as a more comprehensive tests to perform QA.
2022-10-11 13:02:40 +00:00
endif()
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
if(WITH_CYCLES OR WITH_OPENGL_RENDER_TESTS)
if(NOT OPENIMAGEIO_IDIFF)
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(WARNING "Disabling render tests because OIIO idiff does not exist")
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
elseif(NOT EXISTS "${TEST_SRC_DIR}/render/shader")
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(WARNING "Disabling render tests because tests folder does not exist at ${TEST_SRC_DIR}")
Compositor: Rename compositor build option Currently, the compositor can be disabled using the WITH_COMPOSITOR build option. Since, we intent to always build the realtime compositor, we need to make the distinction between both compositors clear. So this patch renames the option to WITH_COMPOSITOR_CPU. Additionally, the check for the option was moved inside the compositor modules' own CMake file in preparation for the realtime compositor code. Differential Revision: https://developer.blender.org/D15622 Reviewed By: Jeroen Bakker, Ray Molenkamp
2022-08-09 13:59:56 +00:00
elseif(NOT WITH_COMPOSITOR_CPU)
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(WARNING "Disabling render tests because WITH_COMPOSITOR_CPU is disabled")
Tests: disable Cycles tests based on more build options WITH_OPENCOLORIO and WITH_COMPOSITOR are required to run the tests at all, since they affect many tests. WITH_OPENSUBDIV WITH_FREESTYLE, WITH_OPENVDB, WITH_OPENIMAGEDENOISE and WITH_MOD_FLUID selectively disable some tests.
2021-11-09 12:35:51 +00:00
elseif(NOT WITH_OPENCOLORIO)
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(WARNING "Disabling render tests because WITH_OPENCOLORIO is disabled")
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
else()
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
set(render_tests
Tests: add Cycles perspective/ortho/panoramic camera regression tests Ref D12691
2021-12-07 19:07:41 +00:00
camera
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
bsdf
hair
image_colorspace
image_data_types
image_mapping
image_texture_limit
integrator
light
Add light group tests category to Cycles Pull Request: https://projects.blender.org/blender/blender/pulls/108424
2023-05-30 12:37:42 +00:00
light_group
Cycles: light and shadow linking With light linking, lights can be set to affect only specific objects in the scene. Shadow linking additionally gives control over which objects acts a shadow blockers for a light. Usage: https://wiki.blender.org/wiki/Reference/Release_Notes/4.0/Cycles Implementation: https://wiki.blender.org/wiki/Source/Render/Cycles/LightLinking Ref #104972 Co-authored-by: Brecht Van Lommel <brecht@blender.org>
2023-05-24 11:36:13 +00:00
light_linking
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
mesh
Cycles: pointcloud rendering This add support for rendering of the point cloud object in Blender, as a native geometry type in Cycles that is more memory and time efficient than instancing sphere meshes. This can be useful for rendering sand, water splashes, particles, motion graphics, etc. Points are currently always rendered as spheres, with backface culling. More shapes are likely to be added later, but this is the most important one and can be customized with shaders. For CPU rendering the Embree primitive is used, for GPU there is our own intersection code. Motion blur is suppored. Volumes inside points are not currently supported. Implemented with help from: * Kévin Dietrich: Alembic procedural integration * Patrick Mourse: OptiX integration * Josh Whelchel: update for cycles-x changes Ref T92573 Differential Revision: https://developer.blender.org/D9887
2021-12-01 16:30:46 +00:00
pointcloud
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
shader
shadow_catcher
sss
)
Tests: disable Cycles tests based on more build options WITH_OPENCOLORIO and WITH_COMPOSITOR are required to run the tests at all, since they affect many tests. WITH_OPENSUBDIV WITH_FREESTYLE, WITH_OPENVDB, WITH_OPENIMAGEDENOISE and WITH_MOD_FLUID selectively disable some tests.
2021-11-09 12:35:51 +00:00
if(WITH_OPENSUBDIV)
list(APPEND render_tests displacement)
endif()
if(WITH_FREESTYLE)
list(APPEND render_tests render_layer)
endif()
if(WITH_MOD_FLUID)
Tests: disable Cycles volume test when WITH_MOD_FLUID is off
2021-11-19 12:21:48 +00:00
list(APPEND render_tests motion_blur reports volume)
Tests: disable Cycles tests based on more build options WITH_OPENCOLORIO and WITH_COMPOSITOR are required to run the tests at all, since they affect many tests. WITH_OPENSUBDIV WITH_FREESTYLE, WITH_OPENVDB, WITH_OPENIMAGEDENOISE and WITH_MOD_FLUID selectively disable some tests.
2021-11-09 12:35:51 +00:00
endif()
if(WITH_OPENVDB)
list(APPEND render_tests openvdb)
endif()
if(WITH_OPENIMAGEDENOISE)
list(APPEND render_tests denoise)
endif()
Cycles: add Path Guiding on CPU through Intel OpenPGL This adds path guiding features into Cycles by integrating Intel's Open Path Guiding Library. It can be enabled in the Sampling > Path Guiding panel in the render properties. This feature helps reduce noise in scenes where finding a path to light is difficult for regular path tracing. The current implementation supports guiding directional sampling decisions on surfaces, when the material contains a least one diffuse component, and in volumes with isotropic and anisotropic Henyey-Greenstein phase functions. On surfaces, the guided sampling decision is proportional to the product of the incident radiance and the normal-oriented cosine lobe and in volumes it is proportional to the product of the incident radiance and the phase function. The incident radiance field of a scene is learned and updated during rendering after each per-frame rendering iteration/progression. At the moment, path guiding is only supported by the CPU backend. Support for GPU backends will be added in future versions of OpenPGL. Ref T92571 Differential Revision: https://developer.blender.org/D15286
2022-09-21 15:58:34 +00:00
# Disabled until new OpenGL version with deterministic results.
#if(WITH_CYCLES_PATH_GUIDING)
# list(APPEND render_tests guiding)
#endif()
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
if(WITH_OPENGL_RENDER_TESTS)
list(APPEND render_tests grease_pencil)
endif()
Tests: disable Cycles tests based on more build options WITH_OPENCOLORIO and WITH_COMPOSITOR are required to run the tests at all, since they affect many tests. WITH_OPENSUBDIV WITH_FREESTYLE, WITH_OPENVDB, WITH_OPENIMAGEDENOISE and WITH_MOD_FLUID selectively disable some tests.
2021-11-09 12:35:51 +00:00
list(SORT render_tests)
Tests: add CMake option to run Cycles regression tests on GPU devices CYCLES_TEST_DEVICES is a list of devices (CPU, CUDA, OPTIX, OPENCL). It is set to CPU only by default. Test output is now writen to build/tests/cycles/<device>, and the HTML report has separate report pages for the different devices, with option to compare between CPU and GPU renders. Various GPU tests are still failing due to CPU/GPU differences, these are to be fixed or blacklisted still. Ref T82193
2020-10-28 15:19:03 +00:00
# Cycles
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
if(WITH_CYCLES)
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
set(_cycles_blacklist "")
Tests: skip OSL render tests in build without OSL Differential Revision: https://developer.blender.org/D9990
2021-01-14 11:24:24 +00:00
if(NOT WITH_CYCLES_OSL)
set(_cycles_blacklist OSL)
endif()
Tests: add CMake option to run Cycles regression tests on GPU devices CYCLES_TEST_DEVICES is a list of devices (CPU, CUDA, OPTIX, OPENCL). It is set to CPU only by default. Test output is now writen to build/tests/cycles/<device>, and the HTML report has separate report pages for the different devices, with option to compare between CPU and GPU renders. Various GPU tests are still failing due to CPU/GPU differences, these are to be fixed or blacklisted still. Ref T82193
2020-10-28 15:19:03 +00:00
foreach(_cycles_device ${CYCLES_TEST_DEVICES})
string(TOLOWER "${_cycles_device}" _cycles_device_lower)
Tests: blacklist failing tests for Cycles CUDA and OptiX devices Blacklist a bunch of tests on the GPU, which are known to currently have differences with CPU. These can be enabled as they are fixed or the test is modified to give compatible results when there are known limitations. OSL tests were also moved to their own directory since those are not supported on the GPU. Ref T82193
2020-11-27 15:40:16 +00:00
set(_cycles_render_tests bake;${render_tests};osl)
Tests: add CMake option to run Cycles regression tests on GPU devices CYCLES_TEST_DEVICES is a list of devices (CPU, CUDA, OPTIX, OPENCL). It is set to CPU only by default. Test output is now writen to build/tests/cycles/<device>, and the HTML report has separate report pages for the different devices, with option to compare between CPU and GPU renders. Various GPU tests are still failing due to CPU/GPU differences, these are to be fixed or blacklisted still. Ref T82193
2020-10-28 15:19:03 +00:00
foreach(render_test ${_cycles_render_tests})
Fix Cycles Metal failing when run in parallel, always run serial The command buffer fails to execute, the cause is unknown. It does not appear to be related to the binary archive cache as disabling that does not prevent the issue. Pull Request: https://projects.blender.org/blender/blender/pulls/106328
2023-03-30 17:46:49 +00:00
set(_cycles_test_name "cycles_${render_test}_${_cycles_device_lower}")
Tests: enable full Cycles Metal device regression tests on buildbot Now that all tests are passing. This does add about 5 minutes to the macOS builds on buildbot. Ref T92212
2022-02-10 17:44:58 +00:00
add_python_test(
Fix Cycles Metal failing when run in parallel, always run serial The command buffer fails to execute, the cause is unknown. It does not appear to be related to the binary archive cache as disabling that does not prevent the issue. Pull Request: https://projects.blender.org/blender/blender/pulls/106328
2023-03-30 17:46:49 +00:00
${_cycles_test_name}
Tests: enable full Cycles Metal device regression tests on buildbot Now that all tests are passing. This does add about 5 minutes to the macOS builds on buildbot. Ref T92212
2022-02-10 17:44:58 +00:00
${CMAKE_CURRENT_LIST_DIR}/cycles_render_tests.py
-blender "${TEST_BLENDER_EXE}"
-testdir "${TEST_SRC_DIR}/render/${render_test}"
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/cycles"
-device ${_cycles_device}
-blacklist ${_cycles_blacklist}
)
Fix Cycles Metal failing when run in parallel, always run serial The command buffer fails to execute, the cause is unknown. It does not appear to be related to the binary archive cache as disabling that does not prevent the issue. Pull Request: https://projects.blender.org/blender/blender/pulls/106328
2023-03-30 17:46:49 +00:00
Cleanup: use lowercase cmake commands The `Find*.cmake` modules originally used uppercase commands to match CMake's own conventions. Since then CMake uses lower-case and even within our own find modules, using all uppercase wasn't done consistently. Opt for lowercase everywhere.
2023-08-17 03:15:56 +00:00
if(NOT ("${_cycles_device_lower}" STREQUAL "cpu"))
Fix Cycles Metal failing when run in parallel, always run serial The command buffer fails to execute, the cause is unknown. It does not appear to be related to the binary archive cache as disabling that does not prevent the issue. Pull Request: https://projects.blender.org/blender/blender/pulls/106328
2023-03-30 17:46:49 +00:00
set_tests_properties(${_cycles_test_name} PROPERTIES RUN_SERIAL TRUE)
endif()
unset(_cycles_test_name)
Tests: add CMake option to run Cycles regression tests on GPU devices CYCLES_TEST_DEVICES is a list of devices (CPU, CUDA, OPTIX, OPENCL). It is set to CPU only by default. Test output is now writen to build/tests/cycles/<device>, and the HTML report has separate report pages for the different devices, with option to compare between CPU and GPU renders. Various GPU tests are still failing due to CPU/GPU differences, these are to be fixed or blacklisted still. Ref T82193
2020-10-28 15:19:03 +00:00
endforeach()
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
endforeach()
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
unset(_cycles_blacklist)
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
endif()
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
if(WITH_OPENGL_RENDER_TESTS)
Tests: add CMake option to run Cycles regression tests on GPU devices CYCLES_TEST_DEVICES is a list of devices (CPU, CUDA, OPTIX, OPENCL). It is set to CPU only by default. Test output is now writen to build/tests/cycles/<device>, and the HTML report has separate report pages for the different devices, with option to compare between CPU and GPU renders. Various GPU tests are still failing due to CPU/GPU differences, these are to be fixed or blacklisted still. Ref T82193
2020-10-28 15:19:03 +00:00
# Eevee
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
foreach(render_test ${render_tests})
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
add_python_test(
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
eevee_${render_test}_test
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
${CMAKE_CURRENT_LIST_DIR}/eevee_render_tests.py
Tests: run tests from install path Blender can only be run correctly from the install path since it requires Python scripts, dynamic libraries and other files to be present. By default the install path is the same as the build path, so it works anyway. But on the buildbot it isn't. There was a workaround but it failed on Windows and macOS. Now tests run from the install path. Detecting that path for ctest is more complicated than I would like, but I couldn't find a better solution. Ref T69541.
2019-09-07 12:03:39 +00:00
-blender "${TEST_BLENDER_EXE}"
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
-testdir "${TEST_SRC_DIR}/render/${render_test}"
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/eevee"
)
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
endforeach()
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
foreach(render_test ${render_tests})
Tests: add CMake option to run Cycles regression tests on GPU devices CYCLES_TEST_DEVICES is a list of devices (CPU, CUDA, OPTIX, OPENCL). It is set to CPU only by default. Test output is now writen to build/tests/cycles/<device>, and the HTML report has separate report pages for the different devices, with option to compare between CPU and GPU renders. Various GPU tests are still failing due to CPU/GPU differences, these are to be fixed or blacklisted still. Ref T82193
2020-10-28 15:19:03 +00:00
# Workbench
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
add_python_test(
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
workbench_${render_test}_test
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
${CMAKE_CURRENT_LIST_DIR}/workbench_render_tests.py
Tests: run tests from install path Blender can only be run correctly from the install path since it requires Python scripts, dynamic libraries and other files to be present. By default the install path is the same as the build path, so it works anyway. But on the buildbot it isn't. There was a workaround but it failed on Windows and macOS. Now tests run from the install path. Detecting that path for ctest is more complicated than I would like, but I couldn't find a better solution. Ref T69541.
2019-09-07 12:03:39 +00:00
-blender "${TEST_BLENDER_EXE}"
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
-testdir "${TEST_SRC_DIR}/render/${render_test}"
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/workbench"
)
Tests: reorder render tests so cycles/eevee/workbench are not interleaved
2019-08-30 15:50:01 +00:00
endforeach()
Tests: add automated regressions tests for Hydra Storm These are meant to test Hydra integration. Currently they are only enabled for WITH_OPENGL_RENDER_TESTS=ON due to similar reasons as Eevee and Workbench, which is that they require a GPU and results can be platform dependent due to hardware and driver differences. There are separate tests for USD and Hydra export paths. The goal is to make these identical, but they aren't yet. So for that reason they have separate reference renders, and there is a HTML page to compare them. Ref #110765
2023-08-04 13:01:55 +00:00
if(WITH_HYDRA)
# Hydra Storm
foreach(render_test ${render_tests})
add_python_test(
storm_hydra_${render_test}_test
${CMAKE_CURRENT_LIST_DIR}/storm_render_tests.py
-blender "${TEST_BLENDER_EXE}"
-testdir "${TEST_SRC_DIR}/render/${render_test}"
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/storm_hydra"
-export_method "HYDRA"
)
endforeach()
foreach(render_test ${render_tests})
add_python_test(
storm_usd_${render_test}_test
${CMAKE_CURRENT_LIST_DIR}/storm_render_tests.py
-blender "${TEST_BLENDER_EXE}"
-testdir "${TEST_SRC_DIR}/render/${render_test}"
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/storm_usd"
-export_method "USD"
)
endforeach()
endif()
Tests: make grease pencil tests part of OpenGL render tests Otherwise tests fail on machines without OpenGL.
2019-05-28 15:57:16 +00:00
endif()
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
endif()
CTests: Add render tests for Cycles The idea is to use the set of really small images from the lib folder and run Cycles render on them comparing render output to reference images in the tests repository. For sure same thing could become more generic for BI or Freestyle render engines. Thanks Campbell for review and code tweaks!
2015-01-22 10:53:49 +00:00
endif()
Render Layers and Collections (merge from render-layers) Design Documents ---------------- * https://wiki.blender.org/index.php/Dev:2.8/Source/Layers * https://wiki.blender.org/index.php/Dev:2.8/Source/DataDesignRevised User Commit Log --------------- * New Layer and Collection system to replace render layers and viewport layers. * A layer is a set of collections of objects (and their drawing options) required for specific tasks. * A collection is a set of objects, equivalent of the old layers in Blender. A collection can be shared across multiple layers. * All Scenes have a master collection that all other collections are children of. * New collection "context" tab (in Properties Editor) * New temporary viewport "collections" panel to control per-collection visibility Missing User Features --------------------- * Collection "Filter" Option to add objects based on their names * Collection Manager operators The existing buttons are placeholders * Collection Manager drawing The editor main region is empty * Collection Override * Per-Collection engine settings This will come as a separate commit, as part of the clay-engine branch Dev Commit Log -------------- * New DNA file (DNA_layer_types.h) with the new structs We are replacing Base by a new extended Base while keeping it backward compatible with some legacy settings (i.e., lay, flag_legacy). Renamed all Base to BaseLegacy to make it clear the areas of code that still need to be converted Note: manual changes were required on - deg_builder_nodes.h, rna_object.c, KX_Light.cpp * Unittesting for main syncronization requirements - read, write, add/copy/remove objects, copy scene, collection link/unlinking, context) * New Editor: Collection Manager Based on patch by Julian Eisel This is extracted from the layer-manager branch. With the following changes: - Renamed references of layer manager to collections manager - I doesn't include the editors/space_collections/ draw and util files - The drawing code itself will be implemented separately by Julian * Base / Object: A little note about them. Original Blender code would try to keep them in sync through the code, juggling flags back and forth. This will now be handled by Depsgraph, keeping Object and Bases more separated throughout the non-rendering code. Scene.base is being cleared in doversion, and the old viewport drawing code was poorly converted to use the new bases while the new viewport code doesn't get merged and replace the old one. Python API Changes ------------------ ``` - scene.layers + # no longer exists - scene.objects + scene.scene_layers.active.objects - scene.objects.active + scene.render_layers.active.objects.active - bpy.context.scene.objects.link() + bpy.context.scene_collection.objects.link() - bpy_extras.object_utils.object_data_add(context, obdata, operator=None, use_active_layer=True, name=None) + bpy_extras.object_utils.object_data_add(context, obdata, operator=None, name=None) - bpy.context.object.select + bpy.context.object.select = True + bpy.context.object.select = False + bpy.context.object.select_get() + bpy.context.object.select_set(action='SELECT') + bpy.context.object.select_set(action='DESELECT') -AddObjectHelper.layers + # no longer exists ```
2017-02-07 09:18:38 +00:00
Compositor: Rename compositor build option Currently, the compositor can be disabled using the WITH_COMPOSITOR build option. Since, we intent to always build the realtime compositor, we need to make the distinction between both compositors clear. So this patch renames the option to WITH_COMPOSITOR_CPU. Additionally, the check for the option was moved inside the compositor modules' own CMake file in preparation for the realtime compositor code. Differential Revision: https://developer.blender.org/D15622 Reviewed By: Jeroen Bakker, Ray Molenkamp
2022-08-09 13:59:56 +00:00
if(WITH_COMPOSITOR_CPU)
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
if(NOT OPENIMAGEIO_IDIFF)
message(WARNING "Disabling Compositor CPU tests because OIIO idiff does not exist")
else()
set(compositor_tests
color
converter
filter
input
output
vector
multiple_node_setups
Compositor automated testing Added support for compositor tests. Compositor tests can be added, executed and viewed in a similar way to cycles and other render engines tests. Running test: `ctest -R compositor` Updating test: `BLENDER_TEST_UPDATE=1 ctest -R compositor` Viewing test results: typically saved under `build_folder/tests/compositor/report.html` Reviewed By: jbakker Differential Revision: https://developer.blender.org/D6334
2021-03-26 15:04:09 +00:00
)
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
if(WITH_LIBMV)
list(APPEND compositor_tests distort matte)
endif()
foreach(comp_test ${compositor_tests})
add_python_test(
Realtime Compositor: add regression tests Tests must be enabled manually using the CMake flag `WITH_COMPOSITOR_REALTIME_TEST`. Reasons are F12 for realtime compositor is experimental and buildbots have no GPU. Failing tests are excluded. Pull Request: https://projects.blender.org/blender/blender/pulls/109878
2023-08-19 13:00:54 +00:00
compositor_${comp_test}_cpu_test
${CMAKE_CURRENT_LIST_DIR}/compositor_cpu_render_tests.py
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
-blender "${TEST_BLENDER_EXE}"
-testdir "${TEST_SRC_DIR}/compositor/${comp_test}"
-idiff "${OPENIMAGEIO_IDIFF}"
Realtime Compositor: add regression tests Tests must be enabled manually using the CMake flag `WITH_COMPOSITOR_REALTIME_TEST`. Reasons are F12 for realtime compositor is experimental and buildbots have no GPU. Failing tests are excluded. Pull Request: https://projects.blender.org/blender/blender/pulls/109878
2023-08-19 13:00:54 +00:00
-outdir "${TEST_OUT_DIR}/compositor_cpu"
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
)
endforeach()
Realtime Compositor: add regression tests Tests must be enabled manually using the CMake flag `WITH_COMPOSITOR_REALTIME_TEST`. Reasons are F12 for realtime compositor is experimental and buildbots have no GPU. Failing tests are excluded. Pull Request: https://projects.blender.org/blender/blender/pulls/109878
2023-08-19 13:00:54 +00:00
endif()
endif()
Cleanup: format
2023-08-24 01:37:29 +00:00
# NOTE: WITH_COMPOSITOR_CPU is needed for rendering.
CMake: Rename compositor tests option to WITH_COMPOSITOR_REALTIME_TESTS It follows the naming convention of other unit-test variables. Pull Request: https://projects.blender.org/blender/blender/pulls/111437
2023-08-23 14:03:12 +00:00
if(WITH_COMPOSITOR_REALTIME_TESTS AND WITH_COMPOSITOR_CPU)
Realtime Compositor: add regression tests Tests must be enabled manually using the CMake flag `WITH_COMPOSITOR_REALTIME_TEST`. Reasons are F12 for realtime compositor is experimental and buildbots have no GPU. Failing tests are excluded. Pull Request: https://projects.blender.org/blender/blender/pulls/109878
2023-08-19 13:00:54 +00:00
if(NOT OPENIMAGEIO_IDIFF)
message(WARNING "Disabling realtime compositor tests because OIIO idiff does not exist")
else()
set(compositor_tests
color
converter
filter
input
output
vector
multiple_node_setups
)
Cleanup: format
2023-08-24 01:37:29 +00:00
Realtime Compositor: add regression tests Tests must be enabled manually using the CMake flag `WITH_COMPOSITOR_REALTIME_TEST`. Reasons are F12 for realtime compositor is experimental and buildbots have no GPU. Failing tests are excluded. Pull Request: https://projects.blender.org/blender/blender/pulls/109878
2023-08-19 13:00:54 +00:00
if(WITH_LIBMV)
list(APPEND compositor_tests distort matte)
endif()
foreach(comp_test ${compositor_tests})
add_python_test(
compositor_${comp_test}_realtime_test
${CMAKE_CURRENT_LIST_DIR}/compositor_realtime_render_tests.py
-blender "${TEST_BLENDER_EXE}"
-testdir "${TEST_SRC_DIR}/compositor/${comp_test}"
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/compositor_realtime"
)
endforeach()
CMake: quiet references to undeclared variable warnings These warnings can reveal errors in logic, so quiet them by checking if the features are enabled before using variables or by assigning empty strings in some cases. - Check CMAKE_THREAD_LIBS_INIT is set before use as CMake docs note that this may be left unset if it's not needed. - Remove BOOST/OPENVDB/VULKAN references when disable. - Define INC_SYS even when empty. - Remove PNG_INC from freetype (not defined anywhere).
2023-01-19 06:07:23 +00:00
endif()
Compositor automated testing Added support for compositor tests. Compositor tests can be added, executed and viewed in a similar way to cycles and other render engines tests. Running test: `ctest -R compositor` Updating test: `BLENDER_TEST_UPDATE=1 ctest -R compositor` Viewing test results: typically saved under `build_folder/tests/compositor/report.html` Reviewed By: jbakker Differential Revision: https://developer.blender.org/D6334
2021-03-26 15:04:09 +00:00
endif()
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
set(geo_node_tests
Added more Geometry Node tests * Attributes * Utilities * Volume Test folder located in `lib\tests\modeling\geometry_nodes` It contains around 34 new tests. * attribute clamp + other attribute nodes * Curve Primitive nodes * Mesh Primitive nodes * delete geometry * convex hull * subdivision surface * boolean intersect * boolean diff * volume to mesh Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D12250
2021-08-24 07:52:01 +00:00
attributes
curve_primitives
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
curves
Geometry Nodes: new Interpolate Curves node This adds a new `Interpolate Curves` node. It allows generating new curves between a set of existing guide curves. This is essential for procedural hair. Usage: - One has to provide a set of guide curves and a set of root positions for the generated curves. New curves are created starting from these root positions. The N closest guide curves are used for the interpolation. - An additional up vector can be provided for every guide curve and root position. This is typically a surface normal or nothing. This allows generating child curves that are properly oriented based on the surface orientation. - Sometimes a point should only be interpolated using a subset of the guides. This can be achieved using the `Guide Group ID` and `Point Group ID` inputs. The curve generated at a specific point will only take the guides with the same id into account. This allows e.g. for hair parting. - The `Max Neighbors` input limits how many guide curves are taken into account for every interpolated curve. Differential Revision: https://developer.blender.org/D16642
2023-01-20 11:09:29 +00:00
curves/interpolate_curves
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
geometry
Geometry Nodes: add instance test category
2022-12-05 16:56:35 +00:00
instance
Geometry Nodes: new Repeat Zone This adds support for running a set of nodes repeatedly. The number of iterations can be controlled dynamically as an input of the repeat zone. The repeat zone can be added in via the search or from the Add > Utilities menu. The main use case is to replace long repetitive node chains with a more flexible alternative. Technically, repeat zones can also be used for many other use cases. However, due to their serial nature, performance is very sub-optimal when they are used to solve problems that could be processed in parallel. Better solutions for such use cases will be worked on separately. Repeat zones are similar to simulation zones. The major difference is that they have no concept of time and are always evaluated entirely in the current frame, while in simulations only a single iteration is evaluated per frame. Stopping the repetition early using a dynamic condition is not yet supported. "Break" functionality can be implemented manually using Switch nodes in the loop for now. It's likely that this functionality will be built into the repeat zone in the future. For now, things are kept more simple. Remaining Todos after this first version: * Improve socket inspection and viewer node support. Currently, only the first iteration is taken into account for socket inspection and the viewer. * Make loop evaluation more lazy. Currently, the evaluation is eager, meaning that it evaluates some nodes even though their output may not be required. Pull Request: https://projects.blender.org/blender/blender/pulls/109164
2023-07-11 20:36:10 +00:00
repeat_zone
Added more Geometry Node tests * Attributes * Utilities * Volume Test folder located in `lib\tests\modeling\geometry_nodes` It contains around 34 new tests. * attribute clamp + other attribute nodes * Curve Primitive nodes * Mesh Primitive nodes * delete geometry * convex hull * subdivision surface * boolean intersect * boolean diff * volume to mesh Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D12250
2021-08-24 07:52:01 +00:00
mesh_primitives
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
mesh
Tests: Enable new tests for geometry nodes extrude node rB95981c9876483256b28
2022-01-24 19:55:32 +00:00
mesh/extrude
Geometry Nodes: Use Mesh instead of BMesh in split edges node Rewrite the edge split code to operate directly on Mesh instead of BMesh. This allows for the use of multi-threading and makes the node around 2 times faster. Around 15% of the time is spent just on the creation of the topology maps, so these being cached on the mesh could cause an even greater speedup. The new node gave identical results compared to the BMesh version on all the meshes I tested it on (up to permutation of the indices). Here are some of the results on a few simple test cases: (Intel i7-7700HQ (8 cores) @ 2.800GHz , with 50% of edges selected) | | 370x370 UV Sphere | 400x400 Grid | Suzanne 4 subdiv levels | | ----- | ----------------- | -------------- | --------------------- | | Mesh | 89ms | 111ms | 76ms | | BMesh | 200ms | 276ms | 208ms | Differential Revision: https://developer.blender.org/D16399
2022-11-20 21:42:10 +00:00
mesh/split_edges
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
points
Geometry Nodes: add texture regression test category
2022-12-05 11:06:18 +00:00
texture
Added more Geometry Node tests * Attributes * Utilities * Volume Test folder located in `lib\tests\modeling\geometry_nodes` It contains around 34 new tests. * attribute clamp + other attribute nodes * Curve Primitive nodes * Mesh Primitive nodes * delete geometry * convex hull * subdivision surface * boolean intersect * boolean diff * volume to mesh Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D12250
2021-08-24 07:52:01 +00:00
utilities
vector
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
)
Tests: Disable tests for non-compiled libraries This diff disables tests for Boolean, subdivision surface and volume when GMP, Opensubdiv and Openvdb are not compiled respectively. It also changes the existing file structure and adds sub-folders for boolean and subdivison tests. The volume folder only has one test and is as unchanged structure-wise. Reviewed By: JacquesLucke, LazyDodo Differential Revision: https://developer.blender.org/D12448
2021-09-29 15:42:55 +00:00
if(WITH_GMP)
list(APPEND geo_node_tests mesh/boolean)
endif()
if(WITH_OPENVDB)
list(APPEND geo_node_tests volume)
endif()
if(WITH_OPENSUBDIV)
list(APPEND geo_node_tests mesh/subdivision_tests)
endif()
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
foreach(geo_node_test ${geo_node_tests})
if(EXISTS "${TEST_SRC_DIR}/modeling/geometry_nodes/${geo_node_test}/")
file(GLOB files "${TEST_SRC_DIR}/modeling/geometry_nodes/${geo_node_test}/*.blend")
foreach(file ${files})
get_filename_component(filename ${file} NAME_WE)
add_blender_test(
geo_node_${geo_node_test}_test_${filename}
${file}
--python ${TEST_PYTHON_DIR}/geo_node_test.py
)
endforeach()
else()
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(STATUS "Directory named ${TEST_SRC_DIR}/modeling/geometry_nodes/${geo_node_test}/ Not Found, disabling test.")
Regression Testing: Running tests based on blend files Runs tests based on blend files with minimum python interaction. Developed as part of GSoC 2021 - Regression Testing of Geometry Nodes. Earlier, tests were built from scratch by adding a modifier/operation from the Python API. Now, tests can also be created inside blender and are compared using Python script. Features: Automatically adding expected object if it doesn't exist. This patch adds tests for the following Geometry Nodes category: * Curves * Geometry * Mesh * Points The implemented UML diagram for refactoring of mesh test framework. {F10225906} Technical Changes: SpecMeshTest: It adds the modifier/operation based on the Spec provided. BlendFileTest: It applies already existing modifier/operation from the blend file. Test folders hierarchy with tests. This folder should be extracted to `lib\tests\modeling` {F10240651} Note: The `geometry_nodes` folder might lie under another `geometry_nodes` folder while extracting, please double check. Use the inner-most one. The hierarchy should be: -`lib\tests\modeling\geometry_nodes\mesh` -`lib\tests\modeling\geometry_nodes\points` and so on. * From `ctest` the tests should be run as `ctest -R geo_node -C [Configuration]` on Windows. * Each single test can be run with its entire name e..g `ctest -R geo_node_geometry_join_geometry`.(just an example). Run `ctest -N -R geo_node` to see all tests. * From blender, the tests can be run `blender -b path\to\blend\file --python path\to\geo_node_test.py` Reviewed By: zazizizou, JacquesLucke Differential Revision: https://developer.blender.org/D11611
2021-07-27 15:30:28 +00:00
endif()
endforeach()
Tests: support simulation nodes regression tests Geometry nodes supports simulation nodes which allows later frames to depend on previous frames. The existing geometry nodes regression tests only evaluated the node tree at a single frame and therefore couldn't test the correct behavior of simulations. This adds a new kind of regression test that evaluates the scene at multiple consecutive frames and then checks if the last frame matches. Pull Request: https://projects.blender.org/blender/blender/pulls/109046
2023-06-16 08:00:55 +00:00
if(EXISTS "${TEST_SRC_DIR}/modeling/geometry_nodes/simulation/")
file(GLOB files "${TEST_SRC_DIR}/modeling/geometry_nodes/simulation/*.blend")
foreach(file ${files})
get_filename_component(filename ${file} NAME_WE)
add_blender_test(
geo_node_simulation_test_${filename}
${file}
--python ${TEST_PYTHON_DIR}/geo_node_sim_test.py
)
endforeach()
else()
message(STATUS "Directory named ${TEST_SRC_DIR}/modeling/geometry_nodes/simulation/ not found, disabling tests")
endif()
Tests: add OpenGL UI drawing tests. This reuses the Cycles regression test code to also work for OpenGL UI drawing. We launch Blender with a bunch of .blend files, take a screenshot and compare it with a reference screenshot, and generate a HMTL report showing the failed tests and their differences. For Cycles we keep small reference renders to compare to in svn, but for OpenGL developers currently have to generate the references manually. How to use: * WITH_OPENGL_DRAW_TESTS=ON in CMake * BLENDER_TEST_UPDATE=1 ctest -R opengl_draw * .. make code changes .. * ctest -R opengl_draw * open build_dir/tests/opengl_draw/report.html Differential Revision: https://developer.blender.org/D3064
2018-02-14 19:33:33 +00:00
if(WITH_OPENGL_DRAW_TESTS)
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
if(NOT OPENIMAGEIO_IDIFF)
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(STATUS "Disabling OpenGL draw tests because OIIO idiff does not exist")
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
elseif(NOT EXISTS "${TEST_SRC_DIR}/opengl")
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(STATUS "Disabling OpenGL draw tests because tests folder does not exist at ${TEST_SRC_DIR}")
Tests: add more descriptive messages when idiff is not available Based on patch contributed by Diana Picus in D4355.
2019-05-16 18:21:35 +00:00
else()
Tests: only run OpenGL draw tests on lib/tests/opengl, support symlinks. To keep running these tests relatively fast and practical to run often, running it on all .blend files is a bit much. So now we only run it on files from this directory. Additionally this adds supports for following symlinks, so that you can easily symlinks to other directories if you want to tests extra files which may have linked libraries.
2019-02-20 15:03:13 +00:00
# Use all subdirectories of opengl folder.
file(GLOB children RELATIVE ${TEST_SRC_DIR}/opengl ${TEST_SRC_DIR}/opengl/*)
Code cleanup: deduplicate code for running Python scripts outside Blender.
2018-02-16 00:22:34 +00:00
foreach(child ${children})
Tests: only run OpenGL draw tests on lib/tests/opengl, support symlinks. To keep running these tests relatively fast and practical to run often, running it on all .blend files is a bit much. So now we only run it on files from this directory. Additionally this adds supports for following symlinks, so that you can easily symlinks to other directories if you want to tests extra files which may have linked libraries.
2019-02-20 15:03:13 +00:00
# Resolve symlinks, useful to test production files with linked libraries.
get_filename_component(child_path ${TEST_SRC_DIR}/opengl/${child} REALPATH)
if(IS_DIRECTORY ${child_path})
file(GLOB_RECURSE blends "${child_path}/*.blend")
Code cleanup: deduplicate code for running Python scripts outside Blender.
2018-02-16 00:22:34 +00:00
if(blends)
add_python_test(
Tests: remove unnecessary _test postfix on test names.
2019-03-15 18:11:33 +00:00
opengl_draw_${child}
Tests: add OpenGL UI drawing tests. This reuses the Cycles regression test code to also work for OpenGL UI drawing. We launch Blender with a bunch of .blend files, take a screenshot and compare it with a reference screenshot, and generate a HMTL report showing the failed tests and their differences. For Cycles we keep small reference renders to compare to in svn, but for OpenGL developers currently have to generate the references manually. How to use: * WITH_OPENGL_DRAW_TESTS=ON in CMake * BLENDER_TEST_UPDATE=1 ctest -R opengl_draw * .. make code changes .. * ctest -R opengl_draw * open build_dir/tests/opengl_draw/report.html Differential Revision: https://developer.blender.org/D3064
2018-02-14 19:33:33 +00:00
${CMAKE_CURRENT_LIST_DIR}/opengl_draw_tests.py
Tests: run tests from install path Blender can only be run correctly from the install path since it requires Python scripts, dynamic libraries and other files to be present. By default the install path is the same as the build path, so it works anyway. But on the buildbot it isn't. There was a workaround but it failed on Windows and macOS. Now tests run from the install path. Detecting that path for ctest is more complicated than I would like, but I couldn't find a better solution. Ref T69541.
2019-09-07 12:03:39 +00:00
-blender "${TEST_BLENDER_EXE}"
Tests: only run OpenGL draw tests on lib/tests/opengl, support symlinks. To keep running these tests relatively fast and practical to run often, running it on all .blend files is a bit much. So now we only run it on files from this directory. Additionally this adds supports for following symlinks, so that you can easily symlinks to other directories if you want to tests extra files which may have linked libraries.
2019-02-20 15:03:13 +00:00
-testdir "${child_path}"
Code cleanup: deduplicate code for running Python scripts outside Blender.
2018-02-16 00:22:34 +00:00
-idiff "${OPENIMAGEIO_IDIFF}"
-outdir "${TEST_OUT_DIR}/opengl_draw"
)
Tests: add OpenGL UI drawing tests. This reuses the Cycles regression test code to also work for OpenGL UI drawing. We launch Blender with a bunch of .blend files, take a screenshot and compare it with a reference screenshot, and generate a HMTL report showing the failed tests and their differences. For Cycles we keep small reference renders to compare to in svn, but for OpenGL developers currently have to generate the references manually. How to use: * WITH_OPENGL_DRAW_TESTS=ON in CMake * BLENDER_TEST_UPDATE=1 ctest -R opengl_draw * .. make code changes .. * ctest -R opengl_draw * open build_dir/tests/opengl_draw/report.html Differential Revision: https://developer.blender.org/D3064
2018-02-14 19:33:33 +00:00
endif()
Code cleanup: deduplicate code for running Python scripts outside Blender.
2018-02-16 00:22:34 +00:00
endif()
endforeach()
Tests: add OpenGL UI drawing tests. This reuses the Cycles regression test code to also work for OpenGL UI drawing. We launch Blender with a bunch of .blend files, take a screenshot and compare it with a reference screenshot, and generate a HMTL report showing the failed tests and their differences. For Cycles we keep small reference renders to compare to in svn, but for OpenGL developers currently have to generate the references manually. How to use: * WITH_OPENGL_DRAW_TESTS=ON in CMake * BLENDER_TEST_UPDATE=1 ctest -R opengl_draw * .. make code changes .. * ctest -R opengl_draw * open build_dir/tests/opengl_draw/report.html Differential Revision: https://developer.blender.org/D3064
2018-02-14 19:33:33 +00:00
endif()
endif()
Added simple unittests for Alembic exporter This test checks that a set of cubes are exported with the correct transform, both with flatten=True and flatten=False. This commit also adds an easy to use superclass for upcoming Alembic unit tests.
2017-04-14 10:54:20 +00:00
if(WITH_ALEMBIC)
Alembic unit tests: don't depend on ALEMBIC_ROOT_DIR being defined by user By mistake, the code relied on ALEMBIC_ROOT_DIR being defined by the user running the tests. Now CMake macros are used to correctly find the Alembic root directory.
2017-04-21 14:20:01 +00:00
find_package_wrapper(Alembic)
if(NOT ALEMBIC_FOUND)
message(FATAL_ERROR "Alembic is enabled but cannot be found")
endif()
get_filename_component(real_include_dir ${ALEMBIC_INCLUDE_DIR} REALPATH)
get_filename_component(ALEMBIC_ROOT_DIR ${real_include_dir} DIRECTORY)
Cleanup: use 2 space indentation for CMake
2019-04-17 04:35:54 +00:00
Code cleanup: deduplicate code for running Python scripts outside Blender.
2018-02-16 00:22:34 +00:00
add_python_test(
CMake: use bf_io_ prefix for IO tests This simplifies running built-in IO tests with: ctest -R bf_io_ Also use "bf_io_" prefix for the libraries since it was already used by some and it's a useful hint the libraries are used for IO.
2023-09-23 10:22:19 +00:00
bf_io_alembic_export_tests
Cleanup: rename `alembic_tests.py` to `alembic_tests_export.py` Rename `alembic_tests.py` to `alembic_tests_export.py`, as this makes it clearer what is being tested. No functional changes.
2020-08-17 10:55:23 +00:00
${CMAKE_CURRENT_LIST_DIR}/alembic_export_tests.py
Tests: run tests from install path Blender can only be run correctly from the install path since it requires Python scripts, dynamic libraries and other files to be present. By default the install path is the same as the build path, so it works anyway. But on the buildbot it isn't. There was a workaround but it failed on Windows and macOS. Now tests run from the install path. Detecting that path for ctest is more complicated than I would like, but I couldn't find a better solution. Ref T69541.
2019-09-07 12:03:39 +00:00
--blender "${TEST_BLENDER_EXE}"
Code cleanup: deduplicate code for running Python scripts outside Blender.
2018-02-16 00:22:34 +00:00
--testdir "${TEST_SRC_DIR}/alembic"
--alembic-root "${ALEMBIC_ROOT_DIR}"
)
Cleanup: use 2 space indentation for CMake
2019-04-17 04:35:54 +00:00
Cleanup: refactor tests executing Blender to use add_blender_test function
2019-08-02 12:25:40 +00:00
add_blender_test(
Cleanup: Alembic, rename unit test This rename is to prepare for a future addition to the unit test file. Currently it's named "import" and I will add an export test as well. The rename is a separate commit to easily see the difference between the rename and the addition of another test. No functional changes.
2020-02-14 14:14:46 +00:00
script_alembic_io
--python ${CMAKE_CURRENT_LIST_DIR}/bl_alembic_io_test.py
Fix alembic tests not running with debug build on windows
2017-06-04 23:05:59 +00:00
--
--testdir "${TEST_SRC_DIR}/alembic"
CMake: test build configuration support D2765 by @akitula
2017-08-03 22:11:42 +00:00
)
Added simple unittests for Alembic exporter This test checks that a set of cubes are exported with the correct transform, both with flatten=True and flatten=False. This commit also adds an easy to use superclass for upcoming Alembic unit tests.
2017-04-14 10:54:20 +00:00
endif()
Merged master@e12c3110024dc4b62ffefa739288218b04e39f71 into blender2.8 This doesn't merge entire master into blender2.8, but at least solves one conflict.
2017-04-18 12:18:06 +00:00
New test for USD import. Added a basic test for importing a primitive hierarchy from a USDA file into Blender. This was reviewed by Sybren in patch D12479.
2021-10-20 16:07:28 +00:00
if(WITH_USD)
Fix T103354: Author extents on UsdGeomMesh A properly authored USD file will have the extent attribute authored on all prims conforming to UsdGeomBoundable. This cached extent information is useful because it allows the 3D range of prims to be quickly understood without reading potentially large arrays of data. Note that because the shape of prims may change over time, extent attributes are always evaluated for a given timecode. This patch introduces support for authoring extents on meshes and volumes during export to USD. Because extents are common to multiple kinds of geometries, the main support for authoring extents has been placed in USDAbstractWriter, whose new author_extent method can operate on any prim conforming to pxr::UsdGeomBoundable. The USD library already provides us the code necessary to compute the bounds for a given prim, in pxr::UsdGeomBBoxCache::ComputeLocalBound. Note that not all prims that are imageable are boundable, such as transforms and cameras. For more details on extents, see https://graphics.pixar.com/usd/release/api/class_usd_geom_boundable.html#details. Note that when new types of geometries are introduced, such as curves in https://developer.blender.org/D16545, we will need to update the USD writer for that geometry such that it calls this->author_extent. Update on Feb 2: This patch has been updated to include a unit test to ensure authored extents are valid. This test requires new test assets that will need to be submitted via svn. The test assets are attached in the d16837_usd_test_assets.zip file. To use, unzip and merge the contents of this zip into the lib/tests/usd folder. This unit test also addresses #104269 by validating compliance of exported USD via UsdUtils.ComplianceChecker. Pull Request #104676
2023-02-14 11:11:53 +00:00
add_blender_test(
CMake: use bf_io_ prefix for IO tests This simplifies running built-in IO tests with: ctest -R bf_io_ Also use "bf_io_" prefix for the libraries since it was already used by some and it's a useful hint the libraries are used for IO.
2023-09-23 10:22:19 +00:00
bf_io_usd_export_test
Fix T103354: Author extents on UsdGeomMesh A properly authored USD file will have the extent attribute authored on all prims conforming to UsdGeomBoundable. This cached extent information is useful because it allows the 3D range of prims to be quickly understood without reading potentially large arrays of data. Note that because the shape of prims may change over time, extent attributes are always evaluated for a given timecode. This patch introduces support for authoring extents on meshes and volumes during export to USD. Because extents are common to multiple kinds of geometries, the main support for authoring extents has been placed in USDAbstractWriter, whose new author_extent method can operate on any prim conforming to pxr::UsdGeomBoundable. The USD library already provides us the code necessary to compute the bounds for a given prim, in pxr::UsdGeomBBoxCache::ComputeLocalBound. Note that not all prims that are imageable are boundable, such as transforms and cameras. For more details on extents, see https://graphics.pixar.com/usd/release/api/class_usd_geom_boundable.html#details. Note that when new types of geometries are introduced, such as curves in https://developer.blender.org/D16545, we will need to update the USD writer for that geometry such that it calls this->author_extent. Update on Feb 2: This patch has been updated to include a unit test to ensure authored extents are valid. This test requires new test assets that will need to be submitted via svn. The test assets are attached in the d16837_usd_test_assets.zip file. To use, unzip and merge the contents of this zip into the lib/tests/usd folder. This unit test also addresses #104269 by validating compliance of exported USD via UsdUtils.ComplianceChecker. Pull Request #104676
2023-02-14 11:11:53 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_usd_export_test.py
--
--testdir "${TEST_SRC_DIR}/usd"
)
New test for USD import. Added a basic test for importing a primitive hierarchy from a USDA file into Blender. This was reviewed by Sybren in patch D12479.
2021-10-20 16:07:28 +00:00
add_blender_test(
CMake: use bf_io_ prefix for IO tests This simplifies running built-in IO tests with: ctest -R bf_io_ Also use "bf_io_" prefix for the libraries since it was already used by some and it's a useful hint the libraries are used for IO.
2023-09-23 10:22:19 +00:00
bf_io_usd_import_test
New test for USD import. Added a basic test for importing a primitive hierarchy from a USDA file into Blender. This was reviewed by Sybren in patch D12479.
2021-10-20 16:07:28 +00:00
--python ${CMAKE_CURRENT_LIST_DIR}/bl_usd_import_test.py
--
--testdir "${TEST_SRC_DIR}/usd"
)
endif()
FFmpeg: Add regression tests Currently only covering handful of files from reports about wrong fps detected. It will need D3083 applied first to get tests passed, also tests themselves are to be committed to svn. But there are some python code which needs to be reviewed, like blendfile passed to run_blender(). Reviewers: sybren, mont29 Reviewed By: sybren, mont29 Subscribers: mont29 Differential Revision: https://developer.blender.org/D3096
2018-03-05 14:32:49 +00:00
if(WITH_CODEC_FFMPEG)
add_python_test(
Tests: remove unnecessary _test postfix on test names.
2019-03-15 18:11:33 +00:00
ffmpeg
FFmpeg: Add regression tests Currently only covering handful of files from reports about wrong fps detected. It will need D3083 applied first to get tests passed, also tests themselves are to be committed to svn. But there are some python code which needs to be reviewed, like blendfile passed to run_blender(). Reviewers: sybren, mont29 Reviewed By: sybren, mont29 Subscribers: mont29 Differential Revision: https://developer.blender.org/D3096
2018-03-05 14:32:49 +00:00
${CMAKE_CURRENT_LIST_DIR}/ffmpeg_tests.py
Tests: run tests from install path Blender can only be run correctly from the install path since it requires Python scripts, dynamic libraries and other files to be present. By default the install path is the same as the build path, so it works anyway. But on the buildbot it isn't. There was a workaround but it failed on Windows and macOS. Now tests run from the install path. Detecting that path for ctest is more complicated than I would like, but I couldn't find a better solution. Ref T69541.
2019-09-07 12:03:39 +00:00
--blender "${TEST_BLENDER_EXE}"
Tests: Point ffmpeg data to a new folder
2019-07-01 15:18:43 +00:00
--testdir "${TEST_SRC_DIR}/ffmpeg"
FFmpeg: Add regression tests Currently only covering handful of files from reports about wrong fps detected. It will need D3083 applied first to get tests passed, also tests themselves are to be committed to svn. But there are some python code which needs to be reviewed, like blendfile passed to run_blender(). Reviewers: sybren, mont29 Reviewed By: sybren, mont29 Subscribers: mont29 Differential Revision: https://developer.blender.org/D3096
2018-03-05 14:32:49 +00:00
)
endif()
Tests: Add tests for image format saving and loading This adds saving and loading tests for our supported image formats. **Saving - bf_imbuf_save.py** There are 2 template images which are loaded anew for each file save attempt. One is an 8-bit RGBA image and the other 32-bit. This is required as many formats use a variety of factors to determine which of `ibuf->rect` or `ibuf->rectfloat` to use for processing. The templates are constructed to have alpha transparency as well as values > 1 (or clamped to 1 for the case of the 8-bit template). Test flow: - Load in an appropriate template image - Save it to the desired format with the desired set of options - Compare against the reference image Notes: - 98 references are used totaling ~3.6MB - 10-12 second test runtime - Templates can be reconstructed with the create-templates.blend file **Loading - bf_imbuf_load.py** Test flow: - Load in each of the reference images - Save them back out as .exr - Save additional metadata to a secondary file (alpha mode, colorspace etc) - Compare the saved out .exr with another set of reference .exrs - Compare the saved out file metadata with set of reference metadata Notes: - 98 exr references are used totaling ~10MB - 10-12 second test runtime as well A HTML report is not implemented. The diff output organization is very similar to the other tests so it should be somewhat easy to do in the future if we want. The standard set of environment variables are implemented for both: BLENDER_TEST_UPDATE, BLENDER_VERBOSE, and BLENDER_TEST_COLOR Pull Request #104442
2023-02-21 03:04:34 +00:00
if(NOT OPENIMAGEIO_IDIFF)
message(STATUS "Disabling ImBuf image format tests because OIIO idiff does not exist")
else()
Cleanup: use lowercase cmake commands The `Find*.cmake` modules originally used uppercase commands to match CMake's own conventions. Since then CMake uses lower-case and even within our own find modules, using all uppercase wasn't done consistently. Opt for lowercase everywhere.
2023-08-17 03:15:56 +00:00
set(OPTIONAL_FORMATS "")
Tests: Add tests for image format saving and loading This adds saving and loading tests for our supported image formats. **Saving - bf_imbuf_save.py** There are 2 template images which are loaded anew for each file save attempt. One is an 8-bit RGBA image and the other 32-bit. This is required as many formats use a variety of factors to determine which of `ibuf->rect` or `ibuf->rectfloat` to use for processing. The templates are constructed to have alpha transparency as well as values > 1 (or clamped to 1 for the case of the 8-bit template). Test flow: - Load in an appropriate template image - Save it to the desired format with the desired set of options - Compare against the reference image Notes: - 98 references are used totaling ~3.6MB - 10-12 second test runtime - Templates can be reconstructed with the create-templates.blend file **Loading - bf_imbuf_load.py** Test flow: - Load in each of the reference images - Save them back out as .exr - Save additional metadata to a secondary file (alpha mode, colorspace etc) - Compare the saved out .exr with another set of reference .exrs - Compare the saved out file metadata with set of reference metadata Notes: - 98 exr references are used totaling ~10MB - 10-12 second test runtime as well A HTML report is not implemented. The diff output organization is very similar to the other tests so it should be somewhat easy to do in the future if we want. The standard set of environment variables are implemented for both: BLENDER_TEST_UPDATE, BLENDER_VERBOSE, and BLENDER_TEST_COLOR Pull Request #104442
2023-02-21 03:04:34 +00:00
if(WITH_IMAGE_CINEON)
set(OPTIONAL_FORMATS "${OPTIONAL_FORMATS} CINEON")
endif()
if(WITH_IMAGE_OPENEXR)
set(OPTIONAL_FORMATS "${OPTIONAL_FORMATS} OPENEXR")
endif()
if(WITH_IMAGE_OPENJPEG)
set(OPTIONAL_FORMATS "${OPTIONAL_FORMATS} OPENJPEG")
endif()
if(WITH_IMAGE_WEBP)
set(OPTIONAL_FORMATS "${OPTIONAL_FORMATS} WEBP")
endif()
add_blender_test(
bf_imbuf_save
--python ${CMAKE_CURRENT_LIST_DIR}/bl_imbuf_save.py
--
-test_dir "${TEST_SRC_DIR}/imbuf_io"
-output_dir "${TEST_OUT_DIR}/imbuf_io/save"
-idiff "${OPENIMAGEIO_IDIFF}"
-optional_formats "${OPTIONAL_FORMATS}"
)
add_blender_test(
bf_imbuf_load
--python ${CMAKE_CURRENT_LIST_DIR}/bl_imbuf_load.py
--
-test_dir "${TEST_SRC_DIR}/imbuf_io"
-output_dir "${TEST_OUT_DIR}/imbuf_io/load"
-idiff "${OPENIMAGEIO_IDIFF}"
-optional_formats "${OPTIONAL_FORMATS}"
)
endif()
Add sequencer transform tests Tests files are based on test from D8393 Test files should be in `lib\tests\sequence_editing` These are files, I will add few more tests including animation test. {F9155273} Using generic tool to compare rendered vs reference image as other render engines. Reviewed By: sergey Differential Revision: https://developer.blender.org/D9394
2020-11-01 20:33:38 +00:00
# ------------------------------------------------------------------------------
# SEQUENCER RENDER TESTS
if(NOT OPENIMAGEIO_IDIFF)
Cleanup: use lowercase function calls & macros in for CMake This is already the case for most CMake usage. Although some find modules are an exception to this, as they were originally maintained externally they use some different conventions. Also corrected bad indentation in: intern/cycles/CMakeLists.txt
2022-09-23 04:33:44 +00:00
message(STATUS "Disabling sequencer render tests because OIIO idiff does not exist")
Add sequencer transform tests Tests files are based on test from D8393 Test files should be in `lib\tests\sequence_editing` These are files, I will add few more tests including animation test. {F9155273} Using generic tool to compare rendered vs reference image as other render engines. Reviewed By: sergey Differential Revision: https://developer.blender.org/D9394
2020-11-01 20:33:38 +00:00
else()
set(render_tests
transform
)
foreach(render_test ${render_tests})
add_python_test(
sequencer_render_${render_test}
${CMAKE_CURRENT_LIST_DIR}/sequencer_render_tests.py
-blender "${TEST_BLENDER_EXE}"
-testdir "${TEST_SRC_DIR}/sequence_editing/${render_test}"
-idiff "${OPENIMAGEIO_IDIFF}"
Fix sequence tests writing HTML report to wrong directory It was missing from tests/report.html that gathers all tests reports.
2020-11-03 12:23:43 +00:00
-outdir "${TEST_OUT_DIR}/sequence_editing"
Add sequencer transform tests Tests files are based on test from D8393 Test files should be in `lib\tests\sequence_editing` These are files, I will add few more tests including animation test. {F9155273} Using generic tool to compare rendered vs reference image as other render engines. Reviewed By: sergey Differential Revision: https://developer.blender.org/D9394
2020-11-01 20:33:38 +00:00
)
endforeach()
endif()
T45687: Rework the Export/Import of Animations This started with a fix for an animated Object Hierarchy. Then i decided to cleanup and optimize a bit. But at the end this has become a more or less full rewrite of the Animation Exporter. All of this happened in a separate local branch and i have retained all my local commits to better see what i have done. Brief description: * I fixed a few issues with exporting keyframed animations of object hierarchies where the objects have parent inverse matrices which differ from the Identity matrix. * I added the option to export sampled animations with a user defined sampling rate (new user interface option) * I briefly tested Object Animations and Rig Animations. What is still needed: * Cleanup the code * Optimize the user interface * Do the Documentation Reviewers: mont29 Reviewed By: mont29 Differential Revision: https://developer.blender.org/D3070
2018-02-24 12:11:30 +00:00
add_subdirectory(collada)
Collections and groups unification OVERVIEW * In 2.7 terminology, all layers and groups are now collection datablocks. * These collections are nestable, linkable, instanceable, overrideable, .. which opens up new ways to set up scenes and link + override data. * Viewport/render visibility and selectability are now a part of the collection and shared across all view layers and linkable. * View layers define which subset of the scene collection hierarchy is excluded for each. For many workflows one view layer can be used, these are more of an advanced feature now. OUTLINER * The outliner now has a "View Layer" display mode instead of "Collections", which can display the collections and/or objects in the view layer. * In this display mode, collections can be excluded with the right click menu. These will then be greyed out and their objects will be excluded. * To view collections not linked to any scene, the "Blender File" display mode can be used, with the new filtering option to just see Colleciton datablocks. * The outliner right click menus for collections and objects were reorganized. * Drag and drop still needs to be improved. Like before, dragging the icon or text gives different results, we'll unify this later. LINKING AND OVERRIDES * Collections can now be linked into the scene without creating an instance, with the link/append operator or from the collections view in the outliner. * Collections can get static overrides with the right click menu in the outliner, but this is rather unreliable and not clearly communicated at the moment. * We still need to improve the make override operator to turn collection instances into collections with overrides directly in the scene. PERFORMANCE * We tried to make performance not worse than before and improve it in some cases. The main thing that's still a bit slower is multiple scenes, we have to change the layer syncing to only updated affected scenes. * Collections keep a list of their parent collections for faster incremental updates in syncing and caching. * View layer bases are now in a object -> base hash to avoid quadratic time lookups internally and in API functions like visible_get(). VERSIONING * Compatibility with 2.7 files should be improved due to the new visibility controls. Of course users may not want to set up their scenes differently now to avoid having separate layers and groups. * Compatibility with 2.8 is mostly there, and was tested on Eevee demo and Hero files. There's a few things which are know to be not quite compatible, like nested layer collections inside groups. * The versioning code for 2.8 files is quite complicated, and isolated behind #ifdef so it can be removed at the end of the release cycle. KNOWN ISSUES * The G-key group operators in the 3D viewport were left mostly as is, they need to be modified still to fit better. * Same for the groups panel in the object properties. This needs to be updated still, or perhaps replaced by something better. * Collections must all have a unique name. Less restrictive namespacing is to be done later, we'll have to see how important this is as all objects within the collections must also have a unique name anyway. * Full scene copy and delete scene are exactly doing the right thing yet. Differential Revision: https://developer.blender.org/D3383 https://code.blender.org/2018/05/collections-and-groups/
2018-04-30 13:57:22 +00:00
# TODO: disabled for now after collection unification
# add_subdirectory(view_layer)
Reference in New Issue Copy Permalink