Restore the skipped compat Firestore and Storage specs

Open
#3,822 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
angular, firebase, typescript

Research direction

Start with the listed compat Firestore specs under src/compat/firestore and src/compat/storage/storage.spec.ts; inspect the top-level and individual pending calls and run the affected browser specs to identify why they were disabled. Check the Firebase SDK v11 flakes in the collection and collection-group specs as well. Done means the underlying failures are fixed, all listed specs run without pending skips, and the browser tests pass.

Written by the indexing model from the issue text.

Description

comp: compat comp: firestore comp: storage type: chore

The browser test suite skips every spec for three compat Firestore classes and one compat Storage spec, so CI does not check those APIs:

  • src/compat/firestore/collection/collection.spec.ts, src/compat/firestore/collection-group/collection-group.spec.ts and src/compat/firestore/document/document.spec.ts call pending("These are pretty broken, investigate.") in their top-level beforeEach, which skips every spec in those files (AngularFirestoreCollection, AngularFirestoreCollectionGroup, AngularFirestoreDocument). This came in with #3586.
  • Inside the first two files, four more specs carry their own pending for flakes with Firebase SDK v11, and will need the same look once the beforeEach skip is gone.
  • src/compat/storage/storage.spec.ts skips "should upload, get metadata, and delete" with pending("Not sure why this is busted.").

The compat support statement in docs/compat.md (#3810) commits to bug fixes for these APIs, so their specs should run. The work is to find out why each one was disabled, fix the spec or the code, and remove the pending calls.

Dominant language
TypeScript
Stars
7.8k
Forks
2.1k
Avg merge
2d 22h
Merged PRs (30d)
25

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angularfire

All issues in angular/angularfire

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.