I'm doing a lot of QA in my startups. There are several layers:
1. One model (Opus) writes a code, another model (Sonnet, Qwen, Kimi) writes unit tests using requirements and code;
2. Full code review by me. Just to understand what is going on in the codebase;
2. Integration tests are running with PlayWright MCP. Another model validates UI per requirements;
3. Substantive runtime tests prepared by me or human QA team. All features should be included into testing, plus regression testing of existing features, plus edge cases.
QA in AI era becomes more important than coding skills. So keep it in a good shape.
Everyone is QA at a startup. I hope y'all are using your own product regularly right? You should have a nice simple way to raise these issues, maybe a slack channel or something with a convenient way to turn a screenshot into an item in your todo/work system if you have one. Encourage product ownership.
Alternatively, if you don't really care about the product, everyone is also customer support at a startup - you should be quickly be able to solve regressions that customers raise. I hope that at least you are talking to your customers and are very responsive to them at a startup.
You'd be surprised. Every software application has bugs. If customers are willing to give you money despite bugs that's a very string signal in favour of your product.
I'm doing a lot of QA in my startups. There are several layers: 1. One model (Opus) writes a code, another model (Sonnet, Qwen, Kimi) writes unit tests using requirements and code; 2. Full code review by me. Just to understand what is going on in the codebase; 2. Integration tests are running with PlayWright MCP. Another model validates UI per requirements; 3. Substantive runtime tests prepared by me or human QA team. All features should be included into testing, plus regression testing of existing features, plus edge cases. QA in AI era becomes more important than coding skills. So keep it in a good shape.
Everyone is QA at a startup. I hope y'all are using your own product regularly right? You should have a nice simple way to raise these issues, maybe a slack channel or something with a convenient way to turn a screenshot into an item in your todo/work system if you have one. Encourage product ownership.
Alternatively, if you don't really care about the product, everyone is also customer support at a startup - you should be quickly be able to solve regressions that customers raise. I hope that at least you are talking to your customers and are very responsive to them at a startup.
I second this.
Everyone does QA at a startup. There is no dedicated QA. If you're a developer, you're doing QA. Product, whatever your job title is, you're doing QA.
Even the customer does QA.
And very soon no longer a customer
You'd be surprised. Every software application has bugs. If customers are willing to give you money despite bugs that's a very string signal in favour of your product.
The investors doing QA too
I guess usually using things like sentry or having a close conversation with customers.
Use https://github.com/vostride/agent-qa you don't need a QA team just ask coding harness to write tests and you can review the test runs.
QA should not be done by the same entity writing code.
Is there any AI Agent do it ?
Yes - https://github.com/vostride/agent-qa