I am trying to test a patch for a contributed module with D9.
But I don't see a way to do that on simplytest.me.
The issue is that if I enter my module name where it says "Enter a project name", I can choose my module patch under "Advanced options", but then I can't choose the core version - STM will default to installing Drupal 8.9, not D9.0 like I want.
If I enter "Drupal core" where it says "Enter a project name", I can choose Drupal 9.0 and add my module under "Advanced options", but then I can only specify a CORE patch, not a MODULE patch.
I would like a way to specify core Drupal 9.0, a specific module, AND a patch for that specific module and have all this run on STM.
Specificially, this is for the Fivestar module version 8.x-1.x to test the fix in #3158105: Can't click gear icon in manage display to change settings, but the specific module/patch involved shouldn't be a factor here. The module is fully D9 compatible.
This use case of testing a module patch on simplytest.me is the main way I use simplytest.me - as part of issue queue support. This works great for Drupal 8, and I would find it very useful to do the same in Drupal 9.
Comments
Comment #2
kristen polWhile we're at it, it would be great to be able to choose the version of each module rather than it using the most recent version. :)
Comment #3
pameeela commentedI think that this also prevents you from selecting a version when using a core patch + contrib module? E.g. I usually like to add devel module when testing patches so I can generate dummy content. But it seems if you select a module at all it defaults to 8.9.x even if the patch is a core patch.
Comment #4
kristen polSee the re-design work here: #2946735: Create a new design/UX
Comment #5
tr commentedThe designs look nice but they don't address the issue because the form fields are the same as the current design - they're missing a way to associate patches with specific module rather than with the main project. Also, the second design #2946735-9: Create a new design/UX is missing the description text that tells the user what will be done with the entered patch.
Comment #6
kristen polI was told that the wireframes in comment 2 should reflect what the new form fields should be:
https://www.drupal.org/files/issues/2018-03-08/simplytest-ui.png
Comment #7
tr commentedOh, I see. The images from #2 don't show up in the issue summary for #2946735: Create a new design/UX - I was looking at #6 and #9. It's still not clear to me from reading the issue which of the designs is the "chosen" one, but if it's #2 then that looks like it will address this issue.
Comment #8
kristen polAgreed. It wasn't obvious to me and I thought it was #9 but then was told it was #6 but then pointed out the same thing as you (that it just has the same form fields as now) and then was directed to #2. :) I guess I'll put a comment on that issue to explain this so others aren't also confused.
Comment #9
pameeela commentedTagging with the initiative since we're all involved :)
Comment #10
kristen pol@pameeela Did you mean to tag a different issue? I thought bugsmash was for core only and for bugs only. ?
Comment #11
pameeela commentedYeah I'll remove, the conversation was ongoing when I did this and I can see it has decisively landed on core bug reports only!
Comment #12
Lal_Planning to work on this
Comment #13
nerdsteinTo do this issue properly, we need to make the React components missing from the design. And, we need the module code and YML code updated. While we are at it, we need to refresh the YML files from the 7.x-1.x branch so we're incorporating recent changes
Comment #14
Lal_Also do you think the version name might create problem for example the module is `Examples for Developer` using new release name ie 3.0.x well this should ran on D9.
Comment #15
Lal_Looks like semantic versioning is messing up the logic https://www.drupal.org/project/simplytest/issues/3163494
Comment #16
mglaman@Lal_ wanna try this on https://beta.simplytest.me/? I think it'll work.