Topic on Talk:Quality Assurance/Writing feature descriptions

This page describes how a volunteer can write descriptions of features in plain English, but the important bit missing is hat a real volunteer will wonder first where to start. What projects are missing descriptions, and therefore my work would be useful? What projects DO have descriptions already, and therefore I can just forget about them?

Without this, the risk of pointless duplicated work is high, and therefore many potential volunteers will just walk away silently.

Is QA/test backlog the best destination? What is the best way to browse the existing descriptions?

This post was posted by Qgil-WMF, but signed as Qgil.

I added some examples of some sorts of personae who I can imagine might contribute tests to be automated.

No, this is not about personae but about real and current indications. For example: do I start going through Echo notifications features, describing the expected behaviors or is it already covered? How can I know?

Put this example to anybody at any point of time. How can people know what is done and what is missing?

This post was posted by Qgil-WMF, but signed as Qgil.