bug taxonomy

4

Click here to load reader

Upload: md-mahedi-mahfuj

Post on 20-Jun-2015

506 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Bug taxonomy

Author: Mahedi Mahfuj -0207

Bug Taxonomy

Functionality error:

Doesn’t do what it should do.

Communication error:

Can’t interpret what it is doing….communication gap.

Command structure:

Confusing commands…..After selecting Print button, there must be an

OK button, its absence will cause command error.

Missing command:

Can be customized, but the option is absent.

Performance error:

Program is running in slower rate.

Output error:

Does provide the desired output….what I want?

Error handling type errors:

Error Prevention:

We could not anticipate the possibility of errors & protect

against them.

Error Detection:

We could not notice error condition.

Page 2: Bug taxonomy

Author: Mahedi Mahfuj -0207

Error Recovery:

We could not deal with a detected error.

# Ensuring good error message.

Boundary Related Error:

My limit is 12 digits….I may have given 13 digits….so, boundary related error.

Calculation Type Error:

# Error in mathematical calculation.

# Value of something should have been same throughout the system, but it is

changing frequently.

# Wrong operation order.

Initial & Later States:

When I install something newly in PC some registry key, temp file etc are created.

If not created, then Initial States error.

In later time, if my PC crashes, some valuable information may not be there after

restoring the system. This is Later State error.

Control Flow error:

Can’t understand where to go after whom.

Errors in interpreting data:

# I expect integer, you are providing me character…..so, misinterpretation.

# Some data should have gone to Capital table, but going to Loan table.

Page 3: Bug taxonomy

Author: Mahedi Mahfuj -0207

Race condition:

1 seat vacant, 2 hits at the same time….whom to give the seat?

Load condition:

Deviation from behavior when over loaded.

# 3 types of testing related to load condition:

1. Load Testing:

How an application runs when 1000 user use this at a time…..how it functions?

2. Stress Testing:

I am increasing load continuously. How much stress my application can take?

3. Performance Testing:

I want the output in 5 seconds. First, I check normally. Gradually, I will try to

increase load. Is still responding within 5 seconds or not?

Hardware error:

To send numerous data through the port of the printer and check any error

occurring or not?

Source and version control error:

Create a new version fixing the errors of the previous version. But, if for some

reason, new enhancements do not work or cause another error, then this is

source and version control error.

Documentation error:

Error found in documentation……misleading information.

Testing error:

# Did not notice an obvious problem.

Page 4: Bug taxonomy

Author: Mahedi Mahfuj -0207

# Did not execute a planned test.

# Unnecessary testing without testing code segments of higher priority.