[wp-trac] [WordPress Trac] #43395: Add Automated E2E Tests for Core Updates
WordPress Trac
noreply at wordpress.org
Mon Feb 26 05:22:54 UTC 2018
#43395: Add Automated E2E Tests for Core Updates
-----------------------------+--------------------
Reporter: jorbin | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: 4.9.5
Component: Upgrade/Install | Version:
Severity: normal | Resolution:
Keywords: 2nd-opinion | Focuses:
-----------------------------+--------------------
Comment (by pento):
I've been chatting to @dd32 about this, I think we've all come to similar
conclusions.
Docker is definitely the best option here, as we're going to need to test
a bunch of variations of WordPress versions (both being upgraded from and
to), PHP versions, file permissions, etc. Dion has a more comprehensive
list of variations that he'll post to this ticket.
The first phase should probably just be something super simple. Use WP-CLI
to install 4.9.0, then run `wp_maybe_auto_update()` to force the update
synchronously.
This will give us something to base it on, we have quite a few Docker
experts in the WordPress Core community who can contribute to expand this,
too.
I hacked together a [https://github.com/pento/wordpress-
develop/tree/try/docker wordpress-develop Docker config] a few weeks ago,
some of this could be reused as the basis for this project, but I think
this would be best done in a repo outside of wordpress-develop. We're
building a tool that installs various versions of WordPress, wordpress-
develop doesn't really have any relation to it.
As far as timing goes, I may have a little time in the coming weeks,
though Gutenberg is still taking most of my time. If someone wants to run
with this in the mean time, we can definitely get a wordpress-e2e repo
going on the GitHub org for better collaboration.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43395#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list