Clean up test suite from 3.x.x upgrade
See original GitHub issueAs part of merging in #717 to upgrade to the Firebase 3.x.x
SDK, we made a lot of testing changes and the test suite is now pretty unstable and does not pass in Travis. We need to clean things up in general and specifically focus on:
- Defining a better
tick()
method to force the digest loop to update. - Make sure our promise chains are set up properly and that we are waiting for things properly. For example, this test does not wait for the Firebase
set()
to complete. - Make sure the e2e tests actually pass (e.g. the Todo app has two failing tests).
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
unittest — Unit testing framework — Python 3.11.1 ...
A test fixture represents the preparation needed to perform one or more tests, and any associated cleanup actions. This may involve, for example, ......
Read more >Java Unit Testing with JUnit and TestNG
You can perform clean-up operations by overriding tearDown() . Each test method runs on its own TestCase instance with its own set of...
Read more >googletest/primer.md at main - GitHub
In this case, TearDown() is not needed since we don't have to clean up after each test, other than what's already done by...
Read more >Testing best practices - GitLab Docs
Without careful preparation before a test runs, and cleanup afterward, a test can change data in a way that affects the behavior of...
Read more >Testing - Spring
This chapter covers Spring's support for integration testing and best practices for unit testing. The Spring team advocates test-driven ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, version 2.0.0 of AngularFire has been released and you can see the change log here. This bug is tracking the build failures. We wanted to get the release out instead of waiting for us to tackle all the build failures which seemed more like testing issues than actual code issues.
@abehaskins - I think we can close this one now that the tests are fast and run reliably. Please re-open if there was anything else you meant to do.