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
I recently passed this exam, after some light-core studying, over maybe three to four weeks, I wasn't preparing all that intensively but considering what is recommended by a lot of people. I prepared more than I needed to prepare, I like to play it safe. A lot of people have been asking me how I prepared for the exam so that gave me the idea to put together this blog post with a few tips. Since this is an entry-level exam it's not too hard, compared to more specialized certification exams. It covers the basic cloud literacy and basic knowledge about Microsoft Azure, its services, and products. If you're new to IT or planning a change of career, this might give you a nice boost of confidence, if this is the case it makes take you a bit more to get acquainted with all the terms that will be new to you, but a few weeks of studying should suffice. On average, one or two weeks should be ample enough to prepare for this exam. The exam topics (at the time I'm writing this) are
Thank you.
ReplyDelete