Why are there Bugs in Software?
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
(Continued from previous part...)
Triage Meetings (Bug Councils)
Bug Triage Meetings are project meetings in which open bugs are divided into categories.
Categories for software bugs
1. bugs to fix now
2. bugs to fix later
3. bugs we'll never fix
Bug Analyzing and Reproduction Tips
To reproduce an environment-dependent error, both the exact sequence of
activities and the environment conditions (e.g. operating system, browser version
, add-on components, database server, Web server, third-party components, client-server
resources, network bandwidth and traffic, etc.) in which the application operations
must be replicated.
Environment-independent errors on the other hand are easier to reproduce -- they do not
require replicating the operating environment. With environment-independent errors, all that need
to be replicated are the steps that generate the error.
Browser Bug Analyzing Tips
- Check if the client operating system(OS) version and patches meet system requirements.
- Check if the correct version of the browser is installed on the client machine.
- Check if the browser is properly installed on the matche.
- Check the browser settings.
- Check with different browsers (e.g., Netscape Navigator versus internet Explorer).
- Check with different supported versions of the same browsers(e.g.3.1,3.2,4.2,4.3, etc).
Equivalence Class Partitiong and Boundary Condition Analysis
Equivalence class partitioning is a timesaving practice that identifies tests that are equivalent to one
another; when two inputs are equivalent, you expect them to cause the identical sequence of operations to
take place or they cause the same path to be executed through the code. When two or more test cases are seen as equivalent, the rresource savings associated with not running the redundant tests normally outweighs the rsik.
An example of an equivalence class includes the testj g of a data-entry field in an HTML form. If the field
accepts a five-digit ZIP code(e.g, 22222) then it can reasonably be assumed that field will accept all other
five-digit ZIP codes (e.g. 33333, 44444, etc.)
In equivalence partitioning, both valid and invalid values are treated in this manner. For example, if entering
six letters into the ZIP code field just described results in an error message, then it can reasonably be assumed that all six-letter conbinations will result in the same error message. Similarly, if entering a four-digit number inti the ZIP code field results in an error message, then it should be assumed that all
four digit combinations will result in the same error message.
(Continued on next part...)
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|