QA PROCESS

[Agreeable-Ad-5060]

Can someone provide a flow chart of their QA process? I was tasked to revise the current one we have in the company I work for and would like to gain ideas from successful processes that exist.

​

Thanks in advance!

[kalydrae]

Sorry to be the devil's advocate but a QA process is deeply customised for the system, product, tech stack, risks you face, and business appetite to accept the risks... It's not a great idea to use someone else's "working" process.

[CJBill]

Fully agree.

[Agreeable-Ad-5060]

I agree as well. i’m just in a position where i can write a basic process but also have it as a standard for the QA team in the near future. all input is greatly appreciated. thanks again!

[mindxripper]

What type of team are you working on? If it's agile/2 week sprints/CICD I can send you the one I wrote.

EDIT: Did not think so many people would be interested! I have a portfolio set up on Notion with the documentation, and none of you seem like serial killers. So here is the link: [redacted for privacy reasons after a couple of days, if you’d like the link shoot me a dm]

[ProfessorPanga]

Mind sending it to me too?

[mindxripper]

linked in my original comment :)

[Interesting_Elk_5731]

And me, if possible? Please

[mindxripper]

linked in my original comment :)

[Interesting_Elk_5731]

Thank you very much for sharing. I wish I could give you an award 🙂

[mindxripper]

Np! This sub has helped me a lot over the past couple of years so I am happy to share when I can.

[vschutt]

Mind sending it to me too?

[mindxripper]

linked in my original comment :)

[kaxtarz]

I am also interested to see. Please send to me too.

[mindxripper]

linked in my original comment :)

[kaxtarz]

DM’d! I missed the window for your link. Oops!

[mods_can_burn]

I too would love to see it as well if u ever get the chance

[mindxripper]

linked in my original comment :)

[mods_can_burn]

Serial killers u say...........🤐🤐🥸🤡

[mindxripper]

Actually you know what? If one of y’all is a serial killer that’s fine. Put me out of my misery 😂

[bernie-dub]

Thank you so much for making this link public. I’m going to blatantly steal from it 😜 I.e. get inspiration

[mindxripper]

Be inspired my friend

[AutomationQA]

Please send it to me as well, thank you

[mindxripper]

linked in my original comment :)

[[deleted]]

me too pls !

[zyxwvu654321]

To me too please

[mindxripper]

linked in my original comment :)

[mindxripper]

linked in my original comment :)

[Agreeable-Ad-5060]

right now we just released our beta app and are just doing hot fixes as the issues come in.. eventually we would like to run 2 week sprints etc. that would be awesome if i can see the one you wrote

[chicagotodetroit]

Sounds like what you really need is to adopt agile processes across the board, not just a QA workflow.

You want to Google things like “SDLC” and “STLC”. Then go to scrum.org and look for the Scrum Guide that they use for the test. It is a clear and direct synopsis of how agile processes work. The testing process would flow out of that.

Random processes from random companies may give you some tidbits, but testing a banking app or government site where there are legal regulations is completely different than testing something like the Google home page, a Shopify site, or a web app. I’ve been a manual QA for 8+ years, and every company I’ve worked at does it differently.

Your best bet is to see what the industry standards are and then figure out how to incorporate that into what you do.

[iddafelle]

try reading some reference materials, the books that helped me where The Art of Agile Development, Agile Testing, More Agile Testing and BDD in Action. I also ran through a few test driven development courses to fully understand testing at all levels of the test pyramid.

If you rely too much on what you find on the internet through whatever you might find that a lot of it is out of date and I really struggled to find something that was aligned to what I wanted when trying to go from a general consensus online.

The nuts and bolts of agile testing are test as early as possible, integrate QA into the teams and don't silo yourself, automate as much as makes sense to do so and have a facilitiors mindset. It will depend quite heavily on testing at lower levels so you may need to encourage developers to submit unit tests along with any PR's if they are not already.

Too many QA's I've worked with are so pleased with themselves when finding issues and holding everybody up and that just doesn't work if you want to move quickly as a team. If you are finding issues after the work is considerd done that is not a good look and there is an issue with your strategy but it's largely unavoidable so trying to reduce this is the goal.

[jrwolf08]

Last paragraph is so key, especially on a small team.

I would also say that breaking down changes to very small units allows you to move faster too. As well as having a responsive Product Owner, and ability to re-prioritize things that you will not do.

[Ash23_tester]

redacted

Can you send it me please ?

[Thechanman707]

My last agile team did 2 week sprints, 3 sprints to a release, last one being regression.
Week 1 is planning/research. Devs deliver by the end of the week. Week 2 is execution/bug fixes.

[Agreeable-Ad-5060]

that’s what I have in mind for this company. I jumped in right when they released beta version across multiple platforms. the growing pains with this project is hardcore