Class 3 - STLC and Its Process
Class 3 - STLC and Its Process
• It is defined as the how much impact the issue which was raised by the tester
affects the system.
Severity Types
• Blocker: This defect indicates complete shut-down of the process, nothing can proceed
further
• Critical: It is a highly severe defect and collapses the system. However, certain parts of the
system remain functional
• Major: It causes some undesirable behavior, but the system is still functional
• Minor: It won't cause any major break-down of the system
Priority and Its Types
• Priority is defined as the order in which a defect should be fixed.
Higher the priority the sooner the defect should be resolved.
• Priority Types
• High: The defect must be resolved as soon as possible as it affects the system severely and
cannot be used until it is fixed
• Medium: During the normal course of the development activities defect should be resolved.
It can wait until a new version is created
• Low: The Defect is an irritant but repair can be done once the more serious Defect has been
fixed
Examples of Severity and Priority
High Severity and Low Priority
• Suppose the tester clicks on the “Privacy Notice” hyperlink at the bottom of the amazon.com
homepage and the page is not displayed. This defect will be of high severity because the
functionality is not working. The priority is low because people do not normally spend time
reading the privacy notice.
• State transition should be used when a testing team is testing the application for a
limited set of input values.
• The technique should be used when the testing team wants to test sequence of events
which happen in the application.
• Example:
• In the following example, if the user enters a valid password in any of the first three
attempts the user will be able to log in successfully. If the user enters the invalid
password in the first or second try, the user will be prompted to re-enter the password.
When the user enters password incorrectly 3rd time, the action has taken, and the
account will be blocked.
State Transition Example
Error Guessing
• Error guessing is a software testing technique which is based on
guessing the error .
Test Planning Requirement Identifying the resouces Project manager 75% Test
Docucment, Team Formation and Team led 25% plan/strategy
FRS document Team Estimation document.
Preparation of test plan
Review of test plan
Writing test cases FRS document Preparation of test scenarios Team lead 50% and test Test case
Test Plan doc,design Preparation of test cases engineers 50% document
doc , Use case doc Review of test scenario
Review of test cases
Executing the test Test plan Executing the test cases. Team lead 10% and test Test report
cases Test case doc engineers 90% document
Design doc
Build from development
team
Identify the defect Test report, Identifying the bug. Team lead 10% and test Defect report
test cases document Raising a bug engineers 90% doc
Test plan Communicate with the
developer
Test Closure Test report Analysing the test report Project manager 80% Test summary
Defect report Analysing the bug report and Team lead 20% report