For most testers, designing, executing, and maintaining test cases are regular activities, this is especially true for new testers and those in the early stages of their career. This post is inspired by some documentation I worked on, in an effort to standardize the testing process in one of my previous jobs. Bear in mind that in each company the approach to handling test cases can differ significantly, old-school (Waterfall-like) enterprises might favor very long and detailed test cases, where each step required to execute the test cases is described in great detail, to more Agile environment where testing is moving at a faster pace, so test cases in Agile are shorter and more concise. There is a great course at the MoT on this topic called Optimising Manual Test Scripts For An Agile Environment , by Match Archer, the course is not too long and it's full of useful info, I'd highly recommend it. There is also a third alternative - no test cases at all! This has been a trend in
Full honest disclaimer: I haven’t used many no-code automation tools, and the ones I’ve used have always been just out of curiosity, and I never went deep into any of those tools until now. I’m a QA who’s mainly focused on working with coded test automation frameworks and never had much time to look into such tools. So when the folks from testRigor approached me with a question if I would like to try out their tool, I was curious although a bit skeptical. While in the past I disregarded any no-code automation tools, as I didn’t have a need for them, in more recent years I’ve become more open to the idea of giving such tools a try. There is a time and place for everything, and coding a complete automation framework can be a waste of resources - unless you produce it exceptionally specific in terms of testing. Hence, you need to utilize all the customization that is available to you. One of the reasons I changed my mind about tools like this one, was the fact that a couple of people in
Here are the three things that have helped my testing career: Building good relations with people I work with - from personal experience, is what has helped me the most in my career. People remember if they enjoyed having you as their team member and working alongside you. I always advocate that you should be polite and considerate towards everyone you work with, and never burn bridges behind you, as you never know when a previous co-worker can be your future co-worker as well, when you change companies. I got quite a few referrals from previous co-workers when they moved to new companies, and I recommended people who I worked with, so it goes both ways! Learning Continuously - about 5-6 years ago I tried hard to make a habit of trying my best to learn something new (almost) every day, the reason for this is because I'm lazy, and on the other hand people say consistency is the key to learn new things. If you spend 30 minutes daily learning test automation, in a year you will know
Comments
Post a Comment