tag:blogger.com,1999:blog-756591017857898160.comments2023-06-18T03:27:33.650-07:00Chippie Tester - Learning isn't optionalSeanhttp://www.blogger.com/profile/08618839778898252749noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-756591017857898160.post-42776379648065956622020-07-17T21:11:13.055-07:002020-07-17T21:11:13.055-07:00Great content.Thank you so much for sharing.
Java ...Great content.Thank you so much for sharing.<br /><a href="https://www.acte.in/java-training-in-chennai" rel="nofollow">Java training in Chennai </a><br> <br /><a href="https://www.acte.in/java-training-in-bangalore" rel="nofollow">Java training in Bangalore</a><br> <br /><a href="https://www.acte.in/java-training-in-hyderabad" rel="nofollow"> Java training in Hyderabad</a><br><br /><a href="https://www.acte.in/java-training-in-coimbatore" rel="nofollow"> Java Training in Coimbatore</a><br><br /><a href="https://www.acte.in/java-training" rel="nofollow">Java Online Training</a>aarthihttps://www.blogger.com/profile/17456043390101722326noreply@blogger.comtag:blogger.com,1999:blog-756591017857898160.post-12447997615310378532019-09-26T00:59:32.723-07:002019-09-26T00:59:32.723-07:00Thank you so much for this nice information. Hope ...Thank you so much for this nice information. Hope so many people will get aware of this and useful as well. And please keep update like this.<br /><br /><a rel="nofollow">Various Stages of Game Testing Techniques you need to know</a><br /><br /><a rel="nofollow">7 Essential Tips for Successful QA Implementation</a><br /><br /><a rel="nofollow">Types of Game Testing Processes that need to be followed</a><br /><br /><a rel="nofollow">How Game Testing differs from Software Testing</a><br /><br /><a rel="nofollow">6 Challenges that every Game Tester Faces</a><br /><br /><a rel="nofollow">9 Critical Bugs to be Identified in Game Testing process</a><br /><br /><a rel="nofollow">Is the age of AAA gaming dying?</a><br /><br /><a rel="nofollow">Major Mobile Game Testing Concerns for Testers</a><br /><br /><a rel="nofollow">Game Testing Trends to watch out for in 2020</a>Deepikahttps://www.blogger.com/profile/06317348843516098953noreply@blogger.comtag:blogger.com,1999:blog-756591017857898160.post-91015612100676063592019-05-29T04:18:42.143-07:002019-05-29T04:18:42.143-07:00Woah this blog is wonderful i like studying your p...Woah this blog is wonderful i like studying your posts. Keep up the great work! You understand, lots of persons are hunting around for this info, you could help them greatly.<br /><a href="https://www.gangboard.com/database-training/oracle-dba-training?utm_source=backlinks&utm_medium=cmt&utm_campaign=coursepage&utm_term=oracle&utm_content=oveiya" rel="nofollow">oracle online training</a><br />oveiya krishnasamyhttps://www.blogger.com/profile/13355223706227340906noreply@blogger.comtag:blogger.com,1999:blog-756591017857898160.post-8939831333534395152015-10-21T01:17:24.504-07:002015-10-21T01:17:24.504-07:00Thank you Ainars, I really appreciate your feedbac...Thank you Ainars, I really appreciate your feedback.<br /><br />- bugs found late (when we could have found them earlier)<br />* What is late? <br />If you want a success criteria of "Find bugs in time", then you have to understand what 'in time' is for the context of your change.<br />Is 'in time' dependent on the developer remembering the code they changed? or is 'in time' before the project is released?<br />* Why were the bugs found late? and why/how could they be found earlier?<br />Testing isn't just about 'exercising code'. Are the test analysts getting involved early? are their discussions happening about requirements?<br />To say that a bug was found too late, you have to understand the root cause of it. Was it bad requirements? bad understanding? bad coding?<br />- Why is your code sitting around for weeks?<br />* Ultimately it boils down to: When is the best time to find bugs for the success of the project?<br />Probably as early as possible right?<br />But, you also want the biggest bugs as early as possible? which is why you have to ask the 'What bugs are critical to the project's success' question. <br />I'd suggest you could add another question under 'Did I find defects in the product?', along the lines of 'Did testing activities help to find product defects early?'<br /><br />- bugs reported but never fixed for whatever reason<br />A test analyst will almost always be able to find some bug in a product if they look hard enough.<br />Understanding which factors influence 'the projects success' helps to focus testing activities, and this inherently affects the defects that get raised. Defects raised should be those which will adversely affect the project's success.<br />Who makes the call on what gets fixed in your project?<br />Maybe instead of logging a bug, the test analyst should ask the stakeholder to review the bug they've found before it goes to the developer to fix?<br />This will feed into the focusing of testing activities on finding defects which matter.<br />This is where the question 'What bugs are critical to the project's success?' is powerful.<br /><br />- bugs fixed that does not really matter to any stakeholder<br />If bugs are getting fixed that 'do not matter' - something is wrong with the defect prioritisation in the project.<br />Just because we find a defect, doesn't mean it needs fixing.<br />If it doesn't matter to any stakeholder, then the test analyst isn't asking the question: 'What bugs matter most to it's stakeholders?'<br /><br />Thank you again for your feedback. I really appreciate it.Seanhttps://www.blogger.com/profile/08618839778898252749noreply@blogger.comtag:blogger.com,1999:blog-756591017857898160.post-2263638709641726542015-10-20T04:22:23.849-07:002015-10-20T04:22:23.849-07:00Great article! I searched in a lot of sites and fi...Great article! I searched in a lot of sites and finally I found something that could show me the metrics clearly. Congrats!Bárbara Cabralhttps://www.blogger.com/profile/02390338542133153077noreply@blogger.comtag:blogger.com,1999:blog-756591017857898160.post-16711311163440176822015-10-06T05:29:45.699-07:002015-10-06T05:29:45.699-07:00Nice overview. I tend to agree. I have a recommend...Nice overview. I tend to agree. I have a recommendation however - to complete the picture you should not just consider what "help the delivery", but also things that interfere/<br />hinder team and software delivery as a result:<br />- bugs found late (when we could have found them earlier)<br />Rationale: it is easier for developer to fix code he has just broken compared to one untouched for weeks<br />- bugs reported but never fixed for whatever reason(duplicate/not a bug/won't fix/low priority...)<br />Rationale: we waste our time reporting. Developers waste their time reading and analysing bug. Not to mention impact on morale/attitude. <br />- bugs fixed that does not really matter to any stakeholder (but we and even they don't know about it)<br />Rationale: we spent time fining a bug that would never bug anyone in production, or at least they would be perfectly fine using workarounds available<br /><br />Ainars.<br />Anonymoushttps://www.blogger.com/profile/16707171813598953725noreply@blogger.com