Talk:Catalyst

Protected Testing Area For Security Patches

I know such a feature would likely complicate this effort substantially, but it'd be really nice if Catalyst could support a protected area (TBD) for testing security patches and features. Currently, we have to test security patches locally, which can be very tedious if the patch requires a more advanced setup closer to Wikimedia production. Or we have to pull a security patch down to an mwdebug host, which can also be problematic if a tester does not have the appropriate on-wiki rights which may potentially be required by the security patch. Anyhow, the Security Team would love to discuss such a feature for Catalyst, so let us know if this seems feasible for now. Thanks. SBassett (talk) 16:30, 18 September 2023 (UTC)

While a Protected Testing Area would likely fall outside of scope for the prototype. I would be interested in hearing more and incorporating it into the next iteration (hopefully an ongoing product): either here or in a phabricator task. More specifically, what do you mean by a protected testing area? --Stef Dunlap (talk) 17:31, 19 September 2023 (UTC)

Status of the Catalyst project

Currently there's not much information about Catalyst available publicly on wikitech. I see lots of activity on the phabricator project and also https://gitlab.wikimedia.org/repos/qte/catalyst/catalyst-api (which isn't linked from anywhere, I had to search on Gitlab).

We're interested in implementing E2E testing using Catalyst in the Ultraviolet userscript on Gitlab CI (see phab:T333548). Is there any planned launch date at the moment, and how can community developers get involved? Additionally, where would we look for any news/updates regarding Catalyst? Sportzpikachu (talk) 09:36, 7 June 2024 (UTC)