refactor: Reorganize type definition test files

[dplewis]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

All definition tests are contained in single file. This is hard to maintain and isn't scalable.

Ref: #2012

Approach

• Allow for multiple tests files
• Use same test format as unit and integration tests
• Create a POC

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)

[parse-github-assistant]

Thanks for opening this pull request!

• ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (478147c) to head (5569133).

Additional details and impacted files

@@            Coverage Diff            @@
##             alpha     #2488   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         6268      6268           
  Branches      1468      1452   -16     
=========================================
  Hits          6268      6268           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dplewis]

@mtrezza I added one example for Parse.Session since it's a small implementation. The community can addon more files in the future. An added benefit is we can ensure that all definitions are accounted for once the tests are migrated. In this case Parse.Session has all types tested. You can check by comparing it to the definition file ParseSession.d.ts

[mtrezza]

What is this needed for?

[dplewis]

That’s how I’m able to use it and describe in the definition test files. It’s also useful if we ever convert the unit tests to Typescript