What is the difference between High and critical.

Hi,

I am new to this forum.

I have been asked this question in an interview.

What is the difference between High and critical.

My answer was Critical is the show stopper, and need to attend the issue immediately. But then I was asked if High shouldn't be considred like that.

I kind of answered as the difference is so minurt. Any bug has to be attended immediately unless it's very lower in priority. Am I correct?

Could any one please explain the exact difference?

Thanks,
Rani

[QUOTE]
Hi,

I am new to this forum.

I have been asked this question in an interview.

What is the difference between High and critical.

My answer was Critical is the show stopper, and need to attend the issue immediately. But then I was asked if High shouldn't be considered like that.

One kind of answered as the difference is so miner. Any bug has to be attended immediately unless it's very lower in priority. Am I correct?

Could any one please explain the exact difference?

Thanks,

Rani[/QUOTE]

Hello rani,
As per my knowledge critical is Characterized by careful, exact evaluation and judgment.
and high is of course you have explained yourself.

[QUOTE=Rani99;10789]Hi,

I am new to this forum.

I have been asked this question in an interview.

What is the difference between High and critical.

My answer was Critical is the show stopper, and need to attend the issue immediately. But then I was asked if High shouldn't be considred like that.

I kind of answered as the difference is so minurt. Any bug has to be attended immediately unless it's very lower in priority. Am I correct?

Could any one please explain the exact difference?



Thanks,
Rani[/QUOTE]


hi Rani,

both High and Critical are the severities assigned bythe testers
so that the bug can be raised to the development team, acknowledged and recognised and eventually be fixed....


Now people use different terms and assign degrees to the severity of the bug
and both the teams have to come up to a conformation about the terms and their interpretation...same for priorities given by developers...

severity
1 Critical-Show stoppers (In my organisation)
2 High -bugs if not fixed in time and the application has some workaround and you are able to navigate through the application but the bug may cause some hardware or data loss
3 medium- the bug may cause some data loss
4 low - given to cosmetic bugs

the same way corresponding to these severities we try to bring our clients to conformation that developemnt team would understand our interpretaion of the terms and would assign their priorities based on these severities
so that both of us can work in coordination and finally try to the reach the satisfaction level of the client delivering a quality product

Nice description aardvax.

Carry on.

HI Jain brijesh
thanks for complments