Hey there @micheleaz and sorry for the late response.
No, I think you’re fine with having one project, thats all good. I was specifically asking for what the results should look like because of an upcoming feature we plan.
As you may have noticed, when you create a project, you end up with a
default.endpoints.json file. Modifying or adding new endpoints essentially persists those to said file. Now given the case that e.g you want to run your tests on Mac and Win, you can create another json file which targets mac and e.g includes Safari, but the Win one contains Edge (legacy) and IE. So this way you can split up execution environments by individual json files.
Now our upcoming plans are to enable users to store arbitrary data in said file. These data will then be converted to environment variables and can be accessed by your testcode.
Now long story short, this might be exactly what would help solve your case. Because you’d now have for each Server an individual json file, containing the url as additional data, which then can be used within the test to forward the environment-specific url.
I hope that above doesn’t sound too complicated, the actual usage is going to be pretty straight forward and of course also introduced with a HowTo article.