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

Acceptance tests using pre-installed apps_paths #34657

Closed
2 of 3 tasks
phil-davis opened this issue Mar 2, 2019 · 3 comments · Fixed by #35621
Closed
2 of 3 tasks

Acceptance tests using pre-installed apps_paths #34657

phil-davis opened this issue Mar 2, 2019 · 3 comments · Fixed by #35621

Comments

@phil-davis
Copy link
Contributor

phil-davis commented Mar 2, 2019

PR #30889 issue #29839 introduced apps-external as a second apps path on a default installation.

  • review existing appmanagement.feature scenarios to see if they are still "a good thing"
  • add scenarios to confirm the new default path works
  • whatever else might be useful related to this for testing ;)
@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #22485 (test), #31579 (test), #22492 (test), #33690 (cleanup acceptance tests WebDav trait), and #31516 (Acceptance test coding standard changes).

@mmattel
Copy link
Contributor

mmattel commented Mar 26, 2019

References #34898 (Add the apps-external directory during setup only)

@skshetry
Copy link
Member

@phil-davis, I added a few tests, but as the issue is more towards testing installation folder and check where the apps is written to, we need some better way to simulate an actual app install. We might need to use core api's and simulate/emulate installs through use of our custom api's in testing app.

Needs more research.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants