2 Many Bugs

All testers of software strive to attain themselves the essential objective of hunt number maximum of insects in software. When someone construct gets ready to try, the principal objective of the tester is to dig up possible insects maxima of every one &the amplifier; every corner. To attain the perfection in this task essay is executed different angles. The application is liable to the harshnesses of the following type:

# THE analysis of value of Border
# Essay of Validation
# Essay of Verification
# Essay of graphic interface
# Essay of Interoperability
# Essay of Integration
# THE Functional Essay - from the standpoint of concept of Matters
# Essay of Back
# The Security Trying etc.

With such activity tester needs to enter in the ample depth of the application of software taking care of the essential conditions of the matters.

The this is one makes known that the simple conscience of the Insect is insignificant unless it is supported by a correct series of documentation. This generates the need of "the Reports of Insect". These insect reports form the production of primary work of a tester. The insect reports are an important frequently looked at object even by the persons otherwise that the essay team. Such Insect Retrieves the game an extremely crucial role in the various phases of the SDLC. These Reports of Insect frequently are used by the essay engineers, the code contractors, the bosses of project and at last by the customers also. The customers become completely exacting these days &the amplifier; demand the test/the reports of insect. Therefore the Reports of Insect are big meaning &the amplifier; are referred several times by all interested.

After the testers tries software &the amplifier; retrieve the insects to the team of contractors, that need to treat the same, a dissension type is the limit to present itself. This is because, person savors its errors are said. The testers fall of ordinary one on a humiliation type &the amplifier; the cold wars as the positions develop. The special position presents itself when the two testers also the means of contractor to say a special thing in the same manner &the amplifier; the two can be justified in their view point, nevertheless the conflict can present itself because of the difference of projection from the standpoint. Thus we can say that attribute key of a better tester is his capacity to find the big number of insects just like his capacity to obtain the number maximum of insects set up in his application.

The report of Insects in an effective manner is an Art:

Insect report furnishes an effective one feels failure to the contractors. A good Report of Insect is the the one, that is prepared with as much of clarity as the contractors would feel a pleasure direction in the insect fixing. Nevertheless the reports poorly of written insect go in all probability to have the inverse effect of the team of development with the commentaries as - the is an insect and It cannot be reproduced. Same manner there can be numerous commentaries of similar nature.

Thus an intelligent tester understands the big importance of his "the Report of Insect" &the amplifier; prepares a Report of undisputable Insect of his better &the amplifier; the extreme clarity to avoid any type of controversy to any step.


Important Eledments of a Report of Insect:
For an effective communication with the code contractors, Following the news retrieving themselves to the Insect needs to be captured &the amplifier; clearly is transmitted in the Report of Insect. Such information are big assistance to the contractors in the comprehension of the Insect, obtain an idea of the severity of the Insect &the amplifier; it should be able to reproduce the Insect if must be.

As a question of two communications in a manner, the contractor is counted equally to describe the problem cause/l' Insect, the steps that are taken to repair the Insect/The description of Repair, the steps that are taken to verify the repair and all information serviables in to prevent from the events of such Insects in the future.

Annoy the ID: A unique number for the insect identification.

Annoy the State: During the Cycle of Life of the Insect, it passes through the various states before being closed (as describes in the Item "All Knowledge of States of Insect during the Cycle of Life"). The present state of the Insect as the New Insect, the Assigned Insect, the Insect Sets up, the Insect Closed etc. is an essential party of the Report of Insect.

The details of Application: As the application name, the version, URL, the basic details of so any data etc.

Component or Under Component: refer to the application party where the insect was detected by the tester

The details of the Environment: As Name of the details of operating System of the plateforme of Equipment etc.

Annoy the Severity/The Level of Criticality: As Average Critique/Majeur/la or the Minor

Annoy the Priority: When a lot of insects with the similar severity are present in the system, the priorities can be assigned to such insects according to which these these insects will be repaired.

Try ID of Case: A number unique/name for the identification of the case of Test.

Entitle/the Subject of the Insect: A report can be a description of line of the insect

Annoy the Description: A detailed description of the insect.

The steps To Reproduce: An explanation not at all by no method to reproduce the insect.

The details of Data of Data: A detailed description of the data of entry, based on which ones annoys had been detected.

Additional information: As the Blows of Ecran, the error Messages, Note so any files etc. are extremely serviable in to find the problem cause &the amplifier; arriving to a solution to repair it.
The details of the Tester: The details As one) b of Name) the news of Contact etc.

The insect Evednement Details: The details as the Date &the amplifier; the Time to which Annoys had been retrieved
The Try insect Details: The details as the name of the contractor to which the insect was assigned.

The cause of the Problem: A detailed description of the causes takes to the problem

The solution/repair: A detailed explanation of the steps that are businesses to repair the problem.

Difficult sector: The identification of the section of Code/The file/it modulate/the class where the repair was done, including the method details that is used to repair the problem.

The version Details: The details as the Date back to Repair, the file Version that contains the repair interested