Ask HN: How can I improve my team's approach to internal testing?
I'm an engineer at a company that’s building a SaaS product. We use the product internally as it serves as a productivity tool for some use cases we have. A byproduct of this is that we are always internally testing, like running our own testing sessions for new features/versions or just using it internally to do our work.
When we internally test features we document findings through a Confluence page and then export everything to Jira. If we find an issue in something unrelated to what we are testing then it’s likely we don’t know where it should go. This is the same for when we just use the product ourselves, for example, I end up just not sharing problems because I want to save myself from the hour-long Slack rabbit hole that it puts me in.
I’m keen to know if there’s a way I can make this better for my team or the company as a whole. Or if there are any other ways we can go about assuring quality before releases.
FYI we don’t have QAs, developers are expected to handle that part. We also have automated tests but we still find issues when we take a manual approach, ofc depending on the size of the change.
I would appreciate any and all feedback! Thank you.