search

owncloud / smashbox-testing

Smashbox testing running on DroneCI
MIT License
1 stars 3 forks source link

smashbox - same client different ownCloud versions #5

Open patrickjahns opened 6 years ago

patrickjahns commented 6 years ago

It would be great, to run the combination of each released client and each released owncloud server to ensure conformity

tboerger commented 6 years ago

We are not using released versions on purpose. Initially it has been done that way, but since releases are immutable a red job will stay red forever.

Branches are moving targets and can get fixed.

patrickjahns commented 6 years ago

@tboerger Clients are a moving target right? So I want to know when a changing client breaks with a fixed ownCloud version.

And I want to know when a stable client fails with a moved ownCloud version

tboerger commented 6 years ago

But if the client is a moving target and the owncloud is not, and the suite is red because of the owncloud it can never get green. Same for the opposite direction. That's why this approach have been dropped, because exactly that happened.

tboerger commented 5 years ago

Feel free to do that manually once after a release, but doing it regularly in an automated way doesn't make sense.

patrickjahns commented 5 years ago

@tboerger That is for @owncloud/qa to decide

tboerger commented 5 years ago

This repo handles automated tests on a nightly base. Not one shot tests for fixed releases as explained above.