juli/OrcaSlicer
1
1
Fork 0
mirror of https://github.com/OrcaSlicer/OrcaSlicer.git synced 2026-05-25 14:15:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Wiki content

OrcaSlicerBot
2025-12-08 16:15:41 +00:00
parent 76d4c8249a
commit d53ff356bf
1 changed files with 32 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
developer-reference/How-to-test.md

@@ -4,24 +4,48 @@ This wiki page describes how to build and run tests on Linux. It should eventual
## Build Tests ## Build Tests
Can be built when you are building Orca Slicer binary by including the `-t` flag for `build_linux.sh`: Can be built with the `-t` flag for `build_linux.sh`:
``` ```shell
build_linux.sh -st build_linux.sh -t
``` ```
Test binaries will then appear under `build/tests`. As of this writing, not all tests will be built. (or `-ter` or `-stb` etc).
When running `build_linux.sh` with `-t`, make sure you always include the `-e` or `-b` flag if you built the binary with them, otherwise you'll rebuild all of OrcaSlicer again before the tests are ready.
Test binaries will then appear under `build/tests` or `build-dbginfo/tests` or `build-dbg/tests`. As of this writing, not all tests will be built.
### Faster Test Write-Build-Run Loop
For rebuilding after changes, you can look into `build_linux.sh` for the cmake command which triggers the build and adapt it to running independently. You'll be able to use something like:
```shell
# Obviously only use the appropriate one
BUILD_CONFIG=Release
BUILD_CONFIG=RelWithDebInfo
cd $BUILD_DIR # build or build-dbginfo probably
cmake --build . --config $BUILD_CONFIG --target tests/all
# or
cmake --build . --config $BUILD_CONFIG --target libslic3r_tests
# etc
```
If you change any CMakeLists.txt file, you'll need to rerun the configuration generation first. Change to the build directory and run `cmake ..` hopefully works without destroying the cache. Rerunning `build_linux.sh -t{eb}` is the most comprehensive way, but then everything has to be rebuilt. You'll need this if you added a new cpp file, for example.
## Run Unit Tests ## Run Unit Tests
### Run All ### Run All
``` ```shell
ctest --test-dir build/tests cd $BUILD_DIR # build or build-dbginfo probably
ctest --test-dir tests
``` ```
### Run a Specific Set ### Run a Specific Set
``` ```shell
ctest --test-dir build/tests/slic3rutils cd $BUILD_DIR # build or build-dbginfo probably
ctest --test-dir tests/slic3rutils
``` ```