Tuesday, May 28, 2013
Concept of page fault in memory management
Posted by
Sunflower
at
5/28/2013 03:00:00 PM
0
comments
Labels: Address, Fault, Hardware, Invalid, Main Memory, Major, Memory, Memory management, Minor, Operating System, Page Fault, pages, Physical, Processor, program, Software, Types, Virtual Memory
|
| Subscribe by Email |
|
Tuesday, May 17, 2011
What is a bug and bug life cycle? What are guidelines for deciding severity of bugs?
A bug is defined as a defect or some abnormal behavior of software. Testing plays an important part in the removal of bug. Bug has to travel the whole bug life cycle until it is closed. The cycle includes following stages:
- New
When the bug is posted for first time and not yet approved.
- Open
When tester approves that bug is genuine.
- Assign
Bug is assigned to the developer.
- Test
After fixing the bug, it is assigned to testing team to re-test it.
- Deferred
When the bug is changed to deferred state, the bug is expected to be fixed in next releases.
- Rejected
If the developer feels that the bug is not genuine, he can reject the bug.
- Duplicate
If bug is repeated twice or two bugs gives the same concept, then one bug is labeled duplicate.
- Verified
Once the bug is fixed, it is verified that no bug is present and status is changed to verified.
- Reopened
In this stage, the bug traverses the bug cycle once again because the bug still exists.
- Closed
If the bug is fixed and does not exist, the tester changes the status to closed.
SEVERITY AND PRIORITY OF THE BUG HAS TO FOLLOW GUIDELINES:
- Critical bug prevents further testing of the product under test. No work around is possible for such bugs.
- Major bug is in which defect does not function as expected or cause other functionality to fail.
- Medium or average bug in which defects do not conform to standards and conventions.
- Minor or low bugs do not affect the functionality of the system.
To write bug description, follow these guidelines:
- Be specific.
- Use present tense.
- No unnecessary words.
- No exclamation points.
- Do not use all CAPS.
- Mention steps.
Posted by
Sunflower
at
5/17/2011 01:13:00 PM
0
comments
Labels: Abnormal, Bug Fixing, Bug Life Cycle, Bugs, Critical, Defects, Description, Guidelines, Major, Medium bug, Minor bug, Priority, Quality, Severity, Software, Software testing
|
| Subscribe by Email |
|
Sunday, June 20, 2010
How are the defects classified?
All defects are not the same type. Some defects may result in system crash. Some defects may be very minor. So, the defects need to be classified based on its impact on the functionality of the software. There are various ways in which we can classify.
Severity Wise
Major: A defect, which will cause an observable product failure or departure from requirements.
Minor: A defect that will not cause a failure in execution of the product.
Fatal: A defect that will cause the system to crash or close abruptly or effect other applications.
While recording the defects in a defect log sheet, the severity of the defects also needs to be noted. IF a critical defect is present in the code, then the software is not ready for delivery. Only a few major defects are allowed. Similarly, a threshold needs to be kept on the number of minor defects. As the threshold depends on the application, the project manager/test team member has to use the judgement in fixing the thresholds on major and minor defects. After analyzing the test report, the project manager needs to decide whether the software is ready for delivery or not.
Posted by
Sunflower
at
6/20/2010 01:19:00 PM
0
comments
Labels: Bugs, Classification, Critical Path Method, Defects, Errors, Major, Minor Release, Software, software engineering, Types
|
| Subscribe by Email |
|