Selection Strategies
Strategies control how chunks are selected and grouped during test generation.Available Strategies
| Strategy | Description | Use Case |
|---|---|---|
SequentialStrategy | Process all chunks in order | Complete coverage |
RandomSamplingStrategy | Sample random chunks multiple times | Diverse test sets |
SequentialStrategy
The default strategy - processes all chunks sequentially into a single dataset.When to Use
- Complete test coverage needed
- Testing all documentation sections
- Regression testing
RandomSamplingStrategy
Randomly samples chunks multiple times to create diverse test datasets.Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
num_samples | int | Required | Number of datasets to generate |
chunks_per_sample | int | Required | Chunks per dataset |
seed | int | None | None | Random seed for reproducibility |
When to Use
- Cross-validation test sets
- Diverse coverage sampling
- Large documentation with limited budget
- Randomized testing
Combining with Conversation Mode
Strategies work with both independent queries and conversation mode:Sequential + Conversations
Random + Conversations
Examples
Full Coverage
Generate tests for entire documentation:Cross-Validation Sets
Create multiple test sets for evaluation:Budget-Constrained Generation
When you can’t test everything:Comparing Strategies
Best Practices
Use Sequential for Regression Testing
Use Sequential for Regression Testing
Complete coverage ensures no section is missed:
Use Random for Large Documentation
Use Random for Large Documentation
Sample strategically when full coverage isn’t practical:
Set Seed for Reproducibility
Set Seed for Reproducibility
Always set a seed for consistent results:
Match Strategy to Use Case
Match Strategy to Use Case
- CI/CD: Sequential for full coverage
- Development: Random for quick feedback
- Evaluation: Multiple random sets for statistical validity