Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 3 days, 18 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 4 days, 13 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 6 days, 22 hrs ago - more...
 |
|
2010-01-22
, 14:32
|
|
Posts: 1,070 |
Thanked: 1,604 times |
Joined on Sep 2008
@ Helsinki
|
#82
|
Originally Posted by jukey
Yes, exactly what I understood for the first post. We had a case where this could have helped. while ago I was willing to test a app to read RAW images, but I didn't had these kind of files neither enough knowledge in that area, I felt a bit lost, luckily someone with the same problem had already asked in the package interface for some samples and the maintainer provided them
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?
. Is not the good example but is one of these cases
| The Following User Says Thank You to VDVsx For This Useful Post: | ||
 |
| Tags |
| extras-tesing, finishing the job, quality assurance, quarantine, software quality, user testing |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 18:49.
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?
Me on twitter