test

Verify that the CLI can reach your workspace and that your token is valid.

The command runs a single small graph query (MapAsync("_User", "UserName")) and prints the user count. If you see a number, your credentials and connectivity are fine.

Usage

curiosity-cli test \
  --server https://my-workspace.example.com/ \
  --token  $CURIOSITY_TOKEN

Options

Sample output

info: Curiosity.CLI.Program[0]
      Server responded to test query, there are 42 users in the system

When to use it

• In CI, run test immediately after wait-for to confirm the workspace is not just up but also accepting authenticated calls.
• In a new shell, run test to validate a freshly created token before scripting longer-running commands.
• After workspace upgrades, run test to catch authentication regressions early.

See also

• Common Options
• wait-for — block until the workspace is ready, then run test.
• store-token — avoid passing tokens on the command line every time.