|
|
| (9 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | How to do testing in Slicer3.
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:Testing here]</font></big> |
| − | | |
| − | = Writing Tests =
| |
| − | | |
| − | == C++ ==
| |
| − | | |
| − | == Tcl ==
| |
| − | | |
| − | = Calling tests from CMake/CTest =
| |
| − | | |
| − | = Setting up automatic builds =
| |
| − | | |
| − | == Windows ==
| |
| − | | |
| − | For windows you need to use the Add Scheduled Task option in the Control Panel to create the build. This task runs in a 'dumb' dos shell, so you need to help it get jump started. The following works:
| |
| − | | |
| − | * create a .bat file that that is called from the Scheduled Task
| |
| − | * create a shell script that runs the build and call that from the .bat file
| |
| − | | |
| − | Here's an example for run.bat:
| |
| − | | |
| − | <pre>
| |
| − | echo off
| |
| − | | |
| − | C:
| |
| − | chdir C:\cygwin\bin
| |
| − | | |
| − | set CYGWIN=binmode tty ntsec
| |
| − | | |
| − | rxvt -sl 1000 -e c:/pieper/run.csh -l
| |
| − | </pre>
| |
| − | | |
| − | this example uses rxvt, which is available from cygwin, but not installed by default (it's an xterm ported to cygwin). | |
| − | | |
| − | And here's an example run.csh:
| |
| − | | |
| − | <pre> | |
| − | #!/bin/csh
| |
| − | | |
| − | setenv PATH "/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem"
| |
| − | | |
| − | c:/pieper/bwh/slicer3/latest/Slicer3/Scripts/getbuildtest.tcl --update --test-type Nightly |& c:/cygwin/bin/tee c:/pieper/bwh/slicer3/latest/Slicer3.build-log
| |
| − | | |
| − | c:/cygwin/bin/sleep 5
| |
| − | </pre> | |
| − | | |
| − | == Unix ==
| |
Latest revision as of 18:07, 10 July 2017
Home < Slicer3:TestingNote: We are migrating this content to the slicer.org domain - The newer page is here
