tag:blogger.com,1999:blog-7722108.post5116341073517350094..comments2024-03-28T12:11:07.539+05:30Comments on Thinking Tester: Connection between Software Metrics and NewsShrini Kulkarnihttp://www.blogger.com/profile/10782753752478547381noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7722108.post-79062797434877721512014-06-04T22:39:21.400+05:302014-06-04T22:39:21.400+05:30I agree with you it is totally game of number play...I agree with you it is totally game of number playing.But software testing totally change the software scenerio.You can view payroll software products chennai online also.Eilisys Technologieshttps://www.blogger.com/profile/10405654635091485933noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-3921545707238381602014-06-04T22:36:00.339+05:302014-06-04T22:36:00.339+05:30You post great blog about software testing.It give...You post great blog about software testing.It gives great information about software testing.If some one is searching for payroll software products chennai can get it through online.Eilisys Technologieshttps://www.blogger.com/profile/10405654635091485933noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-83275064286115298442014-01-12T23:08:17.796+05:302014-01-12T23:08:17.796+05:30Sandeep - your question needs longer response - I ...Sandeep - your question needs longer response - I will do it in a post<br /><br />short answer is numbers by their nature - allow people to make various interpretations.<br /><br />when we tell a qualitative narration (say a story) using numbers - they come into perspective.<br /><br />that in my opinion is the right use of numbers (metrics)<br /><br />ShriniShrini Kulkarnihttps://www.blogger.com/profile/10782753752478547381noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-1202256098694551632014-01-11T18:46:31.952+05:302014-01-11T18:46:31.952+05:30Hi Shirin,
You are right..there is other side of...Hi Shirin, <br /><br />You are right..there is other side of story. It's not always necessary that we have to play with "number" just to make a senior level "Stakeholder" happy. <br /><br />IMHO, once test team identify true "Objective" of collecting data for a "Metrics" to a relevant "Audience", only then we can achieve something valuable.<br /><br />What is important is how we analyze the information after looking at the Metrics. <br /><br />For example, Within internal team of 10 testers, working on 10 different modules, the team decided to provide information of "Test Coverage" and related "Defect Density Distribution (Severity wise)" on weekly basis. Now we have total ten iterations and in 3rd iteration we looked at the Metric and found....<br /><br />Coverage seems good per module say 40% but high severity Functional defects not present or only a few low severity defect are present ---- Analyze it (IMO) from this point of view<br /><b> 1. Shouldn't we look back at our test cases and find out if they really cover High Risk Areas or not </b> <br /><b> 2. Have we deployed balanced amalgamation of test techniques with the help of Functional and Technical testers which can surface defects in early STLC </b><br /><br />I don't think, it is always about "What we decided to show" and then present accordingly to make someone happy. In a team where delivering good quality is an "Objective", team ask questions to itself through the information from Relevant and Important "Testing Metrics" and then look at Test Strategy, Plan and Design accordingly.<br /><br />Let me know what do you say and correct me If I am wringSandeepnoreply@blogger.com