Jignasha Patel’s Post

Life of a QA in the Indian IT industry... 1. Perform testing for a full day and find bugs. 2. The developer fixes all of them in a few minutes, because "ek chota sa code missing tha, jiski wjh se sab issues mile.." 3. Test again everything, next full day and confirm, things are working fine. 4. In the meantime, the developer pushes some new changes again. 5. go to step 1. 😊

Life of a QA in the Indian IT industry... 1. Perform testing for a full day and find bugs. 2. The developer fixes all of them in a few minutes, because "ek chota sa code missing tha, jiski wjh se sab issues mile.." 3. Test again everything, next full day and confirm, things are working fine. 4. In the meantime, the developer pushes some new changes again. 5. go to step 1. #QA #Software developer

Second part of how we do things in QA team now is live! https://lnkd.in/dckw_YYn 5 months is not much since previous article, right? First one is still there: https://lnkd.in/dC2xG4t2

Nope! Nope! Nope! Nope! I agree with all. Especially with: "Fresh eyes find bugs" 🪲 BUT! A QA team means QA is added as a new step after deployment, slowing it down, causing features to bounce back. You are missing a crucial point! The whole reason to even attempt to ditch QA as a role is not only to save money (that would be a very shallow decision), but to keep the engineer accountable of testing so that a tested feature is only pushed out the door. KEEP THE QA! DON'T DITCH IT! But don't create silos by having a QA team. Blend it in! Have the QA engineer in your product team.

QA are the kind of people who love asking a lot of questions. Sometimes they can be annoying, but they do it for the good of the project! A #QAengineer knows what can interact with what, understands the consequences of functional and logical errors, and asks questions from the perspective of an ordinary user: how will the system behave next? What will the user do? If the user does this, where will they go? During a session of questions, logical errors in the product often come to light. Therefore, #ruleoflifeofkvchk: 👉 The more questions, the better. And the earlier QA starts asking questions and finding flaws in the product, the less money the client will spend on fixing errors later. Think about it☝️

Bug Life Cycle New: The bug is reported. Assigned: Assigned to a developer for resolution. Open: The developer starts working on it. Fixed: The developer resolves the issue. Retest: QA team retests the fix. Closed: The bug is verified and closed. Reopen: If the fix fails, the bug is reopened. #SQA #softwarequalityassuarance #QA #software #manualtesting

I might get all eyes on me for saying this but- QA's job is much more than just spotting bugs! Honestly, that's just scratching the surface.  The role of QA? It's a whole universe beyond mere bug spotting. Let's dive into this: 👉 They make using software nice and easy. QAs work hard so that when you use an app or a program, it feels smooth, like your favorite easy chair. They make sure everything feels just right. 👉 They're all about good quality. It's not just about catching mistakes. QA makes sure everything in the software works great and makes sense. They want you to have a good time using it. 👉 They save time and money. By finding problems early, QA helps avoid big headaches later. It's like noticing a small hole in your roof and fixing it before it rains. This saves a lot of trouble and money. 👉 They keep users happy. When software works well and feels good, people like using it. Happy users mean a good name for the brand. QA helps make sure users smile and keep coming back. So, next time you hear "QA," think big. It's about making software not just bug-free, but also a joy to use. What other tasks do QAs perform? #qa #qajobs #qaengineer #bugs

Life of QA Engineer. Finds 100 bugs and made them fixed but no one cares, Unintentionally missed 1 Bug, Everyone be like what do you do all day. Was this not the part of your test cases. How you can miss this🤷 was this not the part of your test cases😔 NOTE - Quality is everyone's responsibilty. #softwaretest #testers #testing #tester_life #QA_Engineer #QA

Improving the User Experience with #QA QA procedure normally starts during the development stage and lasts the entire lifecycle of the product. Usually, it entails these 8 actions that are important to understand: 1: Establish testing goals and objectives 2: Strategize Testing 3: Create test cases 4: Conduct Testing 5: Find Bugs & record them 6: Prioritize and fix bugs 7: Retest and Release 8: Monitor and Maintain #QA #Goals #Testing

I might get all eyes on me for saying this but- QA's job is much more than just spotting bugs! Honestly, that's just scratching the surface.  The role of QA? It's a whole universe beyond mere bug spotting. Let's dive into this: 👉 They make using software nice and easy. QAs work hard so that when you use an app or a program, it feels smooth, like your favorite easy chair. They make sure everything feels just right. 👉 They're all about good quality. It's not just about catching mistakes. QA makes sure everything in the software works great and makes sense. They want you to have a good time using it. 👉 They save time and money. By finding problems early, QA helps avoid big headaches later. It's like noticing a small hole in your roof and fixing it before it rains. This saves a lot of trouble and money. 👉 They keep users happy. When software works well and feels good, people like using it. Happy users mean a good name for the brand. QA helps make sure users smile and keep coming back. So, next time you hear "QA," think big. It's about making software not just bug-free, but also a joy to use. What other tasks do QAs perform? #qa #qajobs #qaengineer #bugs