From Project plan to scenarios

[baamster]

Hi,

I tried to create scenarios using Testlink, but got a little bit stuck;

Let's take an example, with a test tree like this:

System
1. Application1
1.1 Login (test suite)
1.1.1 Log (test case)
1.1.2 Change password
1.1.3 Account blocked after several tries
1.2 Welcome
1.2.1 Popup first connection
2. Application2
2.1 Login (test suite)
2.1.1 Log (test case)
2.1.2 Change password
2.1.3 Account blocked after several tries
2.2 Welcome
2.2.1 Popup first connection
3. Application3
3.1 Login (test suite)
1.1.1 No Log required (test case)
3.2 Welcome
3.2.1 Popup first connection


Now, If I need to test Application1 login, I take 1.1 test suite, similar to a test scenario SC1.

If I have a global system modification about the number of tries to block an log account, I only take in a test scenario SC2 = 1.1.1 + 1.1.3 + 2.1.1 + 2.1.3;
If I have in the same system version another global modification about the welcome screen popup, I build another test scenario with test cases SC3 = 1.2.1 + 2.2.1 + 3.2.1
The test campaign (or test plan) for the system version is made of SC1 + SC2 + SC3

Possible Solutions I thought of first:

1. Create a new test suite called after the test scenario and copy the individual test cases you wish to use in this scenario in it.
2. Do it through a testplan where you select the testcases you want to execute (so create a testplan for scenario testing for example).

For issue 1, the drawback is that we move the test cases, so that either we lose the test stree structure for a homogeneous referential or we have duplicated tests
For issue 2, we may really have too many testplans to manage, all the more that with Testlink they are not proposed in a tree but in a item list.

Regards,
Reinder

[fman]

please explain if you have a proposal to solve this

[baamster]

Create a Testscenario as part of a tree. For example

TC1.1
TC1.2
TC1.3
TC2.1
TC2.2

TS1: TC1.3; TC1.1; TC2.2
TS2: TC2.1; TC1.2

TP1: TS1; TS2

[fman]

I'm sorry but still I'm not able to understand what if your need.
If you plan to ask for a feature request a very detailed document will be needed

[baamster]

mm, how detailed do you need it? I can only descibe it functionally. TO me a test scenario consists of several testcases in any different order. These scenarios can then be linked to a testplan as to be executed for (e.g.) secnario testing or User Acceptance Testing (which ever you want to call it). At this moment I'm only able to select testcases for a testplan in no particular order (so its not a scenario or flow).

A solution could be to create a testsuite with these testcases copied into, but then you have 2 versions of these cases and next to this I'm still not able to say which should preceed which.

So what should be handy is next to a testsuite, a testscenario where you can (only) select different existing testcases and arange them in any given order you want. Does a picture help?

[fman]

We (dev team) request as much as possible detailed information because is only way to start considering a new feature.
Without good requirements we can not try to do a good implementation.
If we consider our (my) requests something that upset you then I'm sorry very much but we will not be able to help.
The process to request a NEW feature requires that feature be open on Issue Tracking system (our mantis).
Right now only thing we allow is to change is TEST CASE execution order Inside a Test Suite, because execution tree is a view of
test spec tree.