Testing that closes the loop.
Quality in the workflow.
Hans creates test cases from Filo cards, supports public token sharing for external testers, and creates bug cards when tests fail. Complete traceability from development through testing to fixes.
Part of the STEa Closed-Loop System
Hans is the Testing & Quality Management module within STEa. Create test cases from Filo cards with one click, execute tests, and automatically create bug cards back in Filo when tests fail. All test outcomes are captured in Ruby documentation. The complete quality loop.
Test Cases FROM Dev Cards
Development drives testing
Create test cases directly from Filo cards. User stories become preconditions, acceptance criteria become test steps, user flows become execution scripts.
Why it matters: TestRail, qTest, Zephyr require manual test case writing. Hans inherits full context from development cards automatically.
Closed-Loop Bug Workflow
Failed tests → Bug cards
When a test fails, create a bug card in Filo with one click. Bug inherits test context, links back to test case. Complete traceability from test to fix.
Why it matters: First-in-industry: Seamless test-to-development feedback loop. No copying between tools. Bugs automatically linked to failing tests.
Public Test Sharing
External testers, no login
12-hour expiring tokens let external testers access test cases without accounts. Share link, testers execute, results auto-import. Perfect for UAT and beta testing.
Why it matters: No other test management tool supports public token sharing. UAT usually requires expensive licensed seats. Hans = unlimited external testers.
App-Specific Test Pages
Organize by product
Dynamic /hans/<app-name> pages filter test cases by app. Track Tou.Me tests separately from SyncFit tests. Per-app pass rates and metrics.
Why it matters: Most tools use projects or folders. Hans uses dynamic routing for instant app-based organization. URL is the filter.
Interactive Test Execution
Check off as you test
Execute tests with interactive checklists. Check off acceptance criteria, add notes, update status (Open → In Progress → Passed/Failed). Real-time collaboration.
Why it matters: Unlike spreadsheet-based testing, Hans provides rich execution UI with status tracking, notes, and automated notifications.
Multi-Tenant Test Isolation
Secure workspace boundaries
Each workspace sees only their test cases. Complete tenant isolation via Firestore security rules. Your test data never mixes with other teams.
Why it matters: Enterprise-grade security from day one. No complex permission configurations. Workspaces are inherently isolated.
Quality without the overhead
Join teams using Hans for seamless development-to-testing workflows.