View Single Post
jukey's Avatar
Posts: 246 | Thanked: 204 times | Joined on Jun 2007 @ Potsdam (Germany)
#81
Originally Posted by VDVsx View Post
Can you elaborate a bit more in the first point, don't know if I'm understanding it well. Do you mean something like use cases for the app ? Who should provide this list ?
This list should be made by everyone who is willing to do this. This could be the developer itself but also the testers.

The goal is to have a package specific list which could be used as a check list (together with the generic check list) to make sure that every new version works fine. Something where potential testers can go through step-by-step. Maybe one wiki page per application would match perfectly with this request.

An example:
Let's assume there is an application called " all-in-one application suitable for every purpose".
After playing around with it the testers could begin to define what are the key features of the application and write them down as a check list.
After a few month there comes out a new version of this application. It would be easy to test the points on the check list to make sure that there is no regression. It also would help people to start testing this application and not easily thumb up the whole application without deeper tests.

Do you know what I mean?
__________________
-> Join the SailfishOS Meetup Berlin - every first Monday a month <-

Me on twitter
 

The Following 2 Users Say Thank You to jukey For This Useful Post: