Prepare scenarios that will be tested on 1st prototype of plan-manager

[blcham]

Note this is related to #116.

The goal is to persuade us that the current tool is possible to use for reasonable subset of tasks that MK needs.

A/C:

• scenarios what tasks will be done with the tool are described (should be described in abstract way = without tool and in complex cases with reference to the tool)

[lalisand]

As for this task, there has been some testing already in summer 2022, done by Tomáš Ulrich and Ondra Vítovec. From what I remember, they have communicated with Martin at least to understand what the current Excel sheet does at CSAT.

I have discussed this with Martin later in October and suggested he may test even scenarios not supported by the SW tools at that time (i.e. manually). I assume no testing was done since then.

It follows we should revise the test plan. To me, it makes the most sense to have the scenarios selected by Martin. To me, scenarios are simply use-cases - list of workflows the user may want to execute. We already did some analysis on use-cases with Martin [1], so the job now would be to select some or all to test, and specify when and how to do this.

@blcham you can complement me if I am not thinking correctly or miss something here. @kalamartin could you please share your inputs on this? Is this clear?

[1] https://drive.google.com/file/d/18xLYP7kHjAmRtsWee8PgRw22rd3hu4EW/view?usp=share_link

[kalamartin]

@lalisand Testing was performed many times when made changes and I have created plenty of issues here on Github.

5 closed. Some of them with reference to others and these are on the list to do.

8 still opened.

This is result of my own testing of the planner. My suggestions and bugs were mostly not been resolved...what more testing is needed than?

[lalisand]

@kalamartin we need to make sure we have tested everything. From your message I cannot confirm all key functionalities (and the entire scenarios) were tested and we really have a complete list of issues. I guess Miro is suggesting this because of that.

Your testing is valuable but we are not sure what was tested and was wasn't. The goal is not to resolve all the issues as there may be many, but first only those with high priority.

[kalamartin]

@lalisand therefore let me know what I should test then or how should I proceed. What was possible to you use in means of functionality these days, I had done.

[lalisand]

@kalamartin you can do what I mentioned in my first message in this thread - look into use-cases in [1] and use them as check-lists to make sure we did not miss anything from the testing. You can mention, which scenarios you would like to test, but are not yet possible. We would work then with higher priority on enabling these.

[blcham]

Adding shared document Scenarios and Testing -- here we can mark which scenarios will be tested for the 1st prototype.