Specific patches and versions for additional projects

Yes, this feature is definitely planned!

But at the moment it's really hard to implement because of the way simplytest.me works.

Just closed another duplicating issue #2003034: Ability to select versions when adding additional projects, updating this issues title

Definitely needed. Just tried http://simplytest.me/project/fontello/7.x-1.x?add[]=icon-7.x-1.x to test both the latest devs of these modules, but can't :(

Definitely needed. I maintain the twitter_search module, which currently requires a patch to the twitter module to function correctly. Unfortunately, there's no way at present for me to test a patch to the twitter_search module against the correctly patched version of the twitter module.

Simplytest.me is so wonderful now that adding this sort of capability would just make the wonderfulness so much more wonderful!

Related: #1990932: Introduce Release NIDs for pre-setting project and release.

...it could solve this as well in one go ;)

So, given these following module releases and their respective URLs in d.o:

fontello 7.x-1.0: https://drupal.org/node/2026947
fontello 7.x-1.x-dev: https://drupal.org/node/1929332
icon 7.x-1.0-beta2: https://drupal.org/node/2026939
icon 7.x-1.x-dev: https://drupal.org/node/1950242

...instead of:

http://simplytest.me/project/fontello/7.x-1.x?add[]=icon-7.x-1.x

...it would be:

http://simplytest.me/project/2026947/2026939

...or for their respective dev versions:

http://simplytest.me/project/1929332/1950242

or we could omit the "project" part and have it simply be like so:

http://simplytest.me/2026947/2026939
http://simplytest.me/1929332/1950242

Cool huh?

Hell yeah! +1

The current problem of this issue is that any introduction of new submission features/options would currently drastically increase the complexity of the service.

To clarify what's going on with simplytest.me and how we handle this in future I created #2086033: Relaunching simplytest.me

I'm on it, just give me some time!

thanks :)

Trying to test things for #981936: Detect if patch is applied and if not warn the user & point to instructions and (re)realized that you cannot apply separate patches to specific projects.

Switcheroo requires a 1-liner patch to be applied to Drupal core system.module. This makes it impossible to test almost any patch filed for that project because there is no way to define that this one patch is to be applied to core and another to the actual project. So, simplytest.me will try to apply both patches to either core or the module (whichever was set as the main project in the form) and of course it fails :/

...just wanted to add another use case here.

+1

The issue #2086033: Relaunching simplytest.me is closed as outdated, this means that this issue can be unlocked?
I think this is a really needed feature because sometimes you try to test functionalities of modules that aren't in release yet.

with the relaunch coming (https://new.simplytest.me/) there is no longer a differentiation between main and additional projects

you'll be able to add as many projects as necessary and select a specific version and patches for all of them