Definition - importance of a test

[gianmaria]

Under TestLink it's possible to set the importance of every tests.
The default levels are: High, Medium and Low.
I searched under the glossary and manual the definitions of this 3 levels but I didn't find them.
Can you help me?

Thanks.

[fman]

IMHO there is no specific definition.
I have to guess: do you want to have more that 3 values ?

[gianmaria]

Thank fman for the reply.
No, I don't need more values, 3 it's enough.

I'd like to share with you our definitions.

High: basic functionality (needs to go for every demo), high customer impact if fails. High risk area to generate regressions. Any failure in this category will be P1 or P2 bugs. Test cases for components that has very high integration with other modules. Complex features. continuously error prone [from past experience]. High technical risk.
Medium: the test case is better to be executed if time permits. Test cases for components that has very moderate integration with other modules. UI field validations. Moderate technical risk.
Low:Low risk to generate regressions. Failure of the test case will be P3 bugs. Test cases around validating error messages. Test cases for components that has very limited or negligible integration with other modules. Minimal technical risk.

We set bugs with 3 different prioritues: P1, P2, P3

I hope it can help someone.

[fman]

Thanks for your help

[psw_berlin]

Just a quick question .....
... would more than 3 importances possible?
I'm thinking in terms of 1 to 10 to represent the Severity (S) ranking in FMEA.

Thanks!

[fman]

Not now, there is no config option for this, and has important impact on several areas
Workaround => create a Custom Field FMEA Severity.