Test IncrementalLoadingCollection itemsPerPage ctor param

[Rosuavio]

Tests different items per page for IncrementalLoadingCollection

PR Type

What kind of change does this PR introduce?

Tests different values for itemsPerPage in the IncrementalLoadingCollection ctor.

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Pull Request has been submitted to the documentation repository instructions. Link:
• Sample in sample app has been added / updated (for bug fixes / features)
  • Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• New major technical changes in the toolkit have or will be added to the Wiki e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Header has been added to all new source files (run build/UpdateHeaders.bat)
• Contains NO breaking changes

Other information

[ghost]

Thanks RosarioPulella for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

[michael-hawker]

@RosarioPulella was this just to check tests, should we commit this or are we waiting on something else still?

[Rosuavio]

The original intention was to explore IncrementalLoadingCollection.LoadMoreItemsAsync(unit count) and providing different values for its param. But that did not seem to work the way I thought it would so instead this PR just tests the itemPerPage from the IncrementalLoadingCollection ctor.

[michael-hawker]

Should we check the interim results for pageSize here as well as we're passing that into the test now?

[Rosuavio]

I am not sure its that easy since these calls are happening asynchronously and we would need to test ageist collection which will be changing as these tasks complete.