Skip to content

Automating DBuild & DTest

Jump to bottom
Michael Baas edited this page Nov 4, 2021 · 8 revisions

While the focus of this documentation is interactive used of DBuild/DTest in the Dyalog session, they can also be used in unattended mode (automated testing or build-processes with CI-Tools).

The easiest way to do that without any more tools is by launching Dyalog with the commandline-parameter "lx=⎕SE.UCMD'DBuild {myfile}.dyalogbuild". (Because of the ⎕-symbol, this will only work with Unicode-Interpreters.) Note that this will require a v18 interpreter.

Alternative solution

A by-product of Dyalog's CITA-Project (Continous Integration Tool for APL) is the RunCITAworkspace which is primarily used within CITA. But we wanted to also support use cases like starting DBuild or DTest from the commandline. (Don't be confused by the name - while CITA is the general use case, the functionality "execute UCMD" is also accessible without knowing anything about CITA!)

In order to run a user command with RunCITA, follow these steps:

  1. download RunCITA.dws
  2. commandline: dyalog RunCITA RunUCMD="<Commandline>" CITA_Log="<NameOfLog>" [UDEBUG=ON]

The commandline arguments are:

  • RunUCMD=<Commandline> The name and arguments for the UCMD-Call (w/o leading ]), for example: RunUCMD="DBuild /git/MyPrj/MyPrj.dyalogbuild"
  • CITA_Log=<NameOfLog> Any output that is shown in the session will be collected into a logfile (using path & name you provided in <NameOfLog> with a .sessionlog.txt extension.
  • UDEBUG=ON If you set UDEBUG=ON, any errors will be shown in the session and APL will not ⎕OFF after running the command. However, as that defeats the purpose of automated testing, this will probably only be used in exotic circumstances (like the ones that triggered the addition of this modifier).

Clone this wiki locally