Definition - importance of a test

Discuss test processes, standards, documentation, teams, criteria, test environments, etc.

Moderators: Amaradana, TurboPT, TL Developers

Definition - importance of a test

Postby gianmaria » Wed Jul 23, 2014 7:28 am

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.
Cloud solutions, https://onemediahub.com/
gianmaria
Advanced user
 
Posts: 54
Joined: Sat Dec 15, 2012 7:40 am
Location: Pavia, Italy

Re: Definition - importance of a test

Postby fman » Sun Jul 27, 2014 6:26 pm

IMHO there is no specific definition.
I have to guess: do you want to have more that 3 values ?
fman
Member of TestLink Community
 
Posts: 3012
Joined: Tue Nov 15, 2005 7:19 am

Re: Definition - importance of a test

Postby gianmaria » Thu Jul 31, 2014 7:18 am

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.
Cloud solutions, https://onemediahub.com/
gianmaria
Advanced user
 
Posts: 54
Joined: Sat Dec 15, 2012 7:40 am
Location: Pavia, Italy

Re: Definition - importance of a test

Postby fman » Tue Aug 12, 2014 7:51 am

Thanks for your help
fman
Member of TestLink Community
 
Posts: 3012
Joined: Tue Nov 15, 2005 7:19 am

Re: Definition - importance of a test

Postby psw_berlin » Tue Aug 12, 2014 10:20 am

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!
psw_berlin
TestLink user
 
Posts: 6
Joined: Sat Nov 23, 2013 8:25 am
Location: Stahnsdorf (near Berlin, Germany)

Re: Definition - importance of a test

Postby fman » Wed Aug 13, 2014 2:32 pm

Not now, there is no config option for this, and has important impact on several areas
Workaround => create a Custom Field FMEA Severity.
fman
Member of TestLink Community
 
Posts: 3012
Joined: Tue Nov 15, 2005 7:19 am


Return to General Testing and Test management



Who is online

Users browsing this forum: Google [Bot] and 2 guests