[cena]

1.If the customer requirements are changing continuously as a tester how you are going to manage the situation? Suppose you have prepared test cases but still some more time is required to receive the build in between time what you can do? How you know the bug you sent is fixed or not?

a.If the customer changing the reqs ... : If the change came in between the testing time of previous requirement ( change) then i can stop testing and intimated to my TL... if the change came after completion testing of prev change then i can go for testing .. I think in this situation we can't do anything like reporting to PM or any except doing testing for new changes.. at present we doing like this only.. coz all the risk analysis, cost estimations are already done by PM and given it for testing..

b.Suppose you have.... : In between we can review test cases ( by me or peer).. try to prepare effective test cases , or can test application upto completion part if possible...

c.How you know..... : 1. Daily we check the BTS for bug status

2. Actually we sent a mail with bugs to concerned developers to fixed, he revert back with status of bugs, then we can go for re testing.

3.If using any test management tool, if automatic email configuration is configured then concerned tester should receive a conformance email that the bug is fixed...

2.What is Test Summary Report ? What are its contents, its format and fields
a.Test summary report gives the status of Testing by us,it is nothing but daily report regarding testing .
b.It consists of different columns based on the company.Some of the columns are
c.Test case field
d.No.of test cases executed
e.No.of pass
f.No.of fail
g.Pass percentage
h.Fail percentage
3.What is Test Incident Report ? What does it all contain ? What is its format and fields..?
4.What is complaince testing on web applications
a.Conformance testing, also known as compliance testing, is a methodology used in engineering to ensure that a product, process, computer program or system meets a defined set of standards. These standards are commonly defined by large, independent entities such as the Institute of Electrical and Electronics Engineers (IEEE), the World Wide Web Consortium (W3C) or the European Telecommunications Standards Institute (ETSI).
b.
c.Conformance testing can be carried out by private companies that specialize in that service. In some instances the vendor maintains an in-house department for conducting conformance tests prior to the initial release of a product or upgrade. In the software industry, once the set of tests has been completed and a program has been found to comply with all the applicable standards, that program can be advertised as having been certified by the organization that defined the standards and the corporation or organization that conducted the tests.
5.What are the most common bugs that we find on a daily basis in web based testing. Also can some one give examples of high priority real time bugs and how they solved them?
6.what are the different categories in which the bugs are grouped under in general
7.what is the process of bug fixing.
a.Testing application --> finding the bug---> save to the bug into bug tracking tool with the some unique number --> review by the supervisor--> assigned to the developer---> solve the bug by developer ---> test by the developer ---> i) fixed
b. ii) Unfixed
c.
d.If Fixed---> send the new buld for testing ----> create the envirement ----> test by the tester----> no bug found other wise reopen.
e.
f.This process is continue is going on .
8.what is super class and sub class in error ,bug , defect, failure , fault .
9.what is the difference between bug, defect, problem , fault and issue
10.what are the characteristic of efficient bug reporting ?
11.What are the severity and priority levels in Rational Clear Quest.
a.It depends upon the stage of softwareif the software is in Development stage it is specified as Severity and it is in production stage it is given as proprity.

The ClearQuest Administrator can probably define these levels to suit the company's individual needs.

I have seen the Priority Levels defined as:
1 - High, 2 - Medium, 3 - Low. The priority level is normally determined by the end-user's need for the fix.

I have seen the Severity Levels defined as:
1 - Critical, 2 - Serious, 3 - Moderate, 4 - Minor, 5 - Cosmetic. The severity level is normally determined by the impact the defect has on the end-user process. Eq: "Can the process progress or are we stopped in our tracks?"
12.What is biggest bug you ever found in Testing Environment ?
a.Hello, In the process of testing, people have different experiences across various applications. But for the purpose of answering at the interview, I can give you an example of a serious bug from my experince. One of them being, you can say:
b.
c.
d.
e.During system testing, when the exe file was executed that will initiate the application failed to run. Similar issues were found during other phases also like integration testing when the login module that accepts the username and password which takes the user to the next module.. the system did not respond as expected.
f.
g.
h.
i.Do'nt know if this answer will help you...all the best !thanks.

Generally biggest bug means it depends on the application, domain, product or project...etc.,I can say one bug. If u r working on web application. 1. Type the same URL in 2 browsers 2. so u have 2 similar web pages3. Enter the same data in 2 pages4. Click on Submit5. It should not allow u to submit the same data in to database.6. If u r able to do so, that'll be a big issue.we can say so many like this.......But should be related to your project
13.What is test data we must specify in test cases? How to log bugs in bugzilla? What is code coverage testing? how do we write load test case for a portal?
a.Test data is used while doing end to end testing (Product test), Basically end to end testing is done by inputting the the realistic data(In the real scenario). so while writing the test cases i actually make the data requirement based on the scenario. which is created by the the data modelling team and used the same while execution.

