Definition of Test Suite vs Test Cases

[Raul]

Is there an accepted definition of a QA Test Suite vs QA Test Cases?

I don't quite follow the difference between the 2.

[Trushkin]

In article <3a18c3ca.10915397@news>,

ravindra@hold_da_spam_Home.com (Raul) wrote:
>
> Is there an accepted definition of a QA Test Suite vs QA Test Cases?
>
> I don't quite follow the difference between the 2.
>

I dare give you my vision of this: Test Suit is a bunch of test cases
having certain goal when used all together. Examples Regression test
suit, Smoke test suit, Functional test suit, Load test suit. They all
usually consist of the number of test cases.

--
Best Wishes,
Vladimir

//////////////////////////////////////////////
// Many ideas grow better when transplanted //
// into another mind than in the one where //
// they sprang up. //
//////////////////////////////////////////////

Sent via Deja.com http://www.deja.com/
Before you buy.

[Eamonn J. Casey]

I agree.

Make some Test Cases and then group them together into a Test Suite. A
Test Case might exercise some piece of functionality. A Test Suite
executes that Test Cases to peroform some user action or scenarion.

There are exeptions to this, of course. I have a Test Suite that says
'Test database scripts' and another that says 'Check version numbering'.
But those fall into the gernal category.

Eamonn J.

Trushkin, Vladimir wrote:

> In article <3a18c3ca.10915397@news>,
> ravindra@hold_da_spam_Home.com (Raul) wrote:
> >

> > Is there an accepted definition of a QA Test Suite vs QA Test Cases?
> >
> > I don't quite follow the difference between the 2.
> >
>

[JJ]

You know what? I think it's just words.

There's test plans and test specs and test suites and test cases and test
steps and test scenarios ... and I've seen all of these intermixed with each
other. My approach has been to learn what my client prefers in the way of
vernacular and use it that way.

I do have my own idea of what each term means and for the most part (I
think) they match most everybody in the industry. The challenge is that the
IT people and the business people who've started using the terms at their
sites that they prefer are not in the QA industry but they are used to their
terms. We (the QA people) can do the work regardless of what the task is
labeled.

... just words.... :)

--
-- Jean

"Raul" <ravindra@hold_da_spam_Home.com> wrote in message
news:3a18c3ca.10915397@news...

[Bjorn Karlsson]

JJ wrote:
>
> You know what? I think it's just words.
>
> There's test plans and test specs and test suites and test cases and test
> steps and test scenarios ... and I've seen all of these intermixed with each
> other. My approach has been to learn what my client prefers in the way of
> vernacular and use it that way.
>
> I do have my own idea of what each term means and for the most part (I
> think) they match most everybody in the industry. The challenge is that the
> IT people and the business people who've started using the terms at their
> sites that they prefer are not in the QA industry but they are used to their
> terms. We (the QA people) can do the work regardless of what the task is
> labeled.
>
> ... just words.... :)
>
> --
> -- Jean
>
> "Raul" <ravindra@hold_da_spam_Home.com> wrote in message
> news:3a18c3ca.10915397@news...
> >

> > Is there an accepted definition of a QA Test Suite vs QA Test Cases?
> >
> > I don't quite follow the difference between the 2.

It is just words, yes....
but a common definition and use of them are
actually part of the IEEE standard.
See, for instance, IEEE 829 and IEEE 1012.

Regards Björn