Reference

VSCode commands

Access these commands through the Command Palette (Ctrl+Shift+P or Cmd+Shift+P):

Working Set management

  • Plato: Add Page

    • Adds a URL to your working set
    • Prompts for URL input
    • Validates URL format
  • Plato: Remove Page

    • Removes a page from your working set
    • Shows a quick pick menu of current pages
    • Confirms before removal
  • Plato: Clear Working Set

    • Removes all pages from working set
    • Asks for confirmation
    • Useful when starting a new testing session

Configuration

  • Plato: Set Model

    • Changes the AI model
    • Shows available models
    • Prompts for API key if needed
  • Plato: Clear API Key

    • Removes stored API key
    • Useful when switching accounts
    • Requires re-entry of key for next operation

Command shortcuts

You can assign keyboard shortcuts to any command:

  1. Open Keyboard Shortcuts (Ctrl+K Ctrl+S or Cmd+K Cmd+S)
  2. Search for "Plato"
  3. Click the + icon to add a shortcut

Agent commands

Write test command

Basic syntax

All test generation commands start with /test, followed by your requirements in natural language.

/test <your test description>

Examples

Basic Navigation Test

/test Navigate to the homepage and verify the main heading is visible

Form interaction test

/test Fill out the contact form with valid data and submit it

Authentication test

/test Test the login flow with invalid credentials and verify error messages

Multi-page flow test

/test Complete a purchase flow:
1. Add item to cart
2. Go to checkout
3. Fill shipping details
4. Verify order confirmation

Advanced usage

Data-driven tests

/test Create a test that checks login with multiple user types:
- Admin user
- Regular user
- Guest user

Error handling

/test Verify error handling for the payment form:
- Invalid card number
- Expired card
- Invalid CVV

API integration

/test Test the user registration flow including API verification:
1. Submit registration form
2. Verify welcome email
3. Check user record in database

You can use markdown-style lists and formatting in your test descriptions to make complex flows clearer.