UI tests for upload feature

[individual-it]

Description

UI tests that check the basic upload feature

Related Issue

owncloud/QA#437

Motivation and Context

• the upload tests are split into 2 feature files. One for general uploads one for edge cases. That is because we want to test edge cases but if developers or management is reading the feature files (BDD) they don't need to be bored by reading the edge cases
• other tests are touched because of renaming a file in the skeleton folder
• the files to upload have partly the same names like the files in the skeleton but different content to test overwriting

How Has This Been Tested?

run locally, run on travis

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.

[individual-it]

backport in #29574

[codecov]

Codecov Report

Merging #29573 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #29573   +/-   ##
=========================================
  Coverage     61.71%   61.71%           
  Complexity    17482    17482           
=========================================
  Files          1047     1047           
  Lines         57714    57714           
=========================================
  Hits          35619    35619           
  Misses        22095    22095

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 75e6bd7...754035c. Read the comment docs.

[lock]

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.