Skip to main content

​
Basic Workflow

1

Write Your Test Description

Describe what you want to test in natural language
2

AI Generates Steps

Keystone converts your description into executable test steps
3

Review and Execute

Preview the generated test and make adjustments as needed

​
Writing Effective Descriptions

​
Basic Format

Write descriptions as if explaining to a colleague:
  • “Test that users can log in successfully”
  • “Verify the shopping cart updates when adding items”
  • “Check that form validation shows appropriate errors”

​
Include Full Context

Provide complete user journey details: Good: “After filling all required fields, click submit and verify the success message appears” Not recommended: “Click submit”

​
Specify Expected Outcomes

Be explicit about what should happen:
  • “User should see their name in the welcome message”
  • “Cart total should equal sum of items plus tax”
  • “Error message should explain what went wrong”

​
Common Test Patterns

​
Authentication

Test login with valid credentials starting from homepage. 
Verify dashboard loads with user's name displayed.

​
E-commerce

Search for 'laptop', apply price filter $500-1500, 
add first result to cart, verify cart shows correct item and price.

​
Form Validation

Submit contact form with empty email field, verify error appears.
Enter invalid email format, check for format error.
Fill all fields correctly, ensure success message displays.

​
Advanced Descriptions

​
Conditional Logic

If promotional banner appears, close it.
If not logged in, perform login first.
When price exceeds $100, verify free shipping badge.

​
Multiple Scenarios

Test pricing page for three user types:
- Anonymous visitors see public pricing
- Free users see upgrade options  
- Premium users see current plan highlighted

​
Error Handling

Attempt checkout with declining card.
Verify helpful error message appears.
Ensure user can try another payment method.
Confirm cart contents preserved.

​
Best Practices

Use Natural Language

Describe elements as users see them: “big blue Get Started button”

Include Visual Context

Specify location: “in the top navigation menu”

Specify Test Data

Be clear about data needs: “use random email address”

Think Like a User

Focus on user goals, not technical implementation

​
AI Capabilities

​
What AI Handles Automatically

  • Element detection from natural descriptions
  • Wait conditions and timing
  • Cross-browser compatibility
  • Self-healing selectors

​
Current Limitations

  • Complex custom widgets may need manual steps
  • Visual regression testing requires additional tools
  • Performance testing needs specialized approaches

​
Refining Generated Tests

After generation, refine with additional instructions:
  • “Wait longer for chart to load”
  • “Also verify sidebar updates”
  • “Test on mobile viewport”

​
Examples by Feature Type

​
User Registration

Test new user signup: Navigate to registration, enter unique email,
create password meeting requirements, complete profile fields,
verify email confirmation, confirm landing on welcome page.

​
Search and Filter

Test product search: Enter 'headphones', apply brand filter,
sort by price ascending, verify results update correctly,
check first result price is lowest.

​
CRUD Operations

Test contact management: Create new contact with all fields,
edit phone number, verify changes saved, delete contact,
confirm removal from list.
AI test generation improves with usage. Start with simple flows and gradually tackle more complex scenarios.