Setting a Learning path for freshers in Software QA

🙋 Questions
, , , ,
1

If you were tasked with setting a learning path for Freshers in Software QA, what skills, tools, processes and certifications would you recommend?

I have created a small example of what I think should be a good learning path to give a basic platform and orientation to newbies (refer attachment).

Basically, the path can be divided into five main categories:

  • Skills (Coding, Soft Skills)
  • Tools (Automation frameworks, Testing Tools, CI/CD)
  • Cloud Technologies (Cloud hosting, tools, Cost Management)
  • Processes (Agile processes, Agile Test Management, Metrics)
  • Certifications

I’d love to have your opinion too.
Software QA Roadmap (1).pdf (156.6 KB)

4 Likes
3

I always wonder why it’s a linear thing and automation has to be in it.
I don’t see automation as a “need” for growth, you can grow without it also.

Not every tester has to do automation (looking at the pdf) just my 2 cents.
I would never create a growth “path” as a “path” but more like a tree.

But the things that are on it, are good choices still :slight_smile:

I’m also always pretty curious about the security testing (being someone who does pentests & bug bounty), what does it really mean because security is so broad.

4 Likes
4

I like the map but a couple of constructive comments:
Mastering step 1 implies you’re ‘only’ an 11th of the way through a roadmap. In reality though, you could spend 20 years on step 1 and still be learning!
Second comment - I couldn’t see a single mention of BUGS! We love bugs, it’s our reason for getting up in the morning - hunting them, isolating them, categorising them and assigning them… perhaps every single stage in the roadmap is dedicated to finding these little critters?

3 Likes
5

I always wonder why it’s a linear thing and automation has to be in it.
I don’t see automation as a “need” for growth, you can grow without it also.

@kristof
I agree. From my POV, the purpose of making the path is mostly to make newbies aware of all aspects of Software testing, and automation is definitely one of the core aspects. You can’t be a software tester and not be aware of Cloud concepts, Automation, Performance and Security testing.

1 Like
6

Second comment - I couldn’t see a single mention of BUGS!

@danuk
Yep! I assume that would be covered in the software testing bootcamp, along with all other basic fundamentals of the software development / testing process.

But valid point. I really look forward to constructive and observant critiques like this. Keep 'em coming.

7

I would suggest adding a category for “domain”, that is specific to the practitioners current company or project. Not just knowledge and skill in the product itself, but the market it operates in.

So for a banking app, it would include branches above financial compliance in the regions the app operates, awareness of competitors in the banking space, trends in banking. And more general trends and insights into mobile apps, device testing, how data connections of mobile devices impacts end user performance and introduces risk, security topics specific to banking bad mobiles.

2 Likes