Skip to main content

​
Overview

AI Credits are the currency that powers Supatest’s AI features. Each AI-powered action consumes credits from your monthly allocation. Understanding credit usage helps you optimize your testing strategy and budget.
AI Credits

​
Credit Costs

Different AI features consume different amounts of credits:
FeatureCredits per UseDescription
AI Action1 creditExecute complex browser interactions with AI
AI Extract1 creditExtract data using natural language
Visual Assertion1 creditAI-powered visual verification
Auto-Healing1 creditAutomatic test repair when locators break
AI Chat (Global)2 creditsCreate tests via conversation
AI Chat (Test Case)2 creditsModify tests via conversation
Generate AI Logs1 creditAI-generated failure explanations
Enhance Test Steps1 creditAI suggestions for step improvement
Import Test Generation1 creditGenerate tests from imports
AI Credits Usage

​
Managing Credits

​
Viewing Credit Balance

Access your credit information from Settings > AI Credits:
  • Current balance: Credits remaining this period
  • Usage history: Breakdown by feature and date
  • Reset date: When credits refresh
Credits reset at the start of month.

​
Optimizing Credit Usage

​
Use AI Strategically

Reserve AI features for scenarios where they provide the most value: Good use of AI credits:
  • Complex, multi-step interactions (AI Action)
  • Dynamic content extraction (AI Extract)
  • Visual verification of layouts (Visual Assertion)
  • Automatic recovery from UI changes (Auto-Healing)
Consider traditional steps for:
  • Simple clicks on stable elements
  • Form fills with known selectors
  • Basic text verification
  • Navigation to fixed URLs

​
Balance AI and Traditional Steps

Mix step types based on element stability: 
Step 1: Navigate (traditional) - URL is predictable
  URL: {{ env.BASE_URL }}/login

Step 2: Fill (traditional) - Input has stable selector
  Locator: input[name='email']
  Value: {{ env.TEST_EMAIL }}

Step 3: AI Action (AI) - Complex CAPTCHA or MFA
  Prompt: Complete the authentication challenge

Step 4: Verify Visibility (traditional) - Dashboard element is stable
  Locator: .dashboard-header

​
Reduce Unnecessary AI Usage

  1. Use Extract Value over AI Extract when selectors are stable
  2. Fix locators manually instead of relying solely on auto-healing
  3. Write specific assertions instead of broad visual assertions
  4. Batch AI Chat requests to reduce message count

​
Monitoring Usage

​
Usage Dashboard

The AI Credits page shows:
  • Daily usage graph: Credits consumed per day
  • Feature breakdown: Which features consume most credits
  • Trend analysis: Usage patterns over time

​
Usage Alerts

Set up alerts to monitor consumption:
  1. Go to Settings > AI Credits
  2. Enable usage notifications
  3. Set threshold percentage (e.g., 80% consumed)
  4. Receive email when threshold is reached

​
High Usage Scenarios

​
Test Suites with Many AI Steps

If a test suite consumes many credits:
  1. Audit AI step usage across tests
  2. Replace AI steps with traditional steps where possible
  3. Consolidate multiple AI Actions into single prompts
  4. Consider if auto-healing can be disabled for stable tests

​
AI Chat Heavy Usage

If AI Chat consumes significant credits:
  1. Write detailed prompts to reduce back-and-forth
  2. Use recorded tests as a base, then modify with AI
  3. Create test templates to reduce generation needs

​
Auto-Healing Consumption

If auto-healing uses many credits:
  1. Fix frequently healing locators permanently
  2. Use more stable selector strategies
  3. Add data-testid attributes to your application
  4. Review and accept healing suggestions promptly

​
Credit Exhaustion

When credits are exhausted:
  • AI features disabled: AI Action, AI Extract, Visual Assertion, AI Chat become unavailable
  • Auto-healing disabled: Tests fail instead of auto-healing
  • Traditional steps continue: All non-AI steps work normally
  • Credits reset: Wait for monthly reset or upgrade plan

​
Emergency Options

If you run out of credits mid-cycle:
  1. Upgrade plan: Increase your allocation immediately
  2. Purchase add-on: Buy additional credits for the current cycle
  3. Wait for reset: Credits refresh at billing cycle start

​
Best Practices

​
Plan Your AI Usage

  1. Identify AI-critical tests: Mark tests that require AI features
  2. Reserve credits: Keep buffer for auto-healing and debugging
  3. Schedule AI-heavy tests: Run them when credits are fresh

​
Track ROI

Measure the value of AI credits:
  • Time saved by AI vs manual test creation
  • Reduced maintenance from auto-healing
  • Faster debugging with AI logs

​
Team Coordination

For team plans:
  • Set guidelines for AI feature usage
  • Review high-consumption tests together
  • Share credit-saving tips across team