Features

All codeless features →

All advanced features →

Codeless Browser Test Automation

For those new to testing

Email testing

API & third-party integrations

Web test recorder

Codeless test editor

Visual testing

Accessibility testing

Browsers, screens & geolocations

Advanced scheduling

Advanced End-to-End Testing Capabilities

For experienced testers

ALSO INCLUDES

Solutions

QA testers

Build, run, and manage test suites at scale

Engineers

CI/CD hooks, API access, JS execution

Product managers

Visibility into quality without the code

See it in action

Request a personalized demo →

Pricing
Resources

Getting started

Everything you need to run your first test

Documentation

Features, API, integrations and settings

Support

Our team is here to help

Success stories

Real reviews from Ghost Inspector customers

Ghostwriter blog

QA and testing, written by the Ghost Inspector team

Latest articles on browser automation, CI/CD, and more

About Us Blog
Start free trial

GruntJS Plugin for Ghost Inspector

Ghost Inspector is an automated web testing tool that helps QA testers and engineers to easily build, edit, and run low-code/no-code web tests. Start a free trial.

GruntJS Plugin for Ghost Inspector Automated Browster Testing

We just released a new Ghost Inspector plugin for GruntJS called grunt-ghost-inspector. Grunt is a JavaScript task runner that’s often used for building projects and related processes. Our simple plugin lets you execute your Ghost Inspector tests and suites from within Grunt. This makes it easy to automatically trigger tests. For instance, you could run a suite of tests on your staging server immediately after your build process is done. Or, on your production server immediately after you deploy.

Once you add the plugin to your Grunt configuration, you can easily specify which suites and/or tests to execute:

grunt.initConfig({
  ghostinspector: {
    options: {
      apiKey: 'api-key',  // The API key for your Ghost Inspector account
    },
    production: {
      suites: ['suite-id-1', 'suite-id-2', ...],  // The IDs of any suites to execute
      tests: ['test-id-1', 'test-id-2', ...]  // The IDs of any tests to execute
    },
    staging: {
      tests: ['test-id-1', 'test-id-2', ...],
      options: {
        startUrl: 'https://staging.domain.com'  // Override the tests' start URL
      }
    }
  }
})

For full details, visit the GitHub repo or the NPM package page.