How to Run Sedstart Tests Using CLI for CI/CD

Sedstart provides the capability to execute test cases directly from the Command Line Interface (CLI). Running tests via the CLI is especially useful for local validation, CI/CD automation pipelines, and environments where UI-based execution is not feasible. This blog walks through the complete, step-by-step process to run Sedstart test cases using the CLI, covering setup, configuration, and execution.

Prerequisites

Before running Sedstart test cases from the CLI, ensure you have the following:

  • A valid Sedstart account with access to the required project and test cases
  • Sedstart CLI binary downloaded for your operating system
  • Access to Command Prompt / Terminal
  • A valid API Key
  • The relevant Project ID, Test ID, and Profile ID

Step 1: Download Sedstart CLI

Sedstart CLI is distributed as a standalone binary. No additional installation or dependencies are required. You simply need to download the correct binary based on your operating system and CPU architecture.

Base Download URL

All Sedstart CLI binaries are hosted at:

http://cli.sedstart.com/latest/

You can download the CLI by appending the appropriate folder name based on your system.

Available CLI Builds

Operating System Architecture Folder Name
macOS (Intel) amd64 cli_darwin_amd64_v1/
macOS (Apple Silicon M1/M2/M3) arm64 cli_darwin_arm64_v8.0/
Linux (Intel/AMD) amd64 cli_linux_amd64_v1/
Linux (ARM) arm64 cli_linux_arm64_v8.0/
Linux (32-bit) 386 cli_linux_386_sse2/
Windows (64-bit) amd64 cli_windows_amd64_v1/
Windows (ARM) arm64 cli_windows_arm64_v8.0/
Windows (32-bit) 386 cli_windows_386_sse2/

Example Downloads

Windows (64-bit):

http://cli.sedstart.com/latest/cli_windows_amd64_v1/sedstart.exe

Windows (32-bit):

http://cli.sedstart.com/latest/cli_windows_386_sse2/sedstart.exe

macOS (Apple Silicon):

http://cli.sedstart.com/latest/cli_darwin_arm64_v8.0/sedstart

macOS (Intel):

http://cli.sedstart.com/latest/cli_darwin_amd64_v1/sedstart

Linux (amd64):

http://cli.sedstart.com/latest/cli_linux_amd64_v1/sedstart

Make CLI Executable (macOS & Linux)

After downloading the binary, make it executable:

chmod +x sedstart

Step 2: Create the .sedstart Directory

The .sedstart directory is used to store Sedstart configuration files and the CLI binary.

Using CLI (Recommended)

Open Command Prompt or Terminal and run:

mkdir .sedstart

Manually

  1. Create a new folder on your system.
  2. Rename the folder to: .sedstart

Step 3: Add Sedstart CLI to .sedstart

  • Copy the downloaded Sedstart CLI binary into the .sedstart directory.
  • Ensure the file name remains unchanged: sedstart (macOS/Linux) sedstart.exe (Windows)

Step 4: Create the Environment (.env) File

  1. Inside the .sedstart directory, create a new file.

  2. Name the file with any valid name and a .env extension (for example: sedstart-run.env).

  3. Add the following content:

url=https://app.sedstart.com/

4.Save the file.

This file defines the Sedstart environment to which the CLI will connect.

Step 5: Prepare the Sedstart Run Command

  1. Navigate to the Sedstart UI.
  2. Copy the CLI run command for the test case or test suite you want to execute.
  3. Paste the command into a text editor for modification.

Original Run Command (Copied from Sedstart UI)

sedstart run -b chromium -d 801 -t 2120 -e <your config file name>

Edited Run Command (After Configuration)

sedstart run -b chrome -d 801 -t 2120 -p 398 -k 42c49268-69fb-413d-ba04-40dd4ea19230 -e sedstart-run.env

Explanation of Flags

-b : Browser name -d : Profile ID -t : Test ID -p : Project ID -k : API Key -e : Environment (.env) file name

Step 6: Execute the Command from CLI

  1. Open Command Prompt / Terminal.
  2. Navigate to the .sedstart directory: cd path\to\.sedstart
  3. Paste the modified Sedstart run command.
  4. Press Enter to start execution.

Step 7: View Test Results

  • Once execution is complete, results are automatically synced with Sedstart.
  • Navigate to the Sedstart UI to view execution status, logs, and detailed reports.

Conclusion

Running Sedstart test cases using the CLI provides a simple, efficient, and flexible way to execute no-code automation without relying on the UI. By downloading the correct CLI binary, setting up the .sedstart directory, configuring the environment file, and executing the run command, users can quickly trigger and monitor test executions locally or as part of automation workflows.

Best Practices

  • Keep API keys secure and avoid hardcoding them in shared scripts or repositories.
  • Use separate .env files for different environments such as QA, Staging, and Production.
  • Validate CLI execution locally before integrating it into CI/CD pipelines.

Happy Testing with Sedstart!