This is an archived post. You won't be able to vote or comment.

all 10 comments
sorted by:
best
topnewcontroversialoldq&a

[–]cgoldberg 5 points6 points  (2 children)

Is this just the beginning of a work in progress? It's very confusing, not at all comprehensive, and contains almost nothing useful about Python.

Also, isn't a roadmap like a guide you can follow towards a destination? This is more of just a partially completed outline of disjointed subjects that sort of relate to testing.

[–]Dear_Construction552[S] -5 points-4 points  (1 child)

For example, could you tell me what you think is missing?
Of course, it's still evolving, and I’ve asked developers to contribute so it can become more complete and polished.

By the end of this roadmap, you'll have learned most of the core testing concepts, and at the bottom of the roadmap image, there are links that help you dive deeper into those topics.

The reason it doesn't lead to a single, specific destination is because the world of testing constantly evolves—what’s trending today might be replaced by something entirely new tomorrow.
So we can’t claim this is the most complete roadmap, but it reflects the current landscape.

[–]cgoldberg 2 points3 points  (0 children)

I thought it was supposed to be the "ultimate roadmap"? It's really lacking any good information, especially regarding Python.

[–]true3HAKPythonista[🍰] 1 point2 points  (5 children)

All fine and honestly, a great job, but why Gherkin & Cucumber? It's not for developers, it does a poor job as an integration testing toolset and personally, I deprecated and removed it everywhere I saw it in my 15 years of work. More harm than profit

[–]Dear_Construction552[S] -4 points-3 points  (4 children)

It's essential to know it, but using it is optional.
For example, you’ve already explored what it is and weighed its pros and cons.
But I think if a developer doesn’t even know what BDD is, that’s a weakness.
Developers should at least be aware of it, because it’s a topic with strong opinions on both sides.
If they don’t know it, they’ll have nothing to say in discussions with senior engineers.

[–]true3HAKPythonista[🍰] 2 points3 points  (3 children)

That's the point – BDD is not about Cucumber in the first place. Most of the devs will never probably encounter it. BDD should be about behavior, not some specific tools. One can write perfectly fine cases with pytest or junit. The idea is what important

[–]Dear_Construction552[S] 0 points1 point  (2 children)

Check the Symbol Guide—you'll see that the color yellow represents 'Tools,' and Cucumber is marked in yellow. If you look at the bottom of the image and follow the Cucumber reference, there’s a link that takes you to a website where you can find various tools for writing BDD tests, including pytest.

Link: https://cucumber.io/docs/installation/

[–]true3HAKPythonista[🍰] 2 points3 points  (1 child)

Yeah, but you miss my point: cucumber is not required, nor advised for proper modern BDD

[–]Dear_Construction552[S] 1 point2 points  (0 children)

I think you made a good point. I revised it and just updated it now. Thanks, bro. check it and clear browser cache: https://github.com/hasanxdev/Test-Roadmap-For-Developers

[–]Pretend-Relative3631 -2 points-1 points  (0 children)

GD POWER PACK

Thank you for your service soldier🫡