Basic Workflow
1
Start Recording
Click record and navigate to your application URL
2
Perform Actions
Interact with your application as a user would
3
Add Assertions
Specify what to verify during or after recording
4
Save and Run
Stop recording and execute the test
Recording Interface
Key Components
- Record Button - Start/stop recording session
- Browser Window - Interact with your application
- Action Log - View recorded steps in real-time
- Assertion Panel - Add verifications during recording
What Gets Recorded
Captured Automatically
- Mouse clicks and taps
- Keyboard input and shortcuts
- Form submissions
- Page navigation
- Scroll actions
- File uploads
AI Enhancement
Keystone automatically:- Generates stable selectors
- Adds appropriate wait conditions
- Creates readable step descriptions
- Groups related actions
Adding Assertions
During Recording
Add verifications while recording:- “Welcome message should contain user name”
- “Cart should show 3 items”
- “Submit button should be disabled”
After Recording
Enhance your test with additional checks:- Verify specific text content
- Check element visibility
- Validate data changes
- Confirm redirects
Common Recording Scenarios
Login Flow
E-commerce Purchase
Form Submission
Recording Best Practices
One Flow Per Recording
Focus on a single user journey
Natural Interactions
Interact as real users would
Add Context
Include descriptive assertions
Handle Variations
Record different paths and states
Advanced Recording Features
Conditional Actions
Handle dynamic content:- Close popups if they appear
- Deal with A/B tests
- Handle different user states
Data Parameterization
Make recordings reusable:- Replace hardcoded values with variables
- Generate unique test data
- Use different datasets
Cross-browser Support
Recordings work across:- Chrome, Firefox, Safari, Edge
- Different screen sizes
- Various operating systems
Post-Recording Optimization
AI Processing
After recording, Keystone:- Optimizes selector strategies
- Adds intelligent waits
- Groups related steps
- Parameterizes test data
Manual Refinement
You can:- Edit step descriptions
- Adjust timing
- Add additional assertions
- Configure data handling
Handling Dynamic Elements
Smart Element Detection
Keystone uses multiple strategies:- Text content matching
- Relative positioning
- ARIA labels
- CSS selectors
- XPath fallbacks
Self-healing Tests
Tests adapt to:- Minor UI changes
- Different loading times
- Content variations
- Layout shifts
Recording Tips
Before Recording
- Plan your test scenario
- Prepare test data
- Clear browser state
- Disable notifications
During Recording
- Move at normal speed
- Wait for pages to load
- Include all necessary steps
- Add assertions as you go
After Recording
- Review all steps
- Add missing verifications
- Test the recording
- Save with descriptive name
Common Issues and Solutions
Timing Problems
- Let pages fully load before interacting
- Add explicit waits for dynamic content
- Use assertions to verify readiness
Element Selection
- Click center of elements
- Use unique identifiers when possible
- Avoid coordinates-based actions
Data Dependencies
- Use fresh test data
- Clean up after tests
- Handle existing data gracefully
Examples by Feature Type
Authentication
Record login once and reuse:- Standard login
- Social authentication
- Multi-factor auth
- Password reset
Shopping Cart
Test cart functionality:- Add/remove items
- Update quantities
- Apply discounts
- Calculate totals
User Profile
Validate profile management:- Update information
- Upload avatar
- Change settings
- Verify saves
Recording is ideal for capturing complex user flows quickly. For precise control over individual steps, consider building tests manually.

