Some software Testers may get tired of a long career in testing or do not want to pursue a career technical career, such as becoming an automation specialist, or a developer. Such software testers can go on to become product owners, business analysts, scrum masters, project (program or product) managers, or engineering managers. There are many other non-technical roles to choose from, but here I will focus on the most common ones. Let us explore these non-technical career options and dive into the details of each of them. Final remark before we go on: even though these roles seem non-technical, each of these roles benefits if the tester has a technical background, and most contemporary testers do. Product Owners As a tester often you would think about in what way would a customer use a product, and how a particular functionality could be made easier for the customer to use. As a product owner, you would be able to influence those kinds of decisions - after all the product owner is the
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
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