Testing Procedures: Difference between revisions
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
This page provides a description of various testing procedures that are implemented for the different parts of LuxCoreRender. | 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. | 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. | ||
== General Considerations == | |||
Before rendering with LuxCore, BlendLuxCore, or any other software extension you may be working on: Delete the OCL/CUDA kernel caches for the version you are testing, to make sure you are not accidentally testing GPU support with outdated code! | |||
= LuxCoreDeps = | = LuxCoreDeps = | ||
| Line 13: | Line 17: | ||
= BlendLuxCore = | = BlendLuxCore = | ||
== Rendering Example Scenes == | == Rendering Example Scenes == | ||
| Line 25: | Line 26: | ||
== Manual UI Testing == | == Manual UI Testing == | ||
Properly testing the Blender UI behavior and performance can be a very tedious job, as the theoretical number of combination of features simply does not allow to test everything. | |||
The following list is hence a check-list drafted from experience of recurring issues, most-used features, or known setups that allow testing of many aspects in a combined setup | |||
* Start with the "Default-Cube" startup scene of Blender. Run the final, viewport and material preview engines, and observe performance when doing viewport edits. <b>Note: You should use the official default-cube scene and not a custom edited version. There have been cases of bugs in Blender affecting scenes that already had BlendLuxCore-data stored inside.</b> | |||
* ... | |||
* ... | |||
Latest revision as of 22:56, 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.
General Considerations
Before rendering with LuxCore, BlendLuxCore, or any other software extension you may be working on: Delete the OCL/CUDA kernel caches for the version you are testing, to make sure you are not accidentally testing GPU support with outdated code!
LuxCoreDeps
TBD
LuxCore
TBD
BlendLuxCore
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
Properly testing the Blender UI behavior and performance can be a very tedious job, as the theoretical number of combination of features simply does not allow to test everything.
The following list is hence a check-list drafted from experience of recurring issues, most-used features, or known setups that allow testing of many aspects in a combined setup
- Start with the "Default-Cube" startup scene of Blender. Run the final, viewport and material preview engines, and observe performance when doing viewport edits. Note: You should use the official default-cube scene and not a custom edited version. There have been cases of bugs in Blender affecting scenes that already had BlendLuxCore-data stored inside.
- ...
- ...