You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clone the testing app into the apps-external folder, which is where not-built-in apps should get installed anyway.
Adjust tests/lib/DB/MigrationsTest.php so that it does not use the testing app as an example app for its tests. Use another one of the built-in apps - I picked files_sharing.
Motivation and Context
The testing app was put into a separate repo a few months ago.
At the moment we are cloning it into the apps folder of core when running drone CI.
The PHP unit tests scan all code in the apps folder looking for PHP unit tests to run - see https://github.com/owncloud/core/blob/master/tests/apps.phploadDirectory()
That finds the apps/testing folder. So the unit tests in the testing app get run.
When doing core PRs that make non-compatible PHP unit test changes (e.g. bumping to a new major version of PHP unit, and implementing new features of PHP unit etc.), then the testing app unit tests sometimes fail, because they are from the separate testing app that has not had its unit test code updated yet.
How Has This Been Tested?
CI
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Database schema changes (next release will require increase of minor version instead of patch)
Breaking change (fix or feature that would cause existing functionality to change)
Technical debt
Tests only (no source changes)
Checklist:
Code changes
Unit tests added
Acceptance tests added
Documentation ticket raised:
Open tasks:
Backport (if applicable set "backport-request" label and remove when the backport was done)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Clone the
testingapp into theapps-externalfolder, which is where not-built-in apps should get installed anyway.Adjust
tests/lib/DB/MigrationsTest.phpso that it does not use thetestingapp as an example app for its tests. Use another one of the built-in apps - I pickedfiles_sharing.Motivation and Context
The
testingapp was put into a separate repo a few months ago.At the moment we are cloning it into the
appsfolder of core when running drone CI.The PHP unit tests scan all code in the
appsfolder looking for PHP unit tests to run - see https://github.com/owncloud/core/blob/master/tests/apps.phploadDirectory()That finds the
apps/testingfolder. So the unit tests in the testing app get run.When doing core PRs that make non-compatible PHP unit test changes (e.g. bumping to a new major version of PHP unit, and implementing new features of PHP unit etc.), then the
testingapp unit tests sometimes fail, because they are from the separatetestingapp that has not had its unit test code updated yet.How Has This Been Tested?
CI
Types of changes
Checklist:
Open tasks: