E2E tests for Uploading New Version of Themes & Plugins

[juhise]

This is the feature of showing notice when uploading a new version of an already installed theme/plugin

This ticket is to add E2E test for this feature

Related Trac Ticket: https://core.trac.wordpress.org/ticket/54334

---

# Test Scenario

## Install the old plugin from the uploader

Given that plugin zip is present
Go to Plugin -> Add New
Click on Upload Plugin
Choose File: Upload the older version of the plugin
When I click on Install, I should see the Activate Plugin button

I go to plugins->installed plugin and should see old plugin version

## Install the new plugin from the uploader

Given that plugin zip is present
Go to Plugin -> Add New
Click on Upload Plugin
Choose File: Upload the new version of the plugin
When I click on Install, I see the `Replace current with uploaded
` button
When I click on “Replace current with uploaded” I should see the Activate Plugin button

I go to plugins->installed plugin and should see the new plugin version

## Cancel the old version upload
Given that plugin zip is present
Go to Plugin -> Add New
Click on Upload Plugin
Choose File: Upload the older version of the plugin
When I click on Cancel and go back, I should be on plugin-install.php URL

Related Trac Ticket: https://core.trac.wordpress.org/ticket/54334

## Tests scenarios

• Replace an installed theme with a different version by uploading
• Cancel and go back while uploading a new theme version

Related Trac Ticket: https://core.trac.wordpress.org/ticket/54334

## Test Scenario

• Replace the old theme by uploading a new version
• Cancel and go back to the old theme while uploading a new version

@kevin940726 @tellthemachines @hellofromtonya this PR is ready for reviews.
cc @juhi123

Hi @kevin940726 👋🏻
Any updates for your review? I also created this PR ​https://github.com/WordPress/wordpress-develop/pull/1858 for the helpers for e2e in Core.

Hi @JustinyAhin! Sorry, been busy with 5.9 and other things. I'll try to find some time to review this 🙇‍♂️ !

Hi @JustinyAhin! Sorry, been busy with 5.9 and other things. I'll try to find some time to review this 🙇‍♂️ !

Thank you, Kevin :)

[hellofromTonya]

As today is 5.9 Beta 1, moving this to 6.0. Tests are not strictly bound to a milestone. Once the patch is approved and ready, it can committed.

Related Trac Ticket: https://core.trac.wordpress.org/ticket/54334

## Test Scenario

• Replace the old plugin when uploading a new version
• Cancel and go back to the old plugin while uploading a new version

Cc @kevin940726, when you have some time, this PR might need some review.

[hellofromTonya]

Moving this to 6.1, as 6.0 RC1 tomorrow. As this is part of the test suite, it can be committed at any time when reviewed and ready.

[desrosj]

@juhise @justinahinon could you refresh these PRs to include all of the changes to trunk since created?

This has already been punted twice, so I'm going to punt this to Future Release. Once the PRs are refreshed and a Core committer is able to focus on getting these merged, it can be moved back to a numbered milestone.

I have merged the trunk into this.

[costdev]

Looks like ​the PR needs to be changed to compare against WordPress:trunk instead of WordPress:master.

[juhise]

@costdev I made the change, hope it's fine now.