Test data is a set of input values that is needed to execute the test ,it can be any dummy data or data given by the client.

To log a defect in Bugzilla after you login1) Click on New Defect link2)Enter all the detail information required3)In the bug log page, enter the details like Version, Component, OS, Platform, Severity, Priority, Assigned To, Summary, Description etc.Attach a snap shot or print screen or logs if any.
4)Once you complete the Information on the Defect , assign the defect to the concern Developer with Email ID.Here you can also CC the Defect to Couple of Members like Project Mgr ,Team Lead adn you .
5)Click on Commit to save the bug.
15. How to handle the static text values in winrunner by varing it index value different sitiuations ?
16. What is meant by P1 bug? any another similar bugs
P1 bug is the priority 1 bug that means without solving or fixing this bug the application can not continued. we rate the bugs based on the priority and siviority. p1, p2,p3,p4.
p1 bugs also called as showstopper bugs

Priority means the order in which the bug is fixed.Depending on the input of the user defects which are most important to them ,therefore should be fixed first.P1 is priority one defects which are high prority defects & should be fixed very soon before the product/build is to be released.
17. what do mean by bug tracking?give example?
The means of bug tracking is to find out a bug by using a proper process. For that most of the company’s are using bug taking tool like bugzila

Bug tracking is nothing but tracking all the defects some companies may use defect profile template to track all the defectsor we can use tools to trackex: bugzilla,issue-tracker, pr-trackerTest director is also acts as a bug tracking tool and management toolneed not to say u abt this
18. What do we do when we get a bug in an application first? Explain it with the help of an example of Bug Life Cycle.
When we found a bug while testing, We need to clarify whether it is bug or not? If u think that's a bug then we have to log the bug if u r using any bug tracking tool. If u r not using any bug tracking tool, U have to prepare the bug report in an excel sheet. Assume that u don't have any bug tracking tool.

We have to give a unique bug id to that bug. Give title of the bug then Description, Steps to reproduce, Expected Result, Actual Result, Priority, Severity, Build no., Test case id and Date, found by.

If u have bug tracking tool u'll find all these fields in that, u simply enter all these in those fields and automatically bug id will be generated.

When we log or enter a bug that should be in Active or New status. When it gets assigned to developer, he'll fix the bug and he'll change the status to fixed or resolved, After that u have to check or Verify the bug on the new build. If u didn't find any the same bug in the latest build u just close the bug. Otherwise u have to Reopen the bug. In this way bug life cycle goes on.



After confirming it as a Bug, You have to post it in bug tracking tool. Then the status of the Bug will be "New". Your team lead or any senior person will review it and if it is really a bug, then he will change the status to "Open". If he confirms that it is not a bug, he will close the bug and change the status to "Closed".

All the Open status bugs will be mailed to the development team. Their team lead will assign the bugs to the corresponding developer. He will change the status to "Assign" and add the corresponding developer name. When the developer fixes that bug, he changes the bug status to "Test".

If the development team lead confirms that this is not a bug, then he rejects that bug with valid reasons. Then the status of that bug will be "Rejected".

If he confirms that this is not required for the current build, but may be useful for the future releases, then he changes the status of the bug as "Deferred". All the Deferred bugs will be considered for future releases

All the Test status bugs will be mailed to the testing team. The corresponding tester tests that bug in the new build or patch and change the status to "Closed" if it is fixed otherwise to "Re-Open" if it is not fixed.

All the Re-Open bugs will be mailed to the development team and then the above cycle repeats.
19. what is bug leak?
The defect which can be found and Re-produced by End user/Client people the same we(Test Engineer) unable to found at the time of testing. This is also known as "Defect Leakage".

Memory Leak and Bug Leak(Defect Leak) or Different.

I do agree with the first definition.

Defect Leak:The defects that pass through development phases prior to detection is called Bug Leak or Defect Leak.

Memory Leak:

A memory leak is the gradual loss of available computer memory when a program (an application or part of the operating system) repeatedly fails to return memory that it has obtained for temporary use. As a result, the available memory for that application or that part of the operating system becomes exhausted and the program can no longer function. For a program that is frequently opened or called or that runs continuously, even a very small memory leak can eventually cause the program or the system to terminate. A memory leak is the result of a program bug.

[AjayKumar.Kataram]

Thanks and useful post