How to professionalize, modify and expand your QA testing flow as a company grows
First post here on the forum, hopefully i'm doing this in the right section! (if not, i'm sorry! Don't shoot me )
I like to start a discussion about how to professionalize the QA flow when a company grows, i've heard there are a lot of experts on the forum in different fields of QA, to me (and hopefully to others as well) it would be really interesting to see some input of experts who maybe already experienced this change.
I want to make it a general discussion so that this could be help full to other people now or in the future.
But of course i also have a real work situation occurring, which i like to show and hopefully there will be great input and tips to adopt the best flow.
Currently i'm working for a SAAS web (software as a service) company which has been growing like crazy in the last year. As we grew we hired more developers, and the current rate is ~ 30 developers - 4 QA engineers. (Needless to say, it's way off and we are currently doing a lot of interviews to find more QA engineers.
Some background about our current flow
-We are using continues development
-ticket(eq bug or feature) > developer fix the ticket > ticket going to tester > code review > live (before we put it live there wil be a final check on a server which is eq to live)
So at this moment, we have manual testers which only test bugfixes and new features.
We are not working with test cases yet, currently we are trying to plan/shape testrail which is the test management software we want to use.
Also we want to have good and reliable Metrics.
And we've started with automated tests, unit testing is done by the developers. And we are using JMeter for stress and load / performance tests.
So i've had a couple of meetings how we need to professionalize our QA situation, for me the tricky part is how to get good metrics with continues development. Also how to plan the testruns and when to execute the testcases.
Hopefully there are people here who would like to share there opinion, expertise or experience with professionalising the QA process.
Also i want to make clear, i did sketched a work related situation but general input which fits this subject are more then welcome, hopefully it will help other people to!
Thanks in advance for reading (& hopefully replying)
(Sorry if there are grammar mistakes in my english, it's not my first language )
hmm not much activity at this forum
Going with Test Case Management (TCM) is a good start.
2nd you want to tighten the change control process. So for any change made, you'll known which test suites to run and be able to focus your regression efforts. Ideally you want to know before any code changes are made, what would be the testing implications. This allows project management to be able to manage which stories get taken in and the associated risk. For example, they may opt to separate large broad underlying changes from a revamp of a specific feature as it would be hard to isolate which problems with one with another.
You mentioned automation. That's a good direction to go. You'll want to tie your automation with your TCM so you can track your automated coverage and be able to correlate the results and metrics between manual and automated. You'll also want to expand your automated test to be runnable on integration servers on code changes, what we call CI (continuous integration).
From there, you want to graduate to the holy grail of software process, CD (continuous deployment). This is where the deployment and testing is 100% automated and from any code check it, it either gets deployed straight to production without any manual steps or the code automatically gets rejected upon any failures.
Thanks David for your input, it's your vision is very helpful!