Importing Concerto Platform v4 tests into v5 - campsych/concerto-platform GitHub Wiki

Tests

To import test from Concerto Platform v4 to v5, all you need to do is create a new code type test in v5 and copy/paste your v4 test logic code.

View Templates

You're probably showing some view templates from your code, so you also need to recreate them in v5 and copy/paste their head tag and HTML.

Data Tables

If you used a data tables in your test, you also need to recreate it in new version. You can do that by exporting it to CSV from v4 and uploading it from CSV in v5.

Object references

If you referenced any of your objects in your v4 test code by name (e.g. concerto.template.show("intro", ...)), you should use the same name for your object in new version. If you used numeric id to reference your objects (e.g. concerto.template.show(1, ...)), you should keep in mind that in new version the ids of your objects will most probably be different so you need to either change the id or use object name as reference.

Known compatibility issues that require manual edit

• concerto.template.show R function:
  • v4: concerto.template.show(HTML, ...)
  • v5: concerto.template.show(html, ...)
• concerto session id R variable:
  • v4: concerto$sessionID
  • v5: concerto$session$id
• concerto main test id R variable:
  • v4: concerto$mainTest$id
  • v5: concerto$session$id
• CSS class of buttons that should not have default Concerto submit action registered for their on click event:
  • v4: notInteractive
  • v5: concerto-nosubmit
• javascript function to manually submit a view template:
  • v4: test.submit(buttonPressed, isTimeout)
  • v5: testRunner.submitView(buttonPressed, isTimeout, data)
• Last button pressed returned by concerto.template.show function:
  • v4: response$LAST_PRESSED_BUTTON_NAME
  • v5: response$buttonPressed