Downloads · 30 days
11
37% of all-time downloads
yashi29/qa-engineer-v1
qa-engineer-v1 is a text generation model from yashi29. Use it when you need the model to write or continue text. It is set up for transformers.
QLoRA fine-tune of unsloth/qwen2.5-3b-instruct-unsloth-bnb-4bit, trained to write software test plans like a 6-7 year experienced QA engineer. This checkpoint is merged (LoRA folded into the base weights) -- loadable…
Downloads · 30 days
11
37% of all-time downloads
All-time downloads
30
Public
Parameters
3.1B
6.2 GB on disk
Likes
0
Public
Click a slice to open those files.
.safetensors6.2 GB · 100%
From the Hugging Face model README
QLoRA fine-tune of unsloth/qwen2.5-3b-instruct-unsloth-bnb-4bit, trained to write software test plans like a 6-7 year experienced QA engineer. This checkpoint is merged (LoRA folded into the base weights) -- loadable directly with transformers, no PEFT or Unsloth required at inference time. See requirements.txt in this repo for the minimal inference dependencies.
Prompt the model with this fixed instruction followed by a software requirement:
You are a senior QA engineer with 6-7 years of professional testing experience. Given the following software requirement, produce a comprehensive, well-structured test plan. Your response MUST use exactly these Markdown section headings, in this order: ## Requirement Summary & Assumptions, ## Missing Requirement Suggestions, ## Risk Analysis, ## Functional Test Cases, ## Negative Test Cases, ## Boundary Value Test Cases, ## Edge Cases, ## Security Test Cases, ## API Test Cases, ## Performance Test Cases, ## Accessibility Test Cases, ## Cross-Browser / Device Test Cases, ## Test Data Suggestions. For the API Test Cases section, write 'Not applicable — no API surface described in this requirement.' if the requirement is purely UI-only. Each test case must be written as: **TC-<PREFIX><NN>: <Title>** followed by a short bulleted list with Preconditions, Steps, Expected Result, and Priority (High/Medium/Low). Use ID prefixes: F for functional, N for negative, B for boundary, E for edge, S for security, A for API, P for performance, AC for accessibility, X for cross-browser/device.
Output is a fixed 13-section Markdown test plan (Requirement Summary & Assumptions, Missing Requirement Suggestions, Risk Analysis, Functional/Negative/Boundary/Edge/Security/API/Performance/Accessibility/Cross-Browser Test Cases, Test Data Suggestions).
data/versions/v1/train.jsonl (60 examples)Scored on 25 held-out benchmark items, blending rule-based checks with a local LLM judge (8 rubric categories, 0-10 each).
| Category | Score (0-10) |
|---|---|
| Functional Coverage | 7.79 |
| Edge Case Coverage | 4.23 |
| Security Coverage | 3.85 |
| Negative Test Coverage | 6.08 |
| Requirement Understanding | 9.08 |
| Missing Requirement Detection | 7.16 |
| Output Consistency | 1.15 |
| Formatting Consistency | 5.71 |
| Overall | 5.63 (56.3%) |
Inherits the base model's license -- check unsloth/qwen2.5-3b-instruct-unsloth-bnb-4bit before any commercial use.