Guide to QA best practices

Growing as a product manager Leadership
, ,
1

Does anyone have a great guide to QA best practices? Because of the small size of our team, we have to spread QA around to include some team members that aren’t “technical” in nature and it’s been causing some issues.

3 Likes
2

Are you looking to get more technical QA members or just find a way to make it work with the non technical folk ?

3 Likes
3

Great question, I really need to make it work with the non-technical folk, and I think have a more solid procedure in place is the best route.
For context, I come from the marketing side of things and have a strong technical basis for things related to marketing and web development, but am fairly new to running a software development team.
I inherited the current procedures which are basically just check to make sure the AC is met and mark it as passed or revised, there isn’t a lot of structure to it.

2 Likes
4

I find it useful to have several steps depending on the size of what you’re deploying specially for non technical—
small- medium:

  1. Conduct my own internal test which involves comparison against exit criteria and user stories. Going through the scenario end to end even if it’s just a small add on feature, make sure your happy path, medium and worst path continue to function, all alarms and data are recorded, etc.
  2. Host user acceptance testing- this is when i get non technical folks involved and I create a rubric and guide of scenarios they need to test
  3. Production end to end testing.

Large

  1. Same as number 1 but make it your internal team effort.
  2. Bug bash which is a larger version of number 2- usually company wide or spans multiple verticals and needs to be more organized, so prepare for how they can submit feedback, prioritizing feedback, creating tickets, incentives just in case, etc.
  3. Prod end to end testing
    End to end testing for me is including flows that are related to what you launched so for example:
    You added a new marketing event that needs to be tracked, the elements to that would be:
  • Are we tracking for both native and web?
  • Are the right data objects appended?
  • Are we successfully sending the events back to vendors?
  • Are we ingesting the data?
  • Does it fit into the ETL schema?
  • Are we getting the right attribution for that event?

So I will likely mimic a user by

  • Doing a paid path- click on an ad,
  • Do a bunch of events (signup, convert, etc.).
  • See realtime if the event is firing,
  • Check dw if the data stored,
  • Check vendor dash if the data was sent.

Hope that helps…

1 Like
5

@Jesus I’m also super interested in this topic and doing some research currently. If you find something great, please share :slightly_smiling_face:

6

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.