Vous êtes sur la page 1sur 2

Severity describes the seriousness of the bug.

Due to a bug a total module may not be accessed.For example


bug1: if Application button is clicked then it should open the application form
page. If the button click does not work then it can be described as severity is
high .
bug2: If the click of Application button opens the application page but the deta
ils needs to be displayed in the current page are not displayed then it can be d
escribed as severity is medium .
bug3: If the caption of the Application button is misspelled as Aplication then
it can be described as severity is low
Priority describes what is the bug which needs to be fixed at the earliest. This
is normally decided by the PM.
For example in the above case if the application module need not be submitted im
mediately then bug1 and bug3 may be given high priority where as bug2 may be giv
en priority low
In the above case if the application module has to be given immediately then all
the three bugs bug1 bug2 bug3 are given high priority.
----------------------
Severity is in terms of Apllication functionlaty where as priority is in terms o
f Customer Requirements.
If the severity is high we can't able tomove forward any more in the testing pre
spective if the priority is high we should not leave that defects as defered we
have to make it as fixed. Bcz its having theimporatance to fix that defects acco
rding to enduser requirements.
-------------------------------------
QA vs QC
---------

qa: A planned and systematic set of activities necessary to provide adequate con
fidence that requirements are properly established and products or services conf
orm to specified requirements.
qc: The process by which product quality is compared with applicable standards;
and the action taken when nonconformance is detected.
qa: An activity that establishes and evaluates the processes to produce the prod
ucts.
qc: An activity which verifies if the product meets pre-defined standards.
qa: Helps establish processes.
qc: Implements the process.
qa: Sets up measurements programs to evaluate processes.
qc: Verifies if specific attribute(s) are in a specific product or service
qa: Identifies weaknesses in processes and improves them.
qc: Identifies defects for the primary purpose of correcting defects.
QA is the responsibility of the entire team.
QC is the responsibility of the tester.
qa:Prevents the introduction of issues or defects
qc: Detects, reports and corrects defects
QA evaluates whether or not quality control is working for the primary purpose o
f determining whether or not there is a weakness in the process.
QC evaluates if the application is working for the primary purpose of determini
ng if there is a flaw / defect in the functionalities.
QA improves the process that is applied to multiple products that will ever be p
roduced by a process.
QC improves the development of a specific product or service.
QA personnel should not perform quality control unless doing it to validate qual
ity control is working.
QC personnel may perform quality assurance tasks if and when required.

Vous aimerez peut-être aussi