all-in-one/tests/QA
szaimen 3449cd61f1 remove the backup archive from the repo as it produced issues
Signed-off-by: szaimen <szaimen@e.mail.de>
2022-05-09 16:04:44 +02:00
..
assets/backup-archive remove the backup archive from the repo as it produced issues 2022-05-09 16:04:44 +02:00
001-initial-setup.md add qa test plans 2022-04-23 18:58:25 +02:00
002-new-instance.md show the initial credentials more prominent when being new 2022-04-23 20:11:33 +02:00
003-automatic-login.md add qa test plans 2022-04-23 18:58:25 +02:00
004-initial-backup.md show the initial credentials more prominent when being new 2022-04-23 20:11:33 +02:00
010-restore-instance.md make the instance restore process better understandable 2022-04-24 14:12:03 +02:00
020-backup-and-restore.md improve wording regarding daily backup 2022-04-26 15:22:00 +02:00
030-aio-password-change.md add qa test plans 2022-04-23 18:58:25 +02:00
040-login-behavior.md add qa test plans 2022-04-23 18:58:25 +02:00
050-optional-addons.md additional qa test plans 2022-04-23 19:58:20 +02:00
060-environmental-variables.md additional qa test plans 2022-04-23 19:58:20 +02:00
readme.md add qa test plans 2022-04-23 18:58:25 +02:00

QA test plans

In this folder are manual test plans for QA located that allow to manually step through certain features and make sure that everything works as expected.

For a test instance, you should make sure that all potentially breaking changes are merged, build new containers by following https://github.com/nextcloud/all-in-one/blob/main/develop.md#how-to-build-new-containers, stop a potential old instance, remove it and delete all volumes. Afterwards start a new clean test instance by following https://github.com/nextcloud/all-in-one/blob/main/develop.md#developer-channel.

Best is to start testing with 001-initial-setup.md.