Skip to main content
Before Orizon QA selects files or runs the AI, you choose a goal. Goals define what kind of output you want and automatically configure file selection and analysis settings to match. This keeps the setup fast and ensures the AI focuses on the code that matters for your specific task.

​
Available goals

The goal selector appears at the top of the analysis form, above the file picker. Goals that have matching files in your repository are shown as selectable cards; goals with no relevant files are hidden.
Generate unit tests for UI components.Selects component and hook files. Edge cases are enabled by default. Generates test cases formatted for your detected test framework.Generated tests can be executed directly in the browser when your project uses a JavaScript/TypeScript framework.
Generate integration tests for API endpoints.Selects API route files. Edge cases and security tests are both enabled by default, making this goal well-suited for catching both functional gaps and security issues in your API layer.Generated tests can be executed directly in the browser.
Generate unit tests for utility functions.Selects utility and model files. Edge cases are enabled by default. Ideal for ensuring helper functions and shared logic behave correctly across boundary conditions.Generated tests can be executed directly in the browser.
Generate tests for all code files.Selects components, hooks, API routes, utilities, and models — the broadest coverage of any goal. Edge cases and security tests are both enabled. Use this when you want a comprehensive starting test suite for a new or under-tested codebase.Generated tests can be executed directly in the browser.
Generate user stories and acceptance criteria.Selects component, API, and utility files. Produces user stories in the standard As a / I want to / So that format with acceptance criteria checklists. Does not generate executable test code.
Generate complete QA documentation.Selects all file categories. Produces user stories, test cases, and acceptance criteria together. Edge cases and security tests are enabled. Use this goal when you need a full QA artifact package — for example, before a release or audit.
Manually select files and configure all options.No files are auto-selected and no configuration defaults are applied. You pick the files and set every option yourself. Use this when none of the predefined goals match what you need.
Selecting a goal completely overrides the current configuration — it does not merge with previous settings. This prevents leftover values from earlier runs affecting your new goal’s output.

​
Switching goals with an existing file selection

If you change your goal after you’ve already selected files, Orizon shows a confirmation banner. You can either:
  • Accept — replace your current file selection with the new goal’s recommended files
  • Keep — keep your existing file selection and apply only the goal’s output configuration

​
Configuration options

After selecting a goal, you can fine-tune the analysis in the configuration panel.

​
Test framework

Choose the framework Orizon uses to format generated test code:
OptionWhen to use
GenericLanguage-agnostic test cases without framework-specific syntax
JestJavaScript and TypeScript projects
PytestPython projects
JUnitJava projects
Orizon detects languages from your selected files and shows recommended frameworks at the top of the list.

​
Output toggles

These toggles control which types of content the AI generates:
  • Include edge cases — adds boundary conditions, null inputs, and unexpected states to test cases
  • Include security tests — adds tests for common vulnerabilities such as injection, authentication bypass, and input validation
The API Tests and Full Test Suite goals enable both edge cases and security tests by default because API surfaces are the most common attack vectors.

​
Additional context

You can provide free-text instructions to guide the AI — for example, naming a specific area to focus on, describing a constraint, or asking for tests in a particular style.

​
Smart Config Panel

The Smart Config Panel gives you three modes for configuring output:
Orizon scans your selected files, classifies them by category (components, API routes, utilities, etc.), and automatically configures the output. You see a summary of how many categories will be analyzed and a confirmation that configuration is ready.Use Easy mode when you trust Orizon’s defaults and want to get to results quickly.
The Smart Config Panel also shows a token estimate for your current configuration — the approximate number of tokens the analysis will consume, along with an estimated cost. This updates in real time as you change your file selection or configuration.

​
How auto-selection works

When you select a goal (other than Custom), Orizon maps the goal’s file categories to files in your repository. The mapping works like this:
GoalFile categories searched
Component Testscomponents, hooks
API Testsapi
Utility Testsutilities, models
Full Test Suitecomponents, hooks, api, utilities, models
User Storiescomponents, api, utilities
QA Documentationcomponents, hooks, api, utilities, models
Files are classified by their path and extension. For example, files under app/api/ or routes/ are treated as API files; files under components/ or ending in .component.* are treated as component files.