Why Project matters?
Product Name: Treeify Version: 0.2-beta Date: 2025.07.10
Setting up your project correctly ensures that Treeify tailors test case generation to your domain, goals, and testing context. It directly affects accuracy, coverage, and efficiency.
🏭 Industry
Treeify uses your selected industry to activate domain-specific knowledge and terminology.
Why it matters:
- Adds context-aware understanding (e.g., “claim submission” in insurance vs. “order placement” in e-commerce)
- Reduces hallucinations by grounding tests in real-world processes
Example:
In Healthcare, Treeify knows to check HIPAA-related access and audit rules.
🧪 Testing Type
Choose the testing focus area, such as:
- Functional
- Performance
- Security
- Compatibility
- API
- More Coming In
Why it matters:
- Helps the AI decide what kind of test objects and scenarios to generate
- Enables focused validation across relevant dimensions
Example:
If you select Performance Testing, Treeify will prioritize test objects like response time, concurrent users, and throughput.
🔄 Testing Stage
Define whether you're at:
- Requirement validation
- Integration testing
- System-level verification
- Regression testing
Why it matters:
- Adjusts the granularity and scope of tests
- Aligns generated tests with your current QA phase
Example:
During System Testing, Treeify generates more end-to-end flows vs. unit-level checks.
⚙️ Generation Strategy
Choose how broad and deep the AI should explore:
- Strict: Generate test cases strictly based on your input. Most accurate, but may miss implicit coverage.
- Complement: Allows AI to infer and supplement missing cases using industry/domain patterns. Broader scope, higher credit usage.
Why it matters:
- Impacts credit usage and depth of generation
- Complement mode is more exhaustive but may include lower-priority tests
Tip:
🧠 Use Standard for scoped QA with detailed and precise requirements inputs; Complement when preparing for testing without detailed requirements inputs.