Very often, when applying to jobs you may get a task to test an app you're not familiar with, or you might not know who to start testing the product on your new job. In these situations, you can try to use heuristics (general rule of thumb) if you are unfamiliar with the application's domain. For the issues you do find, try to think about the from the user's perspective: is something blocking (like login or registration being completely broken) you completely from accessing the rest of the app? Is an issue annoying, but you can work around it? Is it a minor glitch or a text typo? To help conceptualize this approach you can use Personas-based testing. Here is a list of some techniques that can be helpful for testing most apps. For a lot of apps, you can use the CRUD approach to testing: Can you create resources, like registering for an account? Can you read data, like opening website pages without issues? Can you update data, such as changing your username? Can you delete
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
The International Software Testing Qualifications Board (ISTQB) offers a range of certifications for software testers. The important thing to note is that the CTFL (Certified Tester Foundation Level) certification is the prerequisite that unlocks all other ISTQB certifications. Getting ISTQB certified can have several benefits, so let’s have a look at the situation. Benefits : Validation of knowledge: The ISTQB certification exams test a candidate's knowledge of the software testing process, including test design, test management, and test techniques. By passing the exam, the candidate demonstrates that they have a certain level of knowledge and understanding of software testing. It’s a good way to show that you know the terminology and possessed the required theoretical knowledge of software testing. Career advancement: Many companies require or prefer candidates with ISTQB certification for software testing positions. The certification can help a candidate stand out in a competit
Comments
Post a Comment