I think every tester face a situation when he gets a new feature, then he identifies test cases (or test scenarios) and then he needs to decide what should be automated and what to automate first. In this article, I’d like to share my way of prioritizing test cases and choosing what to automate.
(more…)
I took a part in a RedHat internal CTF challenge run by Keith Swagler and the Red Hat Information Security Team last year. Many awesome and interesting challenges, but I’d like to write about the “bse64” challenge. Along with that I’ll take a closer look at the base64 encoding itself and explain some basics.
(more…)
Your teammate asks you to review his Pull Request. But what should you check and don’t miss anything? Here is my quick checklist for Reviewer.
(more…)
Your code is ready; you are about to push the button “Create Pull Request”! But it’s time to think a bit if your code is good enough for reviewing and doesn’t contain any silly mistakes. Here is my checklist for those who are going to create a Pull Request.
(more…)
It’s not rare to use Pull Requests in test teams nowadays. But to make the process of reviewing Pull Requests more enjoyable and expected, you need a set of rules or recommendations. So it’s a kind of a contract of communication between team members in area of Pull Requests. I’d like to share the rules we use in our team and which help us to be effective during Pull Requests review. These rules are highly depend on a team and a company, also I would emphasize that it’s not a law and you need to use these rules wisely.
(more…)
What does Junior need to properly review Senior? Let’s take a look closer to this question and understand what it takes to become a good reviewer and submitter.
(more…)Pytest 3.5 has released! Many console options have been added to this version. Strongly recommend to read about these options and apply their to your work 🙂
(more…)