Getting started
Overview
What are Templates?
Templates save your preferred AI model, test count, coverage level, and other settings for instant reuse.
- Save time by storing your favorite generation settings
- Ensure consistency across test generations
- Create templates for different testing scenarios
- Share templates with your team (coming soon)
- Track usage and identify your most-used configurations
Templates vs. Manual Configuration
Without templates, you must configure model, count, and coverage for every generation. Templates apply all settings with one click, saving time and ensuring consistency.
Key benefits
Why use the template system?
Time Savings
One-click configuration instead of multiple selections
Consistency
Same settings across similar test generations
Organization
Categorize templates by testing type
Reusability
Duplicate and modify existing templates
Step-by-step
Creating Templates
Organization
Template Categories
Understanding categories
Organize templates by testing type for easy filtering and selection.
Functional
Core features, user workflows, business logic testing
Security
Authentication, authorization, encryption, vulnerability testing
Performance
Load testing, stress testing, response times, scalability
Integration
API testing, third-party services, data exchange
Regression
Existing functionality validation, release verification
Accessibility
WCAG compliance, screen readers, keyboard navigation
Choosing the right category
Select the category that best matches your primary testing goal. Use "Other" for cross-cutting templates or unique scenarios.
Category-specific recommendations
Suggested settings for each template category.
Recommended Settings:
Model: Claude Sonnet 4.5 (balanced)
Count: 15-20 test cases
Coverage: Comprehensive
Edge Cases: On
Negative Tests: On
Deep dive
Configuration Settings
Operations
Managing Templates
In practice
Using Templates
Applying templates in Test Generator
Use templates to speed up test case generation.
Standard workflow:
- Go to the Test Generator page
- Enter or select your requirements
- In the template section, click the template dropdown
- Select a template
- Settings auto-populate
- Adjust if needed (optional)
- Generate test cases
What happens when you select a template:
- AI Model field is set automatically
- Test Case Count is pre-filled
- Coverage Level is selected
- Edge Cases toggle is configured
- Negative Tests toggle is configured
- Usage count for that template increments
Settings remain adjustable
Template application is non-destructive. You can override any setting before generating without affecting the saved template.
Template + Requirement workflow
Combine templates with saved requirements for maximum efficiency.
Power user workflow:
- Create templates for different testing scenarios (Functional - Standard, Security - Exhaustive, etc.)
- Save requirements for features you test repeatedly
- In Test Generator: Select requirement → Select matching template → Generate
- Complete generation in ~5 clicks instead of ~15 manual selections
Efficiency multiplier
Teams using templates + requirements report 70% faster test generation setup times.
Finding templates
Organization & Search
Quality
Best Practices
Effective template management
Strategies for building and maintaining a useful template library.
✅ Do
- Use clear, descriptive template names
- Add descriptions explaining when to use
- Categorize accurately for easy filtering
- Create templates for recurring patterns
- Review and update templates periodically
- Delete unused templates to reduce clutter
❌ Avoid
- Generic names like "Template 1"
- Creating too many similar templates
- Forgetting to categorize properly
- Using wrong coverage for security testing
- Keeping outdated model selections
- Creating one-off templates you'll never reuse
Naming conventions
Consistent naming makes templates easier to find and use.
Suggested patterns:
[Category] - [Scope] - [Coverage]
Example: "Functional - E2E Flows - Comprehensive"
[Feature Type] - [Model] - [Count]
Example: "API Security - Opus - 50 tests"
[Use Case] - [Quick/Thorough]
Example: "Regression Testing - Quick"
Recommended template set
A starting set of templates that covers most needs.
1. Quick Validation
Haiku 4.5, 5 tests, Standard coverage - for rapid smoke tests
2. Standard Functional
Sonnet 4.5, 15 tests, Comprehensive - for typical features
3. Security Testing
Opus 4.5, 30 tests, Exhaustive - for critical paths
4. Regression Suite
Sonnet 4.5, 20 tests, Comprehensive - for release testing
5. Performance Baseline
Sonnet 4.5, 10 tests, Standard - for load testing
Maintenance schedule
Keep your template library healthy and useful.
Regular maintenance:
- Monthly: Review unused templates (usage count = 0)
- Quarterly: Update model selections to latest versions
- When models update: Create new templates with latest models
- After project changes: Adjust test counts based on quota usage
FAQ
Frequently Asked Questions
Help
Support
Getting help
Resources for template-related assistance.
Contact options:
- Email: support@synthqa.app
- Use the feedback button in your dashboard
- Visit our knowledge base for template examples
When requesting template support:
- Describe what you're trying to achieve
- Share your current template configuration
- Explain what's not working as expected
- Include template ID if reporting a bug
Last updated: January 2026 · Guide version: 1.0