This is one of the most common terms in software testing.
What is Severity?
Severity is the impact of bug on application. How the bug is going to affect the application. Severity levels are set by the testers.
What is priority?
Priority is the impact of bug on business.
When a tester reports a bug in an application using a bug tracking tools, the severity and priority levels have to be set.
There are 4 levels.
1) Low Severity Low Priority: Consider a login page. You enter a wrong user name. There is an error message displayed stating that the user name entered is incorrect. The spelling of username is spelled as usirname. This is a case of low severity and low priority. The impact of bug on the application as well as business is low.
2) Low Severity High Priority: Consider the website-Yahoo. When you enter the url:www.yahoo.com. The heading Yahoo on the front page of the website is spelled as Yhaoo. This is a case of low severity and High priority. The impact of bug on the application is too low. However the impact of bug on the business is high. The customers may feel that the website is not of Yahoo.
3) High Severity Low Priority: Let us take the example of a website. A user logs into the website. The user clicks on help section. As soon as the user clicks on next page in the help section, an error message is displayed. This is a perfect example of High Severity and Low Priority. The impact of the bug on the application is high however this does not affect the business.
4) High Severity High Priority: Let us take the example of an online shopping site. The user logs in, adds the item to the cart. Enters the check out page and clicks on submit. Suddenly an error message is displayed. This is a case of High Severity as well as High Priority. This is a critical bug and needs to be fixed as soon as possible. This would affect the application as well as the business.
*Testing is never an activity but a challenge*
Thursday, August 20, 2009
GLOBALISATION AND LOCALIZATION TESTING
LOCALIZATION TESTING:
Testing of an application designed for a specific locality. For eg: MS office in Tamil, malayalam etc.
GLOBALISATION TESTING:
Testing to check how well the application works across the globe.
Why do we need to go for globalisation testing? The color, time zone depends on each country. So we need to test for language, color, timezone, daylight savings, currency. For eg: you can host a website in US with currency as rupees. Consider an ATM centre in UAE with languages in English and Hindi. So globalisation testing has its own importance. In gulf countries, most of the websites would be of green color as of regional sentiments. Even though all these factors do not have much impact on the application, they all contribute to one factor called USER SATISFACTION.
Hope all have got a good idea on localization and globalization testing.
Testing of an application designed for a specific locality. For eg: MS office in Tamil, malayalam etc.
GLOBALISATION TESTING:
Testing to check how well the application works across the globe.
Why do we need to go for globalisation testing? The color, time zone depends on each country. So we need to test for language, color, timezone, daylight savings, currency. For eg: you can host a website in US with currency as rupees. Consider an ATM centre in UAE with languages in English and Hindi. So globalisation testing has its own importance. In gulf countries, most of the websites would be of green color as of regional sentiments. Even though all these factors do not have much impact on the application, they all contribute to one factor called USER SATISFACTION.
Hope all have got a good idea on localization and globalization testing.
ARE DEVELOPERS GOOD TESTERS?
This is a common question in software industry that are faced by the testers. Normally everybody think that since the developer has created the code, he would be the best person to test the code. This assumption is absolutely wrong. Developers can never be good testers. A developer will always have a soft corner towards his code. He would never cause a situation to break his code. He would not think in a negative manner. Since he is the constructor. On the other hand, tester is the destructor. He would always try to break the application. Tester would execute negative as well as positive test cases. Tester himself turns to be a user who is going to use the application for the first time. Never compare a tester with a developer.
QUALITY ASSURANCE & QUALITY CONTROL
These are one of the common terms in software testing. So what is Quality Assurance?
Quality Assurance consists of planning, co-ordinating and other strategic acitivites associated with measuring product quality against external requirements. It is a preventive process. In simple words, quality assurance means we are doing the right things in the right way. It applies to entire life cycle. It's a process oriented activity.
What is Quality control and how is it related with Quality Assurance?
Quality control is a part of Quality Assurance. It's a corrective process. It consists of monitoring, controlling and other tactical activities associated with the measurement of product quality goals. It applies to a specific product or service.
Quality Assurance consists of planning, co-ordinating and other strategic acitivites associated with measuring product quality against external requirements. It is a preventive process. In simple words, quality assurance means we are doing the right things in the right way. It applies to entire life cycle. It's a process oriented activity.
What is Quality control and how is it related with Quality Assurance?
Quality control is a part of Quality Assurance. It's a corrective process. It consists of monitoring, controlling and other tactical activities associated with the measurement of product quality goals. It applies to a specific product or service.
Subscribe to:
Posts (Atom)