Hypertest v2 Docs
HyperTest
  • Overview
    • How It Works?
  • SETUP GUIDE
    • Installation
      • Deploy HyperTest Server
      • Creating your first User
      • Adding your first service
      • Integrate SDK
        • Node.js
          • Node.js SDK with CJS
          • Node.js SDK with ESM
        • Java
    • Start a Test Run
      • CLI Login
      • Type References
      • Java
  • Interpreting Test Results
    • Test Results
    • Understanding Results Categories
    • Mock Not Found
    • AI Match Mocks
    • Accepting Changes
  • USER GUIDES
    • Node.js SDK
      • Limit memory usage
      • Supported NPM packages
      • Mock Dependencies Manually
      • Unmocking/Passing Through
      • Sampling and blocking requests
      • Manage Global Variables
      • Mocking Environment Variables
      • Tags
      • Set HTTP path patterns
      • Discard a test case(Request) while recording
      • Set Git Commit Hash
      • Code coverage based features
        • Continuous Coverage
        • Updating test coverage
        • Running post test deduplication
        • Only testing modified requests
        • Ignore differences for unmodified requests
      • Experimental flags
      • Manual Request
      • Only testing modified requests
      • Server hooks
    • Java SDK
      • Sampling and blocking requests
      • Mock Dependencies Manually
      • Tags
      • Unmocking/Passing Through
      • Code Coverage Setup and Report Generation
      • Supported Java packages
    • Build your own Docker Image
    • CLI Config
    • Ignoring Differences
      • Type References for Filter functions
  • Impact Features
    • Fast Mode
    • Code Coverage Report
    • Delete Recorded Requests
    • Inter Service Testing
  • Release History
    • Slack Integration
    • Version History
Powered by GitBook
On this page
  • 1. If running tests in CI env.
  • 2. If running tests locally.
  1. SETUP GUIDE
  2. Start a Test Run

CLI Login

PreviousStart a Test RunNextType References

Last updated 5 months ago

1. If running tests in CI env.

a. Go to your accounts page

b. Click to create a new CLI token

c. Copy the newly generated CLI token and add it as a env var with key "HT_CLI_REFRESH_TOKEN"

2. If running tests locally.

a. Once the test is started, cli will prompt the user to login by opening the dashboard url.

b. If cli is unable to open the url then it will log the url, user can manually click on the link to open dashboard.

c. User can login with SSO or email password option.

d. Once login is successful the user is redirected to accounts page where the cli token is generated if it doesn't exist and the test execution will resume.

e. If the cli session times out then the process needs to be repeated. Once the token is saved in local, the same token will be reused for future test runs.