Testing Procedures: Difference between revisions
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
= LuxCoreDeps = | = LuxCoreDeps = | ||
TBD | |||
= LuxCore = | = LuxCore = | ||
TBD | |||
= BlendLuxCore = | = BlendLuxCore = | ||
Before rendering, delete the OCL/CUDA kernel caches to make sure you are not accidentally testing GPU support with outdated code. | |||
== Rendering Example Scenes == | |||
TBD: | |||
* Create an archive structure for rendered images associated with each release version | |||
* Add a script that will render all available test scene and save the images with appropriate tag | |||
* Add a script that compares the latest rendering to the previous version to highlight differences for further manual analysis | |||
== Manual UI Testing == | |||
Latest revision as of 13:46, 6 September 2026
Overview
This page provides a description of various testing procedures that are implemented for the different parts of LuxCoreRender. Some of these are based on automated systems (or planned to be implemented as such), while some need to be run manually. This applies specifically to testing BlendLuxCore in conjunction with the Blender User Interface.
LuxCoreDeps
TBD
LuxCore
TBD
BlendLuxCore
Before rendering, delete the OCL/CUDA kernel caches to make sure you are not accidentally testing GPU support with outdated code.
Rendering Example Scenes
TBD:
- Create an archive structure for rendered images associated with each release version
- Add a script that will render all available test scene and save the images with appropriate tag
- Add a script that compares the latest rendering to the previous version to highlight differences for further manual analysis