Test Republic

Community of Software Testing Professionals

chandrasekhar
  • Male
  • Banglore
  • India
Share
Share on Twitter
Share on Facebook

Chandrasekhar's Friends

chandrasekhar's Groups

chandrasekhar's Discussions

How to find memory leak manually?

Replied Nov. 17, 2008

 

chandrasekhar's Page

Latest Activity

chandrasekhar left a comment for 'Niya'
May 14, 2009

Profile Information

I work for
XYZABC
I work as
QA

Comment Wall (7 comments)

You need to be a member of Test Republic to add comments!

Join Test Republic

At 10:21am on October 20, 2009, Kavitha said…
No.what about you?
At 12:14pm on October 16, 2009, Kavitha said…
Hi..
At 6:54pm on February 21, 2008, chandrasekhar said…
As a Tester How can we scale(I mean efficiency or coverage)of the testcases?
At 5:49pm on February 21, 2008, Jyothi said…
High Priority and Low Severity are issues which donot hamper the functionality of the application, which is not a blocker, for example, On a screen you have a field name different from your requirement, it is low in severity but priority is high as the field name does not match your req document.

Low Priority and High Severity are issues which are blockers, it needs to get fixed immediately for that particular module in the entire application to work, but this issue does not hamper the execution of other modules in the same application.
At 11:27am on February 14, 2008, chandrasekhar said…
Can't we say simple typo Error just before the release as high priority with low severity?
At 11:22am on February 14, 2008, nRashmi said…
High severity with low priority
When U click on “Save” button of the Application after entering the details and found the error msg like “Null point exception”. But still the record or Application is saved in the data base and U can retrieve that application later. This type of error can call “High severity High severity with low priority”. High severity because of “Null point exception” when U click on “Save” button. Low priority is the record or application that U have created is still saved in data base.
At 11:02am on February 14, 2008, nRashmi said…
If the requirement of the functionality by Customer is that they require a Application with “Print”, “Save” and “Cancel” buttons
When U enter Maximum values is all the fields of the Application layout and save the application successfully and U will click on “Print” button
U will find the in print out of the application document the field values(data) are truncated. So if U give max values in every fields of the application. U can’t see all the data enter by U in the print out document or page.
This type of Error(bug) is not effecting the functional flow of the Customer requirement. So this type of error is “Low severity with high priority”. Low severity because it is a GUI Bug and High priority because Customer will not be happy when he/she enters Max data in fields and he can’t see that in the printout copy that effects his business
 
 
 

Test Republic Elsewhere

/></a></p> <p style=

Members

  • Vijayalaxmi
  • Sreethin
  • P.K.Ramya
  • Brian Osman
  • s kumar
  • Shreya
  • APARNA
  • Sanjeev Kumar Singh
  • BIDISHA BAGCHI
  • Ipsita ratha
  • Sapna Nair
  • Gaurav Deore
  • anupam
  • Bhavani
  • Shiva Kumar

© 2010   Created by EDISTA.

Badges  |  Report an Issue  |  Terms of Service