Differences

This shows you the differences between two versions of the page.

--- codebase:debugging [2024/09/28 15:58] – created - external edit 127.0.0.1
+++ codebase:debugging [2024/10/18 20:18] (current) – fponzi
@@ Line 11: / Line 11: @@
 ===== Generate the state graph =====
-See [[../using/generating-state-graphs.md|generating state graphs]] page. State graphs can help visualize what’s going on.
+See [[using:generating_state_graphs|generating state graphs]] page. State graphs can help visualize what’s going on.
 ===== Run your spec with assertion turned on. =====
@@ Line 37: / Line 37: @@
 </code>
-====== CustomBuild parameters ======
+===== More options =====
+Check [[codebase:testing|Testing]] page for more info on the options available when running tests.
-customBuild.xml supports different parameters to tune the tests. These can also be combined.
-===== Running a test with a debugger =====
-''%%-Dtest.suspend=y%%'' will suspend the execution and give you time to hook up a debugger before running a test.
-<code>
-ant -f customBuild.xml compile-test test-set -Dtest.suspend=y -Dtest.testcases="tlc2/tool/InliningTest*"
-</code>
-===== Specify number of threads =====
-By default uses all your cores. You can specify a custom amount using ''%%-Dthreads=4%%'':
-<code>
-ant -f customBuild.xml test -Dthreads=4
-</code>
-===== Halt tests when a failure is found =====
-By default the test target will run all the test and report success or failure only at the end. It can be convinient to just stop execution as soon as an error is found, with''%%-Dtest.halt=true%%''.
-<code>
-ant -f customBuild.xml test -Dtest.halt=true
-</code>