A Chrome extension that generates Gherkin (Cucumber) and Manual test cases from JIRA ticket descriptions using AI — either a local Ollama model or Google Gemini. Generated tests can be pushed directly to JIRA or imported into Xray Cloud.
*.atlassian.net)chrome://extensions/extension/ folder from this repositoryThe TestScribe icon will appear in your Chrome toolbar.
Ollama runs entirely on your machine. No API key, no data sent to the cloud.
Download from ollama.com and install it for your OS.
ollama pull qwen2.5-coder
Why
qwen2.5-coder? It is optimised for structured code and specification output, which produces better Gherkin and manual test tables than general-purpose models.
Chrome extensions send requests with an Origin: chrome-extension://... header. Ollama blocks these by default and returns 403 Forbidden. You must allow extension origins before TestScribe can reach Ollama.
launchctl setenv OLLAMA_ORIGINS "*"
Then restart Ollama from the menu bar icon (click the Ollama icon → Quit, then reopen).
sudo systemctl edit ollama.service
Add the following inside the file that opens:
[Service]
Environment="OLLAMA_ORIGINS=*"
Save, then restart the service:
sudo systemctl daemon-reload
sudo systemctl restart ollama
Open PowerShell and run:
[System.Environment]::SetEnvironmentVariable("OLLAMA_ORIGINS", "*", "User")
Then restart Ollama from the system tray (right-click → Quit, then reopen).
Alternatively, set it via the GUI: System Properties → Environment Variables → New User variable
OLLAMA_ORIGINS*Restart Ollama after saving.
http://localhost:11434 — leave as-is unless you changed Ollama’s port)qwen2.5-coder (or whichever model you pulled)Go to aistudio.google.com/app/apikey and create a key.
TestScribe automatically selects the best available Gemini Flash model.
Groq provides extremely fast cloud inference for Llama 3, DeepSeek, and Mixtral models.
Go to console.groq.com/keys and create a free API Key.
llama-3.3-70b-specdec or llama3-8b-8192)Connect to any service hosting models that mirror the standard OpenAI API structure (such as LM Studio, DeepSeek API, or OpenRouter).
http://localhost:1234/v1 for LM Studio, or https://api.deepseek.com/v1 for DeepSeek./models API.If you use Xray Cloud for test management, TestScribe can import tests directly.
In your JIRA instance, go to: Apps → Xray → API Keys (or use the Settings link inside TestScribe)
Create an API key pair and copy the Client ID and Client Secret.
https://yourcompany.atlassian.net/browse/PROJ-123)TestScribe helps teams maintain consistent Gherkin phrasing across their test suite.
To use step consistency, go to Settings ➔ Integration and click Sync Steps Library.
Test in your selected projects. It filters specifically for Cucumber (Gherkin) test issues, parses their scenario definition lines into individual steps, and stores them in the extension’s local storage. Manual test types are ignored.Once synced, TestScribe leverages this local dictionary in two ways:
Given / When / Then) to compare your generated steps against the library:
\(\text{Similarity} = \frac{|A \cap B|}{|A \cup B|}\)
Matches are highlighted: Green for high similarity ($\ge 80\%$) and Yellow for medium similarity ($\ge 50\%$).| Error | Cause | Fix |
|---|---|---|
403 Forbidden |
Ollama CORS not configured | Set OLLAMA_ORIGINS=* — see Fix CORS above |
Ollama unreachable |
Ollama is not running or wrong host | Start Ollama; check the host URL in Settings matches your Ollama port |
No models found |
No models pulled yet | Run ollama pull qwen2.5-coder |
Gemini API Key missing |
Key not saved in Settings | Open Settings → Gemini tab → paste key → Save |
| Popup opens but no JIRA data | Not on a JIRA browse page | Navigate to a ticket URL (/browse/PROJ-123) first |
| Tests not appearing | Generation failed silently | Open the popup’s DevTools console (right-click popup → Inspect) for details |