Skip to main content
Codebase analysis is the core workflow in Orizon QA. You connect your code — by pasting it, fetching it from GitHub, or uploading files — and the AI generates test cases, user stories, and acceptance criteria tailored to what it finds. Analysis runs in parallel chunks so large codebases complete quickly, and every run is saved to your history so you can revisit, resume, or re-run it at any time. The flow is goal-first: you pick what you want to generate before selecting files. Orizon uses your chosen goal to automatically select the right files from your repository, so you spend less time configuring and more time reviewing results.

​
Input methods

There are three ways to get your code into Orizon QA. Each is suited to a different workflow.

Paste code

Paste any snippet or file contents directly. No repository connection required — ideal for quick checks or isolated functions.

GitHub repository

Browse your public or private GitHub repositories, pick a branch, and select files or folders to analyze. Files are cached locally in your browser for fast re-analysis.

Upload files

Upload individual source files or a ZIP archive. Useful when your code is not on GitHub or you want precise control over what gets analyzed.

​
Goal-first analysis flow

Instead of selecting files and then deciding what to generate, Orizon asks you what you want first.
1

Choose a goal

Select from predefined goals such as API Tests, Component Tests, User Stories, or Full Test Suite. Orizon uses your goal to determine which file categories are relevant.
2

Files are auto-selected

Based on your goal, Orizon automatically checks the files that match — API route files for API Tests, component files for Component Tests, and so on. You can override the selection manually at any time.
3

Configure and analyze

Adjust the framework, toggle edge cases or security tests, and click Analyze. Results stream back in real time.
4

Export or execute

Copy results to your clipboard, download in your preferred format, or run the generated tests directly in your browser.
Switching goals after you’ve already selected files shows a confirmation banner. You can choose to keep your current selection or let Orizon replace it with the goal’s recommended files.

​
Framework support

Orizon generates test code formatted for the framework your project uses. Supported test frameworks include:
FrameworkLanguage
JestJavaScript / TypeScript
PytestPython
JUnitJava
GenericLanguage-agnostic (plain test cases)
For BDD workflows, you can export any generated test cases as Gherkin feature files compatible with Cucumber and Behave. See Output Formats for the full list of export options.

​
What’s in this section

Input Methods

Paste code, connect GitHub, or upload files — and how browser caching works.

Goals & Configuration

Available analysis goals, framework settings, and the Smart Config Panel.

Output Formats

Markdown, JSON, Jira/Xray, TestRail, Azure Test Plans, Gherkin, and more.

History & Caching

Browse past analyses, resume interrupted runs, and manage file caches.