[TEAM] Package Testing

[Jack Fromm]

Just using the development release has the advantages of being easier 
for the testers and more realistic but it would also rely on having a 
good cross-section of user types actually doing it.

One disadvantage of that approach is that everything might not get 
tested adequately.  I just counted and it looks like I would never touch 
- or touch just once during the initial install - 20 of the 43 apps 
currently on the tracker.

But if people are willing and able to run the new release during the 
cycle (and report results), it would certainly be better than no testing 
at all.

Jack

On 11/14/2014 06:22 AM, Elfy wrote:
> Last cycle little testing was reported for packages, this cycle we 
> want to try something different.
>
> While we have someone working on producing autopilot tests - but it's 
> still early days with that.
>
> So exploratory testing.
>
> Plan to let people just use development release during the cycle, use 
> application and report bugs to the tracker as they find them.
>
> In addition people can use the staging ppa for some applications in 
> Trusty, Utopic and Vivid - so those new yet to be uploaded versions 
> can be tested.
>
> Communication between the QA and Dev teams is important here - we'll 
> call for testing on new apps when we've been asked to.
>
> We can run a few testing sprints during the cycle - nothing other than 
> the though exists for this yet.
>
> Comments on this please.
>
> Thanks
>
>