Web Testing Notes

Defect:

While testing when a tester executes the test cases he might observe that the actual test results do not match from the expected results. The variation in the expected and actual results is known as defects. Different organizations have different names to describe this variation, commonly defects are also known as bug, problem, incidents or issues. In short we can say identify by tester is called Bug.

Defect Severity:

Def1: Defect Severity or Impact is a classification of software defect (bug) to indicate the degree of negative impact on the quality of software.

Def2: severity: The degree of impact that a defect has on the development or operation of a component or system.

Def3: A defect is a product a nomaly or flaw, which is variance from desired product specification. The classification of defect based on its impact on operation of product is called Defect Severity.

DEFECT SEVERITY CLASSIFICATION:

The actual terminologies, and their meaning, can vary depending on people, projects, organizations, or defect tracking tools, but the following is a normally accepted classification.

Critical:

Def1: The defect affects critical functionality or critical data. It does not have a workaround. Example: Unsuccessful installation, complete failure of a feature.

Def2: There is s functionality block. The application is not able to proceed any further.

Def3: The defect results in the failure of the complete software system, of a subsystem, or of a software unit (program or module) with the system.

Crash:

crashes, loss of data

Block:

Other bugs can't be fixed until this one is. blocks further development and/or testing work. Unlikely unless testing directly from SVN

Fatal:

Def1:A defect that will cause the system to crash or close abruptly or effect other applications.

Def2: A defect that will cause the system to crash or close abruptly or effect other applications.

Def3: Fatal Defects are the defects, which results in the failure of the complete software system, of a subsystem, or of a software unit so that no work or testing can be carried out after the occurrence of the defect.

Showstopper:

Def1: Name itself tells that bug that doesn't allow the user or customer to proceed further steps with testing called as Showstopper.

Def2: the bug which doent allow to carryout further testing

Major:

Def1: The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult.

Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.

Def2: The application is not working as desired. There are variations in the functionality.

Def3: A defect, which will cause an observable product failure or departure from requirements.

Def4: The defect result in the failure of the complete software system of a subsystem, or of a software unit(program or module) within the system. There is no way to make the failed components, however, there are acceptable processing alternatives, which will yield the desired result.

Def5: Major Defects are one, which also causes failure of entire or part of system, but there are some processing alternatives, which allows further operation of the system.

Hotfix:

A bug found in the customersplace for which ur going to send the solution immediatley or fix it imeediately

Average:

The defect does not result in a failure, but causes the system to produce incorrect, incomplete, or inconsistent results, or the defect impairs the systems usability.

Minor:

Def1: The defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.

Def2: There is no failure reported due to the defect, but certainly needs to be rectified.

Def3: A defect that will not cause a failure in execution of the product.

Def4: The defect does not cause failure, does not impair usability, and the desired processing results are easily obtained by working around the defect.

Def5: Minor Defects does not result in failure but causes the system to produce incorrect, incomplete, or inconsistent results, or the defect impairs the system usability.

Cosmetic:

Def1: Defects in the User Interface or Navigation.

Def2: The defect is the result of non-conformance to a standard, is related to the aesthetics of the system, or is a request for an enhancement.Defects at this level may be deferred or even ignored.

Def3: Cosmetic Defects are small errors that do not prevent or hinder functionality.

Text:

consistency of font

Tweak:

Bug affects everyone.

Trivial:

Def1: The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience.

Example: Petty layout discrepancies, spelling/grammatical errors.

Def2: This is a bug, but it doesn't really cause problems. cosmetic problem like misspelled words or misaligned text

Suggestion:

Feature which can be added for betterment

Feature/Enhancement:

A feature request. request for a new feature or change in functionality for an existing feature

The actual terminologies, and their meaning, can vary depending on people, projects, organizations, or defect tracking tools, but the following is a normally accepted classification.

Severity is also denoted as in Method 1:

S1 = Critical
S2 = Major
S3 = Minor
S4 = Trivial

Severity is also denoted as in Method 2:

S1 = Major
S2 = Minor
S3 = Fatal

Severity is also denoted as in Method 3:

S1 = Critical
S2 = Major
S3 = Minor
S4 = Cosmetic
S5=Suggestion

Severity is also denoted as in Method 4:

S1 = Critical
S2 = Major
S3 = Average
S4 = Minor
S5 = Cosmetic

Severity is also denoted as in Method 5:

S1 = Blocker
S2 = Critical
S3 = Major
S4 = Normal
S5 = Minor
S6 = Trivial

Severity is also denoted as in Method 6:

S1 = Critical
S2 = Major
S3 = Minor
S4= Text
S5= Tweak
S6 = Trivial =Cosmetic
S7= Suggestion