ianahilario

First things first, what does a "bug" mean in the software development process? A bug is what we call a behavior that is different from what's expected based on the provided requirements. A tester's main purpose is to find and report bugs in the system as early as possible. In some companies, it's sometimes called a "defect". They actually mean slightly different if we go by the book. In this post, I'll be covering the lifecycle of a software bug which are issues that are found during the development phase. You're testing the system and you found a bug. What is the first thing you do? a) You immediately write a bug report b) You try to reproduce it c) You complain "How could this very obvious bug reach QA? Dev should've spotted this earlier ugh." The formal answer is B (I'll just let you figure out what's the informal answer), It's common for a QA to be gaslighted. "I cannot reproduce this bug.", "It doesn...

Are you familiar with Sudoku? It's a number puzzle that challenges your logic. It's a 9x9 grid where composed of sets of 3x3 tiles. Initially, the grids are pre-filled with a few numbers and the goal is to fill each grid, row, and column with numbers from 1-9 without duplication. Screenshot from Wikipedia Requirements analysis is a crucial task that a QA must do well for this is the pillar of the project's testing outcome. We must immerse ourselves in the requirements specifications, clear out any unclearness or uncertainty in the expected results, think of any possible specifications that were missed, consider how it might work with other features, and imagine different scenarios that an end user could do. Now how does this task compare with Sudoku? Empty cells in grids Requirements, no matter how the product owner/business analysts try to polish it the best as they can, will always have something that a tester might think is missing or unclear. This is like us looking at ...

You'll be surprised to know how broad the testing industry is. Of course, we can break it down into manual and automation testers/test engineers. But there are also different types of test classifications such as functional testing, regression testing, performance testing, accessibility testing, localization testing, etc. For automation you have a lot of frameworks and approaches you can explore as well. Fail to plan and you plan to fail We don't test all the time, or at least literally. For a successful test to happen, we should have a good test plan, design, and process in place to ensure everything will run smoothly when we do that actual testing work (which is the test execution phase). Examples: Test Plan and Strategy. This is an important process especially when you're testing a project for the first time. It gives you a space to think about what and how to test the product overall. Some topics covered are testing timeline, testing type and approaches, defect manageme...