Skip to content
| Marketplace
Sign in
Visual Studio Code>Testing>Geck (Beta)New to Visual Studio Code? Get it now.
Geck (Beta)

Geck (Beta)

Geck

|
19 installs
| (0) | Free
AI-Native Regression Testing: Test generation, execution, and reporting (Beta Release)
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

GECK 🦎 - AI-Native Test Automation (Beta Release)

Supercharge your test automation with Geck, the AI-native platform that writes, runs, and maintains end-to-end tests—right from your VS Code environment.

  • ✅ Self-healing tests: Geck adapts to UI changes without breaking.
  • 🧠 AI-generated test scripts: Describe what you want to test, and let Geck take care of the rest.
  • 🚫 No brittle selectors: Say goodbye to flaky, maintenance-heavy tests.

🚀 User Quick Start

1. Installation

VS Code Extension:

  • Install from the VS Code Marketplace.
  • Open your project folder in VS Code.

2. Authentication (Using Email)

  • You must provide your email address for authentication. No password is required.
  • The first time you use Geck, you will be prompted to enter your email in the extension UI.

3. Setting Up Settings

For the VS Code Extension (Settings Panel)

  • The extension will prompt you for your OpenAI API key if it is not already set.
  • All other test execution settings (browser type, run mode, parallelism, UX report, etc.) can be configured in the Geck Settings Panel within VS Code.

Available Settings in the Extension:

Setting Name Description Default
Run Mode Run tests in headless mode (no UI) or browser mode (visible browser). headless
Max Parallel Tests Number of tests to run at the same time. 2
Browser Type Choose which browser to use: chromium, firefox, or webkit. chromium
Browser Resolution Set the screen size for browser during test runs (e.g., 1024x768). 1024x768
AI Test Automation Choose between visual-based (cuaModel) or code-based (generatePlaywrightCode) AI test generation. cuaModel
Generate UX Report Enable to generate a UX analysis markdown report after test completion. false
Enable Client-Side Login Enable to detect and execute login actions on the client side. false

4. Creating a Test Case and Categories

In the VS Code Extension:

  1. Click the Geck icon in the VS Code sidebar to open the Geck panel. OR select "Open Geck Sidebar" in command pallet (cmd+shift+p)
  2. In the Geck panel, fill out the test creation form:
    • URL: Enter the web address you want to test.
    • Test Case Description: Describe what you want to test in plain English.
    • Project Name (optional): Use this field to group related test cases (acts as a category).
  3. Click Generate Steps. The extension will use AI to generate a sequence of test steps based on your description.
  4. Review the generated steps; edit/improve steps as needed (you know your product better)
  5. Click Save to store the test case.
    • Only after saving will the test case appear in the sidebar list.
    • The Execute (Run) button will now be enabled for this test case.

5. Executing Test Cases

In the VS Code Extension:

  • To run a test case:
    1. Find the saved test case in the sidebar list.
    2. Click the Execute (Run) button next to the test case to start execution.
    3. You can monitor the progress and results in real time.
  • To run multiple test cases:
    • Click Run for project, and all test cases within that project will execute.
    • The extension will execute them in parallel (default 2) and show live progress.

6. Viewing Logs

  • Extension:
    Open the Geck Terminal panel in VS Code to see live test output and results.
  • Log Files:
    All logs are saved in .geck/logs/ in your workspace.

7. Add .geck/ to .gitignore

To avoid committing test data, logs, and screenshots, add the following to your .gitignore:

# Geck test data, logs, and screenshots
.geck/

✨ Key Features

Capability Description
Webview UI Create & manage test cases with a form/table inside a VS Code panel.
AI‑authored steps OpenAI (o3‑mini / gpt‑4o‑mini) converts natural‑language descriptions into step‑by‑step JSON test scripts.
Playwright Runner One‑click "Run" launches Chromium at the requested URL, executes the generated script, and stores run metadata.
Persistent workspace storage Test cases are saved in test/ folder and test runs in .geck/ folder inside the workspace.
Tailwind + Lucide UI kit Clean, dark‑theme‑aware styling without external CSS frameworks.
Fully‑typed TS codebase Strict typescript, ESLint, Webpack build pipeline.

🛠 Requirements

  • VS Code ≥ 1.85 (the extension targets this API level)
  • Node ≥ 18 (to build & run scripts)
  • Playwright: installed automatically on first run (npx playwright install), or install browsers manually.
  • OpenAI API key – exported as OPENAI_API_KEY in your shell, and if you want to use CUA models, make sure you have access to those models.

🖥️ Using Geck

  1. Open a workspace folder – Geck stores files next to your source.

  2. Execute "Geck: Open Geck Panel".

  3. In the form:

    • Enter a URL to test.
    • Describe the test case in plain English.
    • (Optional) toggle Authentication and supply credentials.
  4. Press Submit → a new row appears in the table with status Queued.

  5. Click Run to launch Playwright. Progress & status update live.

  6. Delete or view details as needed.

Where is my data?

  • Test cases → <workspace>/test/{project-name}-testcases.json
  • Test runs → <workspace>/.geck/testruns.json

Delete the folder to reset everything.


⚙️ Configuration

  • Once Geck is installed, you can provide OPENAI_API_KEY which will be securely saved within your VS code (SecretStorage in VS Code) and will stay there. Just make sure it has access to O3, and CUA based models.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft