Prior to using the standalone test runner builder either:
- build the host development engine and if the target is another platform then build standalones and externals for that.
- use with a packaged build
- open the
StandaloneTestRunnerBuilder.livecodescriptstack or otehrwise load it into memory - open the message box and use the following command where:
<buildplatform>is a standalone builder build platform<options>is an array of extra build options:noui- booleantarget- a deploy targetprofile- a provisioning profile uuid for iOS
dispatch "BuildAndRun" to stack "StandaloneTestRunnerBuilder" with <buildplatform>, <options>; put the result
-h,--helpBasically the same as this-p,--platformSpecify the build platform to build and run e.g --platform "MacOSX x86-64"-a,--allBuild and run all platforms-t,--targetSpecify the build target name for mobile builds. If not specified and the all flag is set" & return &
then all targets will be run. e.g --target" && quote & "iPad Simulator 10.3" & quote & return & \--profileSpecify the iOS provisioning profile. Only necessary for device builds." & return & \-v,--verboseOutput all results instead of just failures
In the following command examples lcide is an alias to the community
development engine.
lcide tests/_standalonetestrunner/StandaloneTestRunnerBuilder.livecodescript --verbose --platform "Emscripten"
lcide tests/_standalonetestrunner/StandaloneTestRunnerBuilder.livecodescript -va