Jump to content

Plasma/TestDays: Difference between revisions

From KDE Community Wiki
Jensreuterberg (talk | contribs)
No edit summary
Jensreuterberg (talk | contribs)
No edit summary
Line 2: Line 2:


==What is Plasma Test Days?==
==What is Plasma Test Days?==
The Plasma Test Days will happen the 19th and 20th of June in preparation for the Plasma 5.7 release. During that time we will stress test the upcoming release with the help of the KDE community and we want to invite everyone, no matter what level of experience you have to be part in this project to ensure the stability and quality of Plasma 5.7 for all.
The Plasma Test Days will happen the '''19th and 20th of June 2016''' in preparation for the Plasma 5.7 release. During that time we will stress test the upcoming release with the help of the KDE community and we want to invite everyone, no matter what level of experience you have to be part in this project to ensure the stability and quality of Plasma 5.7 for all.


===I'm in! How does it work?===
===I'm in! How does it work?===

Revision as of 13:46, 26 April 2016

What is Plasma Test Days?

The Plasma Test Days will happen the 19th and 20th of June 2016 in preparation for the Plasma 5.7 release. During that time we will stress test the upcoming release with the help of the KDE community and we want to invite everyone, no matter what level of experience you have to be part in this project to ensure the stability and quality of Plasma 5.7 for all.

I'm in! How does it work?

Currently we are setting up the Test Day

Test Iso's

Here we will display the available iso's hopefully using stable bases and the beta of Plasma 5.7 on top. Our goal is to have a wide range of different distro's to be a part of the testing to easier ensure that whatever bug found is Plasma related. Our hope is to have one from KDE neon, Opensuse, Fedora, KaOS and hopefully one using Arch as base.

Test Scenarios

What Happens Afterwards?

This is where the fun starts, after the scenarios have been tested, the information handed over to the test day team, the test day team have written, triaged and checked the bugs and passed them off to the developers for whom they are relevant; we evaluate the Test Day and present the results and possible future Test Days.

Evaluation

Results

To be announced after the testing is done.