Fix actors e2e test
See original GitHub issueExpected Behavior
Existing tests should pass.
Actual Behavior
== APP == Test Suites: 1 failed, 1 total
== APP == Tests: 8 failed, 1 passed, 9 total
== APP == Snapshots: 0 total
== APP == Time: 9.229 s
== APP == Ran all test suites matching /test\/e2e\/actors.http.test.ts/i.
Steps to Reproduce the Problem
Run E2E tests
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Tests for actors — Leapp 0.15.0 documentation - Read the Docs
These tests provide fabricated input messages for the actor, check the outputs stated in the actor's description. · These tests should not be...
Read more >What is the correct way writing e2e tests? - SQA Stack Exchange
In testing project I have to use Selenium with TestNG. My question is what is the correct way to do this? There are...
Read more >The Most Common Cypress Mistakes - Christian Lüdemann
Not making commands/assertions retry-able; Not creating page objects; Not using dedicated test selectors; Not making tests deterministic; Too many end to end ......
Read more >Why end-to-end tests are flaky, and how to fix them
End-to-end tests are an essential tool to verify that the true ... No maintenance – flakes and refactors are handled entirely by walrus.ai....
Read more >Best Practices - Cypress Documentation
The RWA achieves full code-coverage with end-to-end tests across multiple browsers and device sizes ... Anti-Pattern: Acting like you're writing unit tests.
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
Agreed
Yup, I was thinking about the 1st point but it looks like a TODO on the runtime side? We can check-in with the 2nd point as an immediate fix and I can follow up with dapr/dapr for healthz capabilities in actor.