Actually it depand on which Defect tracking tool u r using
or the company policies. To the fact that a defect is
rejected only when the defect is be not repoduceable or the
tester who filed the defect cannot give sufficient
information on the defect. Upon reject the defect, the
usually status is Rejected. If the reject is due to non
availablity of enough information, doveloper usually gives
a status as Not Reproduceable, need more information.
a) Actuality that is the open states
b) When the developer rejects then tester convenes to
the with respect defect
c) So that is open state
d) All the satiations discuss to developers after the
tester that defect fixed
e) That is the good tester
My name is k.chandra sekhar,
My phone no are 9246540049 65880049 ,Hyderabad.
My mail id is ndra_143@yahoo.co.in
I am take the class for projects if you interst contact
If any body want full explain send the mail
According to the Defect/Bug life cycle, A developer can
face three stages after opening the code:-
a). Deferred - If the defect is not having any importance &
it is not effecting the functionality of the application,
then it is rejected & Application is released.
b). Postponed - If appropriate tools/resources are not
available to fix the Defect. This stage is known as
Postponed.
c). Pending reject - After analysing the part of the
program which contains defect,the developer find that there
is no defect, it is a mistake committed by tester then
stage is called Pending Reject.
Deferred: if it is a postponed defect
Rejected: Not a defect according to developer
Not reproducible: when the developer not able to reproduce
the defect in his system
Maianly the status depends upon in which situation the
developer is rejecting the defect.
if is due not reproducable at developers environement-->
Not reproducible
if the defect is not a defect according to him --> Invalid
If the defect is postponable then he will give the status
as --> Deferred.
"Rejected/Invalid"
why many assholes here are spoiling this forum and telling
that they take classes when they dont know this easy
answer...
rest guys, good going ...
The company has software running in its production
environment that was designed and tested on its quad-
processor servers with 16 GB of RAM. In order to meet
budget constraints, its disaster recovery plan calls for
this same software to be installed on functionally
identical servers, which are dual-processor with 12 GB of
RAM. The test group has been tasked with confirming that
the software is going to work on the hardware proposed in
the disaster recovery plan.
-what testing types is being used in the scenario above?
One very small question, If application/ website performing
all the function perfectly like submission, deletion,
editing etc, why do we require Data base testing
saparately. Please understand before reply thanks !!