Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Pricing service tests failing
See original GitHub issuePriceForTravelPolicyIsCorrect and CommandIsProperlyValidated are failing.
Error Message: System.Net.Internals.SocketExceptionFactory+ExtendedSocketException : Cannot assign requested address [::1]:5432
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
What's the real cost of failing to test?
Naturally, it comes at a cost. But retailers will surely pay the price of opting out of the testing process if an expensive...
Read more >How to Fix Flaky Tests - Semaphore CI
Flaky tests hinder development, slow down progress, hide design problems, and can cost a lot of money in the long run.
Read more >Test Failure Rate: Why and how to find your frequently ...
This article explains test failure rate; why tracking frequently failing mobile tests is important, and how Bitrise Insights can help teams ...
Read more >CICD - How To Resolve Failing Tests
Tests must pass reliably and when they don't, to avoid delivery delays, failing test results need to be actionable and so that they...
Read more >Fixing Tests in CI/CD: Why are Your Tests Failing?
There are multiple reasons to take failing tests seriously. First, failed tests can block the delivery of new releases, because the CI/CD ...
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 Free
Top 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
Hi @tugrulelmas, Big thanks for your support for our little project. I am not a big fan of mocking something I control, in this case, a database that is part of my microservice. My personal experience tells me, that having tests that involve a real database is very useful and may reveal many problems especially when using ORM tools. That’s why I’m insisting on moving these test into a separate assembly and run them in an environment that provides all necessary elements. I’ll try to move “integration” test to a separate assembly. These tests do not test Postgresql or MediatR - they test how service interacts with its own database, which is integral part of it.
I moved integration tests into a separate assembly. Now they can be skipped while executing regular build. I’ll open a separate issues for running integration tests