Showing posts with label severity and priority difference. Show all posts
Showing posts with label severity and priority difference. Show all posts

software police concepts 1

Severity and priority with examples


1.High severity & low priority :- If a application crashes on very rare occasions and changes are very low of crashing.so severity will be high but priority will be low.


2.High severity & high priority:- if a application crashes very frequently and duly visible or first time the application came from development team to the testing department.


3.Low severity & low priority:- it is merely just a enhancement bug which the client wishes like changing the background colour of user interface,also like adding a button like 'back' to navigate previous page.


4.Low severity & high priority:- In this case if the name of the company on its home page is misspelt will be considered. So to find that in which category the bug comes always remember one thing that Low severity bugs are mostly related to GUIs and high severity bugs always related to things like
system crash.severity is always technical while priority is for business purpose.


2.Is testcases compulsary ????
Test case is a Step by step procedure  to validate the functionality of the system. The important
reason why it should be documented is,



1. Testing all the fnctionality is a repeated process and can be executed any number of times in future. So the plan is to Execute all the cases with out fail.


2. The testcase may be executed by any other tester. So rework is avoided.


3. To keep track/cover all the possible functionalities.


3.What is test strategy ??


Test strategy is an organisational level term and it is used for all the projects in the company.
the contains contains contains the followinf items


1.levels of testing
2.types of testing
3.test design techniques
4.configuration management
5.test metics
6.automation plan
7.list of automation tools
 
 
Continue lendo

Testing concepts (Severity and priority)

Severity:
seriousness of defect with respect  to functionality

!High:without resolving the defect we r unable to continue testing.
!Medium:compulsory to solve but able to continue !
low:May or may not be resolved.


Prority:Importance of the defect wrt customer (High,medium,low) When we go for examples 1.user interface bugs[low severity]


Eg1:Spelling mistake(High priority) Eg2:Improper allignment(Low priority) 2.Input domain bugs:[medium severity] Eg1:Doesnot allow valid values(high priority) Eg2:allows invalid type also(low priority) 3.Race condition bugs[High severity] Eg1:Deadlock(High priority)


Eg2:improper order or services(Low priority) like this there r many,but the thing is that as the name severity itself says seriousness, based on the seriousness created by the bug we give priority ie., importance
Continue lendo
 

Software police Copyright © 2011 | Template design by O Pregador | Powered by Blogger Templates | Distributed by Way2 Blogger Templates