Import Your Own Test Cases

Already have test cases written? Skip generation and go straight to review & live execution.

We'll read your file, extract what's already there, and show you exactly what we found for you to check and correct — nothing is generated or invented, and nothing is executable until you confirm it on the next screen.

Access code Application under test Test cases file(s) .docx, .xlsx/.xlsm, .pdf, .txt or .csv — a table works best, but a list or short prose description per case is fine too. You can select more than one file if your test cases are split across several documents. Requirements document (optional) If you'd like a best-effort traceability check (which requirements your test cases appear to cover), attach your requirements document here. This is an AI-inferred match, not a guarantee — your test cases were written independently, so we're matching them after the fact. Process flow diagram(s) (optional, for custom-built applications) If this is a custom-built application, you can attach flow/screen diagrams so we can read the process flow alongside your requirements. Your name or initials (optional) Lets you filter to just your own runs later in Run History if your team shares one access code.

Processing usually takes a few seconds for a well-structured spreadsheet, or up to a minute for a document that needs to be read case-by-case.

Your uploaded file is processed securely and is not stored beyond this review session — only the confirmed test cases you approve are kept.

← Back to Req2QA