Requirements
Track business needs, user stories, and acceptance criteria with full traceability to test cases and defects.
What Are Requirements
Requirements represent the business needs, user stories, acceptance criteria, and functional specifications that your software must satisfy. They answer the question: "What must the system do?" Tracking requirements gives your team visibility into what has been tested, what remains uncovered, and how defects impact the overall feature set.
Without structured requirements tracking, teams lose sight of which features have adequate test coverage and which are at risk. TestKase solves this by making requirements a first-class entity in your test management workflow, enabling you to answer critical questions at any point in the release cycle: "Is this feature fully tested?", "Which requirements are at risk due to open defects?", and "What is our overall coverage percentage?"
How TestKase Connects with Requirements
TestKase offers two approaches to requirements management. Choose the one that fits your team's workflow, or use both together:
1. Built-in Requirements
Set the project's requirement integration to TestKase to create and manage requirements directly in the product. Built-in requirements are ideal for teams that want a single platform for test management and requirements tracking. You link requirements to test cases by hand; defects then appear against a requirement automatically, derived from the test cases the two share.
Learn more about Built-in Requirements →
2. External Integration
Connect Jira, GitHub, or GitLab to pull requirements from your issue tracker. Issues from your external platform are read into TestKase as requirements; their titles, statuses and priorities are re-read when you use the refresh control, not pushed live. Linked test cases are written back as comments on the external issue, giving your development team visibility into test coverage without leaving their preferred tool. TestKase does not create or update issues in the external tracker beyond those comments.
Native management
Create and manage requirements directly in TestKase
External sync
Pull requirements from Jira, GitHub, or GitLab and refresh their statuses on demand
Full traceability
Requirement → Test Case → Defect chain
Coverage tracking
See covered, uncovered, and at-risk requirements
Jira Plugin
Two-way test management from within Jira
Attachments
Attach specs, wireframes, and supporting documents
Enabling Requirements
To start using requirements in your project:
- Navigate to Project Settings -> Requirement Integration in the left sidebar.
- Choose the platform. Pick TestKase to keep requirements inside TestKase, or Jira, GitHub or GitLab to read them from an external tracker.
- Save. With the TestKase platform, a Requirements tab appears in the project sidebar.
- You can now create requirements, organize them into folders, and link them to test cases.
Until a requirement integration is configured, creating a requirement or a requirement folder is rejected -- the project has no requirement integration to store them against.
Resetting the requirement integration while the platform is TestKase permanently deletes every requirement and every requirement folder in the project. There is no undo and no confirmation beyond the reset itself -- export your requirements first.
If your team uses Jira, GitHub, or GitLab, configure the integration before creating requirements manually. The integration reads your issues in as requirements, saving you from duplicating work.