Bug checking - campsych/concerto-platform GitHub Wiki

To check for bugs in your test, click the 'Debug test' button. This will run the test and it won't be immediately obvious that anything different is happening from normal, but never fear!

Bug checking in Concerto v5 is based around the browser JavaScript Console. In most browsers you can press F12 to bring up the Console, but if that doesn't work then check this page for how to access it in your browser. Here's what the console looks like when you're running a test:

Concerto will push to the Console anything that R normally outputs. For example, if the test R code has

print("whatever")

then "[1] whatever" will be displayed in the Console.

If R has any errors then they will also be sent to the Console. This is the key place to look for why your test isn't working.

Concerto will also give an indication of what it's doing by printing milestones such as the below which shows you that it's starting to run node ID 10:

[1] "running test #10..."

Some Concerto starter content also gives you an indication of how it's working by outputting key information and data.

If you're coding your own test and something isn't working, then it's recommended to print your variables to the Console so that you can see what's going on.

Please note that in order to access Debug mode, you have to be logged into Concerto, so the Console output is only available to test developers. This is a good thing because it means that only you, the test developer, can see R's console output.

Concerto also keeps a log of errors in the 'Messages' section of the 'Administration' tab: