Skip to main content

mesmer submit

mesmer submit does pretty much everything it can with a given application binary.

It will:

  1. Upload your binary to a new build in the current project
  2. Queue up test replay
  3. Queue up an application crawl

This is what that looks like when you call it:

$ mesmer submit my-app.apk
โ”€โ”€โ”€ Creating the build โœ“  Uploaded build โœ“  Installed build     Build ID  61418ab46e57b600137b55fd
โ”€โ”€โ”€ Queueing up jobs โœ“  Got test configuration โœ“  Tests in queue โœ“  Crawl in progress     Crawl Template  27381d38-1d85-46f8-adb3-4556d5a7a785     Crawl ID  127d75a2-7f3d-4065-8605-663d9c6be405
โ”€โ”€โ”€ Done!
    Tests    https://your-tenant.mesmerhq.com/home/aaaaaaaaaaaaaaaaaaaaaaaa/testresults/bbbbbbbbbbbbbbbbbbbbbbbb
    Graph    https://your-tenant.mesmerhq.com/home/aaaaaaaaaaaaaaaaaaaaaaaa/app-graph/bbbbbbbbbbbbbbbbbbbbbbbb?job-id=127d75a2-7f3d-4065-8605-663d9c6be405&view=6

Optionally, you can pass --no-crawl or --no-test to skip crawling or skip testing, respectively.

For more control over test execution, you can use --tags Tag1 Tag2 etc to only run tests matching one of several tags. See mesmer test start for more information.

CI#

This command is all you really need to integrate Mesmer with your CI environment. You can use environment variables to pass in your tenant url, project id, and authentication token (generated on a developer machine).

# This configuration can live wherever your CI platform likes to keep its secrets$ export MESMER_TENANT="[your tenant url]"$ export MESMER_AUTH_TOKEN="[your auth token]"$ export MESMER_PROJECT="[your project id]"
# Then, in your CI script:$ ./my-build-script-or-whatever --output build.apk$ mesmer submit build.apk...etc...

mesmer will pick up its configuration from the environment here, and happily upload and test your fresh build.