Scribd
Upload
24 views7 pages

STE 4th Unit Question With Answer

The document outlines defect management, detailing attributes of defects such as severity, work product, type of errors, and status. It describes the defect life cycle stages from 'New' to 'Closed' and identifies root causes of defects, including miscommunication and lack of experience. Additionally, it covers defect classification, the defect management process, and provides a defect report example for a login form issue.

Uploaded by

Gajanan Markad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
24 views7 pages

STE 4th Unit Question With Answer

The document outlines defect management, detailing attributes of defects such as severity, work product, type of errors, and status. It describes the defect life cycle stages from 'New' to 'Closed' and identifies root causes of defects, including miscommunication and lack of experience. Additionally, it covers defect classification, the defect management process, and provides a defect report example for a login form issue.

Uploaded by

Gajanan Markad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Unit 4: Defect Management

Q.1] State any four attributes of defect.


1. 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.
2. Work product wise:
• SSD: A defect from System Study document
• FSD: A defect from Functional Specification document
• ADS: A defect from Architectural Design Document
• DDS: A defect from Detailed Design document
3. Type of Errors Wise:
• Comments: Inadequate/ incorrect/ misleading or missing comments in
the source code
• Computational Error: Improper computation of the formulae /
improper business validations in code.
• Data error: Incorrect data population / update in database
• Database Error: Error in the database schema/Design
4. Status Wise:
• Open
• Closed
• Deferred
• Cancelled

Q.2] Write any two root causes of defect?


1. Miscommunication of requirements introduces error in code
2. Unrealistic time schedule for development
3. Lack of designing experience
4. Lack of coding practices experience
5. Human factors introduce errors in code
6. Lack of version control
7. Buggy third-party tools
8. Poor Software testing skill
Q.3] Describe defect life cycle with neat diagram. write example for defect
template

Fig. Defect life cycle


1. New:
When the bug is posted for the first time, its state will be “NEW”. This
means that the bug is not yet approved.
2. Open:
After a tester has posted a bug, the lead of the tester approves that the bug
is genuine and he changes the state as “OPEN”.
3. Assign:
Once the lead changes the state as “OPEN”, he assigns the bug to
corresponding developer or developer team. The state of the bug now is changed
to “ASSIGN”.
4. Test/Retest:
Once the developer fixes the bug, he has to assign the bug to the
testing team for next round of testing. Before he releases the software with bug
fixed, he changes the state of bug to “TEST”. It specifies that the bug has been
fixed and is released to testing team. At this stage the tester do the retesting of
the changed code which developer has given to him to check whether the defect
got fixed or not.
5. Deferred:
The bug, changed to deferred state means the bug is expected to be
fixed in next releases. The reasons for changing the bug to this state have many
factors. Some of them are priority of the bug may be low, lack of time for the
release or the bug may not have major effect on the software.
6. Rejected:
If the developer feels that the bug is not genuine, he rejects the bug.
Then the state of the bug is changed to “REJECTED”.
7. Verified:
Once the bug is fixed and the status is changed to “TEST”, the tester
tests the bug. If the bug is not present in the software, he approves that the bug
is fixed and changes the status to “VERIFIED”.
8. Reopened:
If the bug still exists even after the bug is fixed by the developer, the
tester changes the status to “REOPENED”. The bug traverses the life cycle once
again.
9. Closed:
Once the bug is fixed, it is tested by the tester. If the tester feels that the
bug no longer exists in the software, he changes the status of the bug to
“CLOSED”. This state means that the bug is fixed, tested and approved.

Defect Template:

Q.4] Give the defect classification and its meaning.


1. Requirement/Specification Defects:
Requirement-related defects arise in a
product when one fails to understand what the customer requires. These defects
may be due to the customer gap, where the customer is unable to define his
requirements. Producer gap, where the developing team is not able to make a
product as per requirements.
2. Design Defects:
Design defects occur when system components, interactions
between system components, interactions between the outside
software/hardware, or users are incorrectly designed. Design defects generally
refer to the way of design creation or its usage while creating a product.
3. Coding Defects:
This defect arises when variables are not initialized properly or
variables are not declared correctly or database is not created properly. Coding
also needs adequate commenting to make it readable and maintainable in future.
4. Testing Defects:
These would encompass incorrect, incomplete, missing
inappropriate test cases and test procedures.

Q.5] Explain defect management process with suitable diagram.


The process of finding defects and reducing them at the lowest cost is called as
Defect Management Process.

Stages of DMP:
1) Defect Prevention
2) Deliverable Baseline
3) Defect Discovery
4) Defect Resolution
5) Process Improvement
1. Defect Prevention –
Defect elimination at early stage is one of the best ways
to reduce its impact. At early stage, fixing or resolving defects required less
cost, and impact can also be minimized. But at a later stage, finding defects
and then fixing it requires very high cost and impact of defect can also be
increased.
2. Deliverable Baseline –
When deliverable such product or document reaches its
pre-defined milestone then deliverable is considered as baseline. Pre-defined
milestone generally defines what the project or software is supposed to
achieve.

3. Defect Discovery –
Defect discovery at early stage is very important.
Afterword’s, it might cause greater damage. A defect is only considered
‘discovered” if developers have acknowledged it to be valid one.

4. Defect Resolution –
Defect is being resolved and fixed by developers and
then places it in the same place from where the defect was initially identified.

5. Process Improvement –
All defects that are identified are critical and cause
some impact on system. It doesn’t mean that defects that have a low impact on
system are not critical. For process improvement, each and every defect that is
identified are needed to fixed.

Q.6] Draw defect prevention process cycle. State working of each phase.
Defect prevention is considered as the best mechanism to remove the
defects in early stage of testing rather than of finding the defects in the later
stage and then fixing it.

Fig. Defect Prevention process cycle


1. Identify Critical Risk:
Identify Critical Risk in system which may have big
impact if occurred during testing or in the later stage.
2. Estimate Expected Impact:
For every critical risk, calculate amount of
financial impact if the risk actually occurred
3. Minimize Expected Impact:
Once you identify all critical risks, the topmost
risks, which may be harmful to system if encountered and try to minimize or
completely eliminate the risk. For risk which cannot be eliminated, it reduces the
probity of occurrence and its financial impacts
Q.7] Prepare defect report after executing test cases for any login form.

Following is Defect report after executing test cases for email-log in form.

Description:
When I put mail id and password, I am unable to login while login
credentials are right.

Steps to reproduce:
> go to the www.gmail.com
> Click on login button
> Put Right mail id and password and click next.
> and take Screenshot.
Expected result:
The mail account should logged in after putting the right mail id and
password.

Actual result:
The mail account is not logging in after putting the right details.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy