Change rethrowAsync()'s behavior in test mode
See original GitHub issueTo follow the conversation here
From a testing point of view, removing rethrowAsync will greatly reduce the amount of flakiness we see. However, is there a valid use case for doing it in the runtime? Why was it added in the first place? Does it prevent the runtime from blocking when it encounters an error, perhaps?
Can we change rethrowAsync
to console.error()
+ reportErrorToServer()
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
How can I unit test this async method which (correctly) throws ...
ThrowAsync <HttpRequestException> (async () => await service. ... You can basically just change the test method declaration by replacing "void" by "async ...
Read more >async/await .not.toThrow idiomatic check · Issue #1377 - GitHub
when the function is called and returns a promise and it doesn't throw, we should wait for the promise to resolve and then...
Read more >Exceptions - Fluent Assertions
However, we discovered that testing the exception message for a substring is so common, that we changed the default behavior of WithMessage to...
Read more >Async Programming - Unit Testing Asynchronous Code
When the unit test method is changed to await the task, the most natural ... [TestMethod] public async Task CorrectlyFailingTest() { await SystemUnderTest....
Read more >Improving Unit Tests with Fluent Assertions - Code Maze
In this article, we are going to learn how we can improve our unit tests using Fluent Assertions library with .NET project.
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
SG, let’s go with @dvoytenko’s proposal.
@torch2424 since you will be working on the amp-experiment soon, it will be very important to unmute the tests. Assigning to you.
I can’t seem to reproduce this issue anymore. If anyone thinks this is still happening, please reopen this ticket. @dvoytenko @lannka