rms/OrcaSlicer_WIKI
1
0
Fork 0
mirror of https://github.com/OrcaSlicer/OrcaSlicer_WIKI.git synced 2026-05-17 08:35:46 +03:00
Code Issues Packages Projects Releases Wiki Activity

How to use the changes from OrcaSlicer#10906 (#40)

Browse Source 
* How to use the changes from OrcaSlicer#10906

* Add ```shell
This commit is contained in:
coryrc
2025-12-08 08:15:24 -08:00
committed by GitHub
parent cd8020ea6a
commit b8adae8197
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
View File

@@ -4,24 +4,48 @@ This wiki page describes how to build and run tests on Linux. It should eventual
## 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`:
```
build_linux.sh -st
```shell
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 All
```
ctest --test-dir build/tests
```shell
cd $BUILD_DIR # build or build-dbginfo probably
ctest --test-dir tests
```
### Run a Specific Set
```
ctest --test-dir build/tests/slic3rutils
```shell
cd $BUILD_DIR # build or build-dbginfo probably
ctest --test-dir tests/slic3rutils
```