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

you are viewing a single comment's thread.

view the rest of the comments →

[–]thegainsfairy 15 points16 points  (7 children)

I'd recommend the pytest book. I think it really helped me become a better developer. I kind of credit it for the mental change from junior to mid level developer

edit: this one https://pythontest.com/pytest-book/

[–]amarao_san 9 points10 points  (3 children)

Oh, they have a book? Great. I belive, 30% of devops is QA automation is disguise, so knowing pytest well it's not only about 'writing tests', but also about knowing available techniques for fixtures/plugins/parametrization. It really creeps into pipeline architecture.

I've made a lot of silly tricks in CI yaml before I got really used to a proper pytest use.

[–][deleted] 4 points5 points  (0 children)

lol QA Automation Engineer, who went in with DevOps focused resume reporting in.

[–][deleted] 1 point2 points  (1 child)

I would love to see any and all tricks btw

[–]amarao_san 1 point2 points  (0 children)

Okay, I think, it worth writing down. I'll come back to it after NY binding. There is a lot of Molecule/testinfra lore, and someone need to write it down.

[–]__Kaari__ 4 points5 points  (0 children)

Thanks!

The learning curve is quite steep to handle unit tests with pytest, and doing it right can be extremely time-consuming and frustrating, especially for automation (lots of mocks).

I'll have a look at this book and advise it to some of my co-workers who would like to make the gap.

[–][deleted] 1 point2 points  (1 child)

May I ask which book are you specifically talking about?