[01:18:17] <wm-bb>	 <u99of9> That task is specifically about built-ins, is that what you're asking about the procedure for? (re @Sannita: Hi all, we're doing some evaluation of https://phabricator.wikimedia.org/T413841 and we wanted to know more about the current pr...)
[09:19:42] <wm-bb>	 <Sannita> Yes (re @u99of9: That task is specifically about built-ins, is that what you're asking about the procedure for?)
[10:42:18] <wm-bb>	 <Npriskorn> I don't think there is an established procedure, I pinged David last, that worked fine. 😀
[13:16:13] <wm-bb>	 <Al> Yes. Maybe that’s why he filed the ticket 😏 So long as we’re only talking about tests for built-ins, I don’t see any drawbacks. It’s actually more of a concern for functions with more than one implementation, where connected tests influence implementation selection. So, to refine my earlier comment about non-functioneers, anyone should be able to connect or disconnect
[13:16:13] <wm-bb>	 <clipped message>
[13:16:13] <wm-bb>	 <Al> a test for a function with zero or one connected implementation (when a new test could be connected automatically). (re @Npriskorn: I don't think there is an established procedure, I pinged David last, that worked fine. 😀)
[13:17:09] <wm-bb>	 <Al> …zero or one… (re @Al: I’m thinking perhaps anyone who can create a Z20/test case should also be entitled to connect and disconnect them if the functio...)