run testing against nightly tarball

[patrickjahns]

Motivation

should address failures in ui/api tests where the context of notifications app is missing

  `NotificationsContext` context class not found and can not be used.  

@phil-davis @individual-it - its a temporary fix - if we can enable/disable context per installed/available apps that is the favorable way to proceed ( I guess )

[phil-davis]

I guess there is nothing here like core drone.yml INSTALL_NOTIFICATIONS-APP which, as well as installing the app, enables it.

I suspect this will also be annoying when running core webUI tests locally - when running scenarios from webUISharingNotifications suite, notifications app needs to be enabled. When running other webUI tests, for some scenarios, it needs to be disabled.

The location of the notifications app enable/disable control needs to be thought through. Perhaps before/after scenario (or suite) methods could enable it for the things that need it. Then whatever runs those scenarios will get the needed app environment. @individual-it ?

[individual-it]

general discussion about how to deal with apps in the acceptance tests here owncloud/QA#548
for notifications app we currently enable it by an env. variable https://github.com/owncloud/notifications/blob/master/.drone.yml#L71

[phil-davis]

@patrickjahns I think we sorted files_primary_s3 CI against core QA tarballs now?
So this is old and can be closed.

[phil-davis]

@patrickjahns this shows in my list of PRs waiting for review.
Is there anything to do here? Or close?

[PVince81]

@phil-davis please make a decision. if the original issue from the OP "motivation" is obsolete then let's close ?

[phil-davis]

We sorted out this stuff over the last months - acceptance test CI runs against both core master and stable10.