u/Mr502i

Hi everyone,

I've been working on VeriOps, an open-source QA test management platform designed for teams that want a self-hosted solution.

Current features:

• Project management
• Test case management
• Test execution and test runs
• Defect tracking
• Role-based access control
• Project-level permissions
• AI-generated test cases from requirements and user stories
• Local AI support (self-hosted models)
• Docker deployment

One feature that has been particularly useful is AI-assisted test case generation. Instead of manually creating repetitive positive and negative scenarios, VeriOps can generate structured test cases directly from requirements while keeping everything inside your environment when using local models.

Tech stack:

• FastAPI
• React
• TypeScript
• PostgreSQL
• Redis
• Docker

GitHub:
[https://github.com/CipherLogicX/veriops\](https://github.com/CipherLogicX/veriops)

I'm looking for feedback from QA engineers, test leads, and open-source contributors.

What would be the most important feature for your team before considering a QA management platform?

Over the last few months I've been building VeriOps, an open-source QA management platform.

What started as a personal project quickly turned into a deep dive into how QA teams actually manage test cases, test runs, defects, permissions, reporting and collaboration.

A few things surprised me:

• Most teams use far fewer workflow states than tools provide.
• Permissions become complicated much faster than expected.
• Test execution is often more important than advanced reporting.
• Simplicity is usually preferred over feature overload.

For QA engineers and test leads:

What is the one feature you can't live without in your current QA tool?

And what is one feature that most QA tools overcomplicate?

I'd love to hear real-world experiences and compare them with what I've seen while building VeriOps.

Over the past few months I've been building VeriOps, an open-source QA management platform.

The original goal wasn't to compete with TestRail or any other tool. I mainly wanted to understand what QA teams actually need in their day-to-day work.

A few things surprised me:

- Many teams use only a small subset of defect statuses.
- Complex permission models become difficult to maintain very quickly.
- Test execution workflows matter more than most reporting features.
- Smaller teams often prefer simplicity over extensive traceability.

For QA engineers, test leads, and managers:

What features do you rely on every day?

What features do existing QA tools overcomplicate?

I'm trying to understand whether my experience matches what other teams are seeing in practice.