I suggest creating a project to track tasks about selenium tests, to make it easier for reviewers to find relevant tasks with patches and for developers to find tasks to work on. Example tasks in the scope include
The project would also include our uses of WebdriverIO, so tasks like T274579
None of the individual tasks I linked in the description are tagged as Browser-Tests, but that project is described as "For teams/users to track issues related to their browser tests." so maybe they all should be tagged? If that project is intended to be used for selenium tests that works for me (maybe #selenium should be added as an alias for it)
In my opinion, these generic tags are rarely useful because code is or should be maintained by individual teams. Issues with Echo browser tests are issues with Echo, period. Whether a PHP file, JavaScript file, SQL file, doc file, unit test or otherwise doesn't really matter in general.
If other interested parties want to track a horizontal slice of issues more broadly, unrelated to where it is deployed or who maintains it, then generic tag could be added in addition. But this would not be a replacement for anything else. We do this for JavaScript for example, and I think these tags work best if they are not automated or generally applied all the time. It is just done ad-hoc when people find it useful to coordinate or distribute certain tasks they find interesting. I'd guess by the same people that would consume the information on those tags.
If it is just about search or discovery for code review, then afaik we don't need a tag for that. The general search in Phab and Gerrit seems to suffice. There's also a certain element of over generalisation where changes may end up merged without awareness or input from maintainers, which can take away oppertunities to learn, and exacerbates the problem of "maintenance" not being accounted for properly in teams, so I would caution there a bit as well. As volunteers you should spend time in ways that interest and engage you best of course, but in my own experience it tends to be more rewarding when you build up famiarity with a certain sets of components more deeply and regularly interact with known individuals, which is different from the scattered approach. Anyway, I suppose that's a different conversation. I agree with Andre this tag already exists and seems close enough. @DannyS712 Any particular reason related to how you contribute that makes you want this tag? Would Browser-Tests suffice for what you're trying to do?
Well I just learned the selenium framework and so would be interested in following related tasks, so I wanted to watch the project (and I can also review simple changes) but I guess Browser-Tests works too if it can be applied more generally