@Krenair so nice, thanks :)

Also formally request here https://www.mediawiki.org/wiki/Git/New_repositories/Requests

@Legoktm. Thanks I couldn't remember the page for that. I guess I thought the phabricator project "MediaWiki-Extension-Requests" would be sufficient.

@Jdlrobson I did use BoilerPlate. @phuedx good to know, I'll add the empty directories.

@Aklapper This is an extension request task. The other task includes pushing the extension skeleton to the repo.

While waiting for extension to be approved, QuickSurveys extension skeleton can be found here
https://github.com/rmoen/creepy-guacamole

Requested QuickSurveys extension T107799

@bmansurov, not sure. Didn't have this issue. Seems like the arc uri isn't being set.

Tested and seems go to me. I've added suggestions to some of the setup and a potential solution to the permission issue at https://www.mediawiki.org/w/index.php?title=Talk:Reading/Web/Setting_up_a_staging_environment&oldid=1783997

@Jdlrobson All issues have been addressed. Bundle install now runs for the test user.
Language support for the test page is now added. Git and Git-review configs are being properly setup as the test user. Also I added the arcanist config so pasting should work now.

It seems roles are the way to go. Since labs-vagrant doesn't contain the mediawiki-vagrant plugin, commands like import-dump or the potential for new commands is not there.
Going with a role, there still is the issue of how to best fetch the dump and import it. Seems this is something that loads of effort has already gone into without coming to an acceptable solution.

I'm able to reproduce this on a mobile screen.

Making progress. Some tests still failing. Still working on it.

@Jdlrobson

• Made extension dependency optional
• Now running bundle install in project directory
• Added --paste and removed --noupdates flags

@Tgr Thanks for the knowledge drop. I agree this would be a better solution than having large dumps in the repo and to limit the amount of roles. I'm guessing a hit to the api would be best to get the unparsed content? eg api.php?action=parse&page=PageName&prop=wikitext. Then import_text as a string?

Confirmed that https://gerrit.wikimedia.org/r/#/c/223176/ resolves this. Keep in Todo column now until Jon's patch lands.

https://www.mediawiki.org/wiki/Reading/Setting_up_a_browser_test_instance

@Jdlrobson hmmm well captcha isn't enabled by default and i found an easy way to create an account from the api. I'm going to add that in

I have a install script going at https://github.com/rmoen/Barry-the-Browser-Test-Bot-Installer

After discussing in IRC @yuvipanda I now understand that the intention is to have more projects that are more tightly scoped. I think we agreed on reading-smoketest

@yuvipanda, could you please identify the appropriate place for us to create our instances?

@Jdlrobson Per your feedback, I added browser tests for changing a collection name. There is another edge case to test for when clicking the back button. I hope this one test satisfies until next week, then I can write the edge case test. We need coverage for delete as well, and it would be helpful to delete the collection this test changes the name of because if we don't it will cause the tests to fail as it will not be able to edit another collection the same name if one already exists with that name. Either that, or change the name back to the original name. I still haven't figured out how to best go about that though as I'm just barely learning ruby/cucumber. I hope this made sense, it's late and I'm tired.

@Jdlrobson After much investigation, this doesn't seem to work very well when configuring an extension with extension.json. Since MF isn't yet doing this, hard to replicate expected behavior without a working example.