Skip to content

Conversation

@individual-it
Copy link
Member

Description

UI tests for renaming folders, the logical next step after testing renaming files #27872

One test is known to fail because of #27864 and of course the corresponding rename file test also fails see #27872

This is build on top of #27860 & #27872

Related Issue

https://github.com/owncloud/QA/blob/master/Server/Test_Plan_WebDav_Interface_WebUI.md

Motivation and Context

make Test plan run automatically
https://github.com/owncloud/QA/blob/master/Server/Test_Plan_WebDav_Interface_WebUI.md

How Has This Been Tested?

run the tests in Chrome on local machine

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Copy link
Contributor

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scrolled through the diff. Now I'm not a behat expert but overall it looked good to me 👍

This applies to the other PRs as well on which this PR is based upon (the full diff), so feel free to "merge them all"

@individual-it individual-it changed the title UI test rename folder feature [WIP] UI test rename folder feature May 19, 2017
@individual-it
Copy link
Member Author

closing as the changes are included in #27872

@individual-it individual-it deleted the ui-test-rename-folder-feature branch May 22, 2017 10:41
@lock
Copy link

lock bot commented Aug 3, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants