I ll start my response here by saying

[steady hill]

Thanks for taking time to reply.

Basically, I'm evaluating whether it's worth to invest into end-to-end testing of any of my modules. I certainly don't want to test compatibility with different Foundry versions manually, for example. Same for different game systems in certain cases.

Ideally I don't want to do it on my own infrastructure (for various reasons) and I assumed you wouldn't want any automation to produce a significant load on your download site (I assume you don't have it behind any kind of CDN, didn't check it either).

Am I correct in understanding that license multiuse is only considered as such if a non-zero number of players (non-GMs) is logged in at the same time on different Foundry instances with the same license key?

So basically having separate short-lived GM-only Foundry instances is fine?

[radiant condor]

if you are constantly hitting our license verification server you are very likely to end up with the license key revoked. I wouldn't recommend going down this avenue.

[steady hill]

OK, so basically this prevents this whole scenario. Well, I suppose potential bugs it is, then.

I'm just curious: does the Foundry team employ any UI tests? I would appreciate if you would be able to answer, but understand if you cannot.

[radiant condor]

I'm not on the dev team myself, but i believe we do have some unit tests that run for our end---though not UI related ones.