Splitting apiSharing feature file into different files

[paurakhsharma]

Description

The apiSharing feature file is now split into other small manageable feature files

Related Issue

#31531

Motivation and Context

To make adding more tests easier

How Has This Been Tested?

Locally

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Change in file structure

[phil-davis]

This is a reasonable first split of the existing sharing scenarios. Now the plan is to look at each of these feature files and reorganize/expand the test scenarios to achieve a sensible level of API acceptance test coverage of each feature.
During that process, some feature files may be split into more pieces. Because actually there will be quite a lot of scenarios for this stuff, taking into account the various permission combinations, user/group/public... share types and all the things a share receiver can and cannot do with each combination.

[phil-davis]

This will be "interesting" to backport. First compare the "old" sharing feature file in master and stable10 - if they are the same then it is easy. If they are different, then we need to look at why, and then sort out what of the differences go where.

[codecov]

Codecov Report

Merging #31422 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #31422   +/-   ##
=========================================
  Coverage     62.64%   62.64%           
  Complexity    18255    18255           
=========================================
  Files          1145     1145           
  Lines         68481    68481           
  Branches       1234     1234           
=========================================
  Hits          42898    42898           
  Misses        25222    25222           
  Partials        361      361

Flag	Coverage Δ	Complexity Δ
#javascript	52.05% <ø> (ø)	0 <ø> (ø)	⬇️
#phpunit	63.84% <ø> (ø)	18255 <ø> (ø)	⬇️

---

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 e4bd14b...87af0c0. Read the comment docs.

[paurakhsharma]

Backport on #31423

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.