JuniorLearnsToCode

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...

Most of the time, when people hear the term "software testing" the first thing that comes to mind is just that - testing some software, which usually involves reporting a lot of bugs, designing test cases, doing exploratory testing sessions, working on automated checks, etc. But, there are a lot of other ways in which a tester can contribute to the overall quality of the product. So what exactly would proactive thinking be, from a tester's perspective? A tester does not have to be just a bearer of bad news, as a tester sees the system as a whole and gets plenty of chance to interact with it, the said tester can also gain a lot of useful insight into the system. One of the most important aspects of our job is to provide information, sometimes that information needs to be distilled down into more succinct formats, but also, a tester should proactively act on the information he/she gains.  Just because you might not find any obvious bugs in a feature you're testing it do...

Test oracles and heuristics can be considered as "meta" aspects in software testing, often we can be in a position where we are using them without being aware of the "official" definitions. In short, an oracle is a way of deciding whether our test has passed or failed - most commonly express by using terms such AR/ER, Actual Result, and Expected Result.  Heuristics can be viewed as a rule of a thumb, a guiding principle, the "official" description goes like this:  " A heuristic, or heuristic technique, is any approach to problem-solving or self-discovery that employs a practical method that is not guaranteed to be optimal, perfect, or rational, but is nevertheless sufficient for reaching an immediate, short-term goal or approximation. " Heuristics can be applied to various testing activities, but are especially useful in exploratory testing, as they are broad and generic enough to be applicable in a variety of different situations.  And lastly, M...

This is another blog post inspired by  Bloggers Club June 2021 - if you are a tester (or interested in testing) be sure to check out the Ministry of Testing, it's wonderful community of smart and helpful people and their forum (called the Club) is great place to get help, get inspired and to discus stuff to stimulate those little grey cells. This month's topic idea appealed to me straight away. I try not to have regrets, per say, but there I decisions from the past that, from today's perspective, I would have made differently. If I could, pretty much only thing I would have done differently is that I would have left support sooner (I worked in tech support for about two and a half years) and gotten into testing sooner. I spent a lot of time trying to find myself, I was learning WordPress and doing freelance consulting, learning Angular, React, PHP, Java, .NET/C# and other development technologies, mostly (but not exclusively) front-end oriented. I recently  blogged about ...