> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scoutqa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Kiro Power - Vibe Testing in Your IDE

> Vibe testing integration for Kiro IDE - test web apps without leaving your editor using natural language.

<Info>
  **GitHub Repository**: [scoutqa-dot-ai/kiro](https://github.com/scoutqa-dot-ai/kiro)
</Info>

The **Scout power for Kiro** brings vibe testing directly into your IDE. Test your web applications with natural language while you code - no context switching, no test scripts.

## What is Vibe Testing with Kiro?

**Vibe testing** is AI-powered exploratory testing designed for modern development workflows. With the Scout power installed in Kiro, you can:

* Say "test the feature I just built" and get instant feedback
* Run accessibility audits without leaving your editor
* Catch bugs before they reach production

This is **QA that matches the speed of AI-assisted development** - test as fast as you code.

## Features

<CardGroup cols={2}>
  <Card title="Autonomous Testing" icon="robot">
    The AI agent executes tests based on natural language instructions without manual scripting.
  </Card>

  <Card title="Proactive Verification" icon="shield-check">
    Automatically test features after implementation to catch issues before they ship.
  </Card>

  <Card title="Comprehensive Coverage" icon="layer-group">
    Functional testing, accessibility audits, and exploratory testing in one tool.
  </Card>

  <Card title="Real-time Results" icon="clock">
    See test progress and findings live as Scout explores your application.
  </Card>
</CardGroup>

## Installation

### Prerequisites

First, install the Scout CLI:

```bash theme={null}
npm install -g @scoutqa/cli@latest
scoutqa auth login
```

### Add the Power to Kiro

1. Open Kiro IDE
2. Click the Powers panel (ghost icon with lightning bolt)
3. Select **Add Custom Power**
4. Choose **Import power from GitHub**
5. Enter: `https://github.com/scoutqa-dot-ai/kiro`
6. Press Enter to install

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/scoutqa/images/kiro-power-install.png" alt="Installing Scout power in Kiro" />
</Frame>

## Usage

Once installed, talk to your AI agent naturally:

<Tabs>
  <Tab title="Login Testing">
    ```
    Test the login flow on https://staging.myapp.com
    ```
  </Tab>

  <Tab title="Accessibility">
    ```
    Check accessibility of the homepage
    ```
  </Tab>

  <Tab title="Exploratory">
    ```
    Run exploratory tests on the checkout process
    ```
  </Tab>

  <Tab title="Smoke Test">
    ```
    Quick smoke test on staging before I deploy
    ```
  </Tab>
</Tabs>

## Example Workflow

<Steps>
  <Step title="Implement a feature">
    Write your code as usual in Kiro
  </Step>

  <Step title="Ask for testing">
    "Test the new user profile page I just built"
  </Step>

  <Step title="Review findings">
    Scout runs tests and reports issues directly in your IDE
  </Step>

  <Step title="Fix and iterate">
    Address issues and re-test until everything passes
  </Step>
</Steps>

```
You: I just finished the checkout flow. Can you test it?

Kiro: Running Scout tests on the checkout flow...

[Scout executes parallel test scenarios]

Kiro: Testing complete. Here are the findings:

Passed:
- Add to cart works correctly
- Cart updates quantities properly
- Payment form validates inputs

Issues Found:
1. Shipping address not saved between sessions (bug)
2. No loading indicator during payment processing (UX)
3. Order confirmation missing for screen readers (a11y)
```

## Parallel Execution

Scout runs multiple test scenarios simultaneously for faster feedback:

```
Testing checkout flow...
├─ Cart functionality      ✓ Passed
├─ Address validation      ✓ Passed
├─ Payment processing      ⚠ 1 issue
└─ Order confirmation      ⚠ 2 issues

Completed in 45 seconds
```

## Troubleshooting

| Issue                 | Solution                                 |
| --------------------- | ---------------------------------------- |
| Power not appearing   | Restart Kiro after installation          |
| Authentication errors | Run `scoutqa auth login` in terminal     |
| Tests not starting    | Ensure target URL is publicly accessible |

## Why Use Vibe Testing with Kiro?

| Traditional Testing         | Vibe Testing with Scout   |
| --------------------------- | ------------------------- |
| Context switch to run tests | Test without leaving Kiro |
| Write and maintain scripts  | Natural language commands |
| Delayed feedback loop       | Instant results in IDE    |
| Manual accessibility audits | Automated WCAG checks     |

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="What is a Kiro power?">
    A Kiro power is an extension that adds capabilities to Kiro IDE's AI agent. The Scout power adds vibe testing functionality, enabling Kiro to run real exploratory tests on your web applications.
  </Accordion>

  <Accordion title="How does vibe testing work in Kiro?">
    When you ask Kiro to test something, the Scout power executes AI-powered tests on your target URL. Scout's agent navigates your app, interacts with elements, checks for issues, and reports findings directly in your IDE.
  </Accordion>

  <Accordion title="Can I test localhost during development?">
    Scout requires publicly accessible URLs. For localhost testing, use a tunneling service like [ngrok](https://ngrok.com/our-product/secure-tunnels) to expose your local server, then test using the tunnel URL.
  </Accordion>

  <Accordion title="Does Scout run tests in parallel?">
    Yes, Scout executes multiple test scenarios simultaneously for faster feedback. You'll see real-time progress as each scenario completes.
  </Accordion>

  <Accordion title="What's the difference between this and the Claude Code skill?">
    The Kiro power integrates Scout into Kiro IDE, while the Claude Code skill integrates Scout into Claude Code CLI. Choose based on your preferred development environment.
  </Accordion>
</AccordionGroup>

## Related

* [Scout CLI](/tooling/cli) - Run Scout from any terminal
* [Cursor Rules](/tooling/cursor-rules) - Use Scout in Cursor IDE
* [Claude Code Skill](/tooling/claude-code-skill) - Use Scout in Claude Code

***

<AccordionGroup>
  <Accordion title="Testing localhost applications">
    Scout requires a **publicly accessible URL** to run tests. Deployed environments like staging and production work immediately.

    For localhost testing, use a tunneling service like [ngrok](https://ngrok.com/our-product/secure-tunnels):

    ```bash theme={null}
    # Start your app, then create a tunnel
    ngrok http 3000
    ```

    Then ask Kiro to test the ngrok URL:

    ```
    Test my checkout flow on https://abc123.ngrok.io
    ```

    \*Third-party tunneling services are not affiliated with Scout. Use at your own risk.
  </Accordion>
</AccordionGroup>