Mobile patch testing with VVV and xip.io

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

I recently started using Varying Vagrant Vagrants and xip.io for real device mobile testing of patches on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets. I go through tickets with patches that change UIUI User interface and drop mobile and desktop screenshots of the patches in action. These screenshots hasten UI feedback and usually reveal visual glitches on mobile that are then patched up, making our mobile experience that little bit better. Until that blue sky someday when I can apply patches to a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. server with a tap, I’ve found VVV and xip.io to be the easiest way to do localhost testing of patches from mobile devices. I’m using Vagrant’s public_network option along with xip.io. This allows me to test from any device on my local network using links like http://build.wordpress-develop.192.168.1.11.xip.io/ without the need for port forwarding, dynamic dns, or hosts file editing. The two resources I used most in setting this up were:

https://github.com/Varying-Vagrant-Vagrants/VVV#the-first-vagrant-up

https://jeremyfelt.com/2015/01/31/various-networking-configurations-vvv/

Working those into something for the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. developer handbook would be a great public service. Patch testing and mobile testing need to be much easier. Let’s all start putting mobile screenshots of our patches on trac and dogfooddogfood The practice of using one's own software, typically bleeding edge (trunk), thus "eating one's own dogfood". This also applies to using one's own APIs internally. the mobile patch testing experience. Setting up and using npm and grunt are currently undocumented in the handbook. There is much confusion about build vs src. Getting to where I could localhost test patches was a struggle.

How do you localhost test patches from physical mobile devices? Do you also use VVV? Have a cool bash_aliases or other script to share?

#beta-testing-flow

bradparbs 8:00 pm on March 16, 2015

Just want to mention that I just added the xip.io configurations for VV (https://github.com/bradp/vv) this weekend, so you’re able to use that as well.
Drew Jaynes 8:31 pm on March 16, 2015

Neat. Might be worth adding a section or article to Core Contributor Handbook. I can help you with that if you like.
Fabien Quatravaux 8:23 am on March 17, 2015

I use ngrok which provides a service similar to xip.io but which needs some installation.
Eric Lewis 9:08 am on March 17, 2015

Can we give VVV the official WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stamp of approval yet
- Ryan Boren 4:01 pm on March 17, 2015
  
  I don’t code anymore and am out of touch with many dev conversations. So read me as openly curious when I ask what this stamp might entail? I think the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. developer handbook is a good vector for infecting WP dev with VVV. Having a VVV section under “Installing a Local Server” seems a good start, something like the ones for MAMP and XAMPP.
  
  grunt, npm, when to use build vs. src, how to patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. against src, and other concepts necessary to creating, applying, and testing patches are pretty much undocumented right now. I, personally, would be just fine with documenting these activities within the context of VVV. VVV does a lot of heavy lifting for you and hides a lot of grief. I want something I can recommend to patch testers, and VVV seems the best candidate.

Comments are closed.

Welcome!

Communication

Share this: