Question { Polaris, 19524 }

explain bug life cycle

Answer

The duration or time span between the first time bug is
found (‘New’) and closed successfully (status: ‘Closed’),
rejected, postponed or deferred is called as ‘Bug/Error
Life Cycle’.

(Right from the first time any bug is detected till the
point when the bug is fixed and closed, it is assigned to
various statuses which are New, Open, Postpone, Pending
Retest, Retest, Pending Reject, Reject, Deferred, and
Closed.

There are seven different life cycles that a bug can passes
through:

< I > Cycle I:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) Test lead finds that the bug is not valid and the bug
is ‘Rejected’.

< II > Cycle II:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is invalid and is marked with a status
of ‘Pending Reject’ before passing it back to the testing
team.
5) After getting a satisfactory reply from the development
side, the test leader marks the bug as ‘Rejected’.

< III > Cycle III:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug
as ‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug
to ‘Pending Retest’ and passes on to the testing team for
retest.
7) The test leader changes the status of the bug
to ‘Retest’ and passes it to a tester for retest.
8) The tester retests the bug and it is working fine, so
the tester closes the bug and marks it as ‘Closed’.

< IV > Cycle IV:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The development leader and team verify if it is a valid
bug. The bug is valid and the development leader assigns a
developer to it marking the status as ‘Assigned’.
5) The developer solves the problem and marks the bug
as ‘Fixed’ and passes it back to the Development leader.
6) The development leader changes the status of the bug
to ‘Pending Retest’ and passes on to the testing team for
retest.
7) The test leader changes the status of the bug
to ‘Retest’ and passes it to a tester for retest.
8) The tester retests the bug and the same problem
persists, so the tester after confirmation from test leader
reopens the bug and marks it with ‘Reopen’ status. And the
bug is passed back to the development team for fixing.

< V > Cycle V:
1) A tester finds a bug and reports it to Test Lead.
2) The Test lead verifies if the bug is valid or not.
3) The bug is verified and reported to development team
with status as ‘New’.
4) The developer tries to verify if the bug is valid but
fails in replicate the same scenario as was at the time of
testing, but fails in that and asks for help from testing
team.
5) The tester also fails to re-generate the scenario in
which the bug was found. And developer rejects the bug
marking it ‘Rejected’.

< VI > Cycle VI:
1) After confirmation that the data is unavailable or
certain functionality is unavailable, the solution and
retest of the bug is postponed for indefinite time and it
is marked as ‘Postponed’.

< VII > Cycle VII:
1) if the bug does not stand importance and can be/needed
to be postponed, then it is given a status as ‘Deferred’.

This way, any bug that is found ends up with a status of
Closed, Rejected, Deferred or Postponed.

Question { 11458 }

What is difference between Defect and Bug?

Answer

WHEN THE ERROR IS FOUND B/W THE SOFTWARE RELEASE ,ITS CALLED
AS BUG.

WHEN ACTUAL RESULT IS DIFFERENT FROM EXPECTED BEHAVOUR THEN
ITS CALLED AS DEFECT.

Question { IBM, 5446 }

diff b/w project based testing and product based testing?

Answer

If software application is developed for a specific customer
then its called as project.

If software application is developed for a set of customers
or according to market requirements , then its called product

Question { Hewitt, 9219 }

10.What is stub?

Answer

A simulated program that replaces a called program is called
stub.

Question { 8165 }

what is stub and driver ?explane in brife.,and some example

Answer

Stub :- In top-down integration " A simulated program which
replaces a called program is called " Stub"

Driver : In bottom-up integration , A simulated program that
replaces a calling program is called "Driver"

Question { 11473 }

why is smoke testing done for a software?

Answer

Smoke tests :- The application to determine whether the
application is eligible for detailed testing or not. It is a
quick end rough check carried out in application. This quick
check for smoke testing is conducted in test environments.
The objective of smoke tests is to check whether basic
features are available or not to conduct to continue the
major testing.

Question { 2992 }

what is module testing, integrity testing? what is a test
script?

Answer

The testing of individual software components is known as
module testing, This test searches for defects in and verify
s the functioning of software (eg:programs, modules,objects
, classes etc) that are separately testabl e.

test script :- A test procedure specification , especially
a automated one.