Introducing JS API v3
new
Awesome improvements to our Suitest JavaScript API!
  • One mode - no interactive vs. automated
  • One authentication - no tokens vs. user credentials
  • No Test packs
  • Configuration extensions
New authentication tokens
We have merged the authentication to a simple use of Personal tokens - with the same permissions as the user has. Old tokens (newly called Service tokens) are still available and can be used.
+
Security.
+
Maintainability.
How to create a personal token?
  1. Log into Suitest Web UI
  2. Go to User Menu → Preferences → API tokens
  3. Click
    Add new personal token
    button
  4. Fill in the
    Token name
    and click
    Create
  5. Store the generated
    Token ID
    and
    Token password
    for later use
Using one mode
We have merged Suitest JavaScript run modes into one. This way, you do not need to define if you are using our JS API tests interactively or in the automated mode anymore. You can use just one CLI script for both scenarios. Debugging and REPL are both still working, you just simply need to use only one device at a time.
+
Simplification.
How to switch to one mode?
  1. Open your configuration file.
  2. Remove your credentials (
    username
    ,
    password
    ) and
    orgId
    .
  3. If not already there, insert your
    Token ID
    (as
    tokenId
    ) and
    Token password
    (as
    tokenPassword
    ).
  4. Open the list of your CLI scripts.
  5. Remove the following options:
    -o
    ,
    --org-id
    ,
    -u
    ,
    --username
    ,
    -p
    ,
    --password
    with corresponding values.
  6. If not yet there, add
    --token-id <value>
    and
    --token-password <value>
    launcher options.
  7. Replace modes
    automated
    and
    interactive
    simply with
    run
    .
Getting rid of Test packs
Less preparation in Suitest Web UI before jumping to our JS API. You only need to add your devices and set up the application configurations. The rest can be handled within Suitest JS API.
+
Simplification.
How to replace Test packs?
  1. Open your configuration file.
  2. Remove the
    testPackId
    line from there.
  3. Create presets to replace the combinations of
    appConfigurationId
    and
    deviceId
    previously configured inside your Test packs. Remove the
    appConfigurationId
    and
    deviceId
    from the rest of the configuration file.
Configuration extensions
Imagine you have a cross-platform application and you want to test it on various types of devices. You can have one base configuration and then just add several more detailed extending the base one.
+
Scalability.
See our user documentation for more information.
No starttest and endtests
Since we do not store results of JS API tests in our Web UI, we have decided to get rid of the
startTest
and
endTest
commands. You just need to use openSession() and close it in the end. And that's it.
+
Simplification.