[Tests-Only] Bump core test commit id to include new sharing tests #1184
Conversation
|
Previous totals for core API scenarios was: https://cloud.drone.io/cs3org/reva/2586/7/7 There are a lot more sharing scenarios now - the run time reached 1 hour! I will split the pipeline... https://cloud.drone.io/cs3org/reva/2594/7/7 - part 1, 7 min https://cloud.drone.io/cs3org/reva/2594/8/7 - part 2, 8 min https://cloud.drone.io/cs3org/reva/2594/9/7 - part 3, 48 min https://cloud.drone.io/cs3org/reva/2594/10/7 - part 4, 12 min Total so far: 1293 scenarios (420 passed, 873 failed) There are so far 129 more scenarios that all fail. Need to also incude core change owncloud/core#37920 Part 3 takes by far the longest - most of the longer more complex scenarios are the sharing ones, and they happen to mostly fall into part 3. |
|
Split into 6 parts now, that happens to split up the sharing suites a bit better:
Grand Total: 949 scenarios (215 passed, 734 failed) |
|
@ishank011 @labkode ready for review. |
This includes resharing tests from ownCloud core in the API test pipelines. The API tests are split into 4 separate pipelines so that the elapsed time stays reasonable.
revaworkflow of:a) share a resource
b) receiver accepts the shared resource
c) receiver sees the resource in their
/Sharesfolder...
The relevant PRs today in core were:
owncloud/core#37916
owncloud/core#37918
owncloud/core#37919
Those add scenarios that do resharing.
Split the ownCloud core API test suite into 6 parts so that each parrt has a reasonnable run time
Adjust the names of some litmus drone steps so there is no confusion about which storage they test.
Create separate storage-publiclink configs for owncloud and ocis storage so that these will be ready for anyone who wants to use them (or drone in the future)