Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cleanup acceptance tests WebDav trait #33690

Closed
3 of 6 tasks
individual-it opened this issue Nov 29, 2018 · 8 comments
Closed
3 of 6 tasks

cleanup acceptance tests WebDav trait #33690

individual-it opened this issue Nov 29, 2018 · 8 comments

Comments

@individual-it
Copy link
Member

individual-it commented Nov 29, 2018

@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #22492 (test), #22485 (test), #31579 (test), #32559 (acceptance tests - stop uploading when receiving an error), and #32510 (fix API acceptance test steps, so that they really use old/new webdav path).

@phil-davis
Copy link
Contributor

FeatureContext includes BasicStructure and that includes all the other traits like WebDav

We can consider having different contexts for areas of test functionality that can be logically separated. e.g. keep FeatureContext having all the knowledge about users (and user attributes, password...), groups, whatever else is "core" to nearly every test scenario. And then make other context files for stuff that is specific to particular parts of the testing - TagsContext for example, or WebDavContext

Then we could not have trait files at all (maybe?) and each suite in behat.yml just needs to list the contexts that it needs - like now, but there will be more different contexts.

Comments please...

@phil-davis
Copy link
Contributor

Assigned @paurakhsharma to look into the structure and suggest a design for doing this

@paurakhsharma
Copy link
Member

paurakhsharma commented Dec 6, 2018

  • use test helpers where possible e.g. WebDavHelper::makeDavRequest and not WebDav::makeDavRequest

Doesn't this make our php files longer then it is? @phil-davis @individual-it

@individual-it
Copy link
Member Author

done a bit of work, there is more to do putting it back into backlog

@individual-it
Copy link
Member Author

moving to next sprint for remaining work

@phil-davis
Copy link
Contributor

Added to QA/CI project. First someone needs to spend a few minutes working out what is still of value to do here, and then a useful direction to go.

@dpakach dpakach self-assigned this Jan 16, 2020
@dpakach
Copy link
Contributor

dpakach commented Jan 16, 2020

Closing this as it is moved to new issue #36770

cc @phil-davis @individual-it

@dpakach dpakach closed this as completed Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants