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

[Tests-Only] Refactor apiShareCreateSpecial1 to use Shares folder #37938

Merged
merged 3 commits into from
Sep 28, 2020

Conversation

haribhandari07
Copy link
Contributor

Description

This PR makes apiShareCreateSpecial1 test scenarios to be valid in both oC10 and OCIS. OCIS always puts received shares into a folder called Shares for the share receiver. On OCIS, auto-accept shares is always disabled.

Related Issue

Motivation and Context

How Has This Been Tested?

  • CI

Screenshots (if appropriate):

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:
  • Changelog item, see TEMPLATE

@codecov
Copy link

codecov bot commented Sep 24, 2020

Codecov Report

Merging #37938 into master will decrease coverage by 0.58%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff              @@
##             master   #37938      +/-   ##
============================================
- Coverage     64.71%   64.13%   -0.59%     
  Complexity    19442    19442              
============================================
  Files          1286     1285       -1     
  Lines         76019    75978      -41     
  Branches       1336     1336              
============================================
- Hits          49196    48727     -469     
- Misses        26429    26857     +428     
  Partials        394      394              
Flag Coverage Δ Complexity Δ
#javascript 54.06% <ø> (ø) 0.00 <ø> (ø)
#phpunit 65.24% <ø> (-0.65%) 19442.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ Complexity Δ
lib/private/DB/PostgreSqlMigrator.php 0.00% <0.00%> (-100.00%) 4.00% <0.00%> (ø%)
...ilder/ExpressionBuilder/PgSqlExpressionBuilder.php 0.00% <0.00%> (-88.89%) 3.00% <0.00%> (ø%)
lib/private/DB/AdapterOCI8.php 0.00% <0.00%> (-86.67%) 4.00% <0.00%> (ø%)
...ivate/Files/ObjectStore/HomeObjectStoreStorage.php 0.00% <0.00%> (-86.67%) 8.00% <0.00%> (ø%)
lib/private/DB/AdapterPgSql.php 0.00% <0.00%> (-85.72%) 2.00% <0.00%> (ø%)
...Builder/ExpressionBuilder/OCIExpressionBuilder.php 0.00% <0.00%> (-85.19%) 18.00% <0.00%> (ø%)
lib/private/DB/OracleMigrator.php 0.00% <0.00%> (-76.85%) 10.00% <0.00%> (ø%)
lib/private/DB/OracleConnection.php 0.00% <0.00%> (-63.89%) 12.00% <0.00%> (ø%)
lib/private/Files/Storage/Wrapper/Availability.php 10.38% <0.00%> (-40.26%) 80.00% <0.00%> (ø%)
lib/private/Autoloader.php 73.17% <0.00%> (-19.52%) 20.00% <0.00%> (ø%)
... and 30 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f1f272d...1724acc. Read the comment docs.

@haribhandari07 haribhandari07 force-pushed the refactor-shareCreateSpecial1 branch 2 times, most recently from 6393abe to bf3cf0d Compare September 24, 2020 10:26
@phil-davis
Copy link
Contributor

I also raised issue #37944 - it applies to a lot of these "sharing to share_folder" scenarios in multiple PRs. So we can sort that out next week.

Copy link
Contributor

@dpakach dpakach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some scenarios have
Then the status code should be <code> step which checks the status of accepting the share not creating the share.
I have not commented on all of them. Please go through all the scenarios fix those to check the status of Sharing step.

Comment on lines +39 to +71
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.

Comment on lines +143 to +206
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.

Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.

Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.

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

Successfully merging this pull request may close these issues.

3 participants