Working with project files in Session Tester

[Martin Jansson]

There is a plan to include the possibilility to work with test
sessions that are included in a project.

Do we have any ideas on how this should work?

Some things I see as interesting for a project is...
- a common preference/settings file that specifies directories, areas
etc.
- a way to structure your test sessions in folders inside a project.
- default when creating a new project is to have one test session
which you are editing
- possibility for a test lead role to create a set of missions that
just need to be "editted" and filled with details
- ability to see some kind of statistics on a project file
- ability to set test sessions in certain states, related to SBTM,
such as approved, submitted etc
- ability to have a history/log connected to the project to see
changes

Issues:
* Do we see a project as a collection of files for one user or a
project file just as we see a project in NetBeans? The implication is
that you might not want to share your files. I guess this is closely
related to how you want a test lead and tester to cooperate with
session-based testing.
* Would we want different views on the project files and structure
depending on role? Test lead and tester see differen things? I propose
not to. This goes perhaps in line with how we view a tester? I propose
we see everyone as a tester (a combination of all test related roles).

To be continued....

What do the rest of you think on this?


--
Subscription settings: http://groups.google.com/group/session-tester-development/subscribe?hl=en

[JonathanKohl]

Great points Martin. I have modeled this a bit, but not enough. We
should start working on this together. I have some ideas based on how
we handle ISO and FDA audits, but I need more.

Thanks,

-Jonathan

> Subscription settings:http://groups.google.com/group/session-tester-development/subscribe?h...

[Jared Quinert]

Hi Martin,

I think I understand most of these features, but as everyone tends to manage exploratory testing a little bit differently, I'd be keen for you to describe each of those points in more detail, really dragging out the problems they solve and the value they add.

For example, I think the high-level problem some of these are related to is something like:

"(Role: Test lead/manager) - Because critical areas of the application will need to be tested repeatedly, I want to be able to reuse session charters"

This would lead to features you described, such as -

- a way to structure your test sessions in folders inside a project.

But we could abstract the problem statements/needs/value contained in that feature to a few different user stories, such as -

- (Test manager/lead) Because some session charters will be frequently re-run together, I want to be able to logically group session charters
- Because stakeholders are interested in what parts of the system have been covered, I want to be able to tie session charters to a higher-level coverage element.
- (Test manager) Because some session charters may be usually run by the same person, I want to be able to assign multiple session charters to a tester

These might all be solved to some degree by having a folder structure, but it's nice to pull out the problems so that we can all understand how the feature's intended to be used, and the context.  It lets us share the problem domain more explicitly.

This 'Because' format for stories is something I've been experimenting with on projects, so I was hoping to try it out further on Session Tester.

Would you like to have a go at writing some of these story titles for the features below?  Or I'm happy to try and write what I understand the problems to be and you can let me know if I'm on the mark.

Jared

[Martin Jansson]

Good idea Jared.

 

Many of these ideas come from the frustration working with regular SBTM where you might handle sessions from various sources and projects trying to sort them out.

 

I'll see If I can delve deeper into these Because-elaborations.

 

/Martin

[JonathanKohl]

Jared has started with stories and epics here:
http://wiki.openqa.org/display/ST/Documentation+-+User+Stories+-+Epics

> >>http://groups.google.com/group/session-tester-development/subscribe?h...

[Martin Jansson]

I'll add the ideas I have here then. This is an interesting way of describing it.

 

BR,

Martin