Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests should avoid real HTTP URLs #10393

Open
rrelyea opened this issue Dec 17, 2020 · 4 comments
Open

Tests should avoid real HTTP URLs #10393

rrelyea opened this issue Dec 17, 2020 · 4 comments
Labels
Priority:2 Issues for the current backlog. Product:VS.Client TechDebt Technical debt Type:Test

Comments

@rrelyea
Copy link
Contributor

rrelyea commented Dec 17, 2020

image.png

image

image

image

@aortiz-msft
Copy link
Contributor

@zivkan @sbanni - Given our stance today, do we still need to do work here?

@zivkan
Copy link
Member

zivkan commented Apr 13, 2021

My PR comments were basically "don't write tests that use real URLs/HTTP requests". When dotnet.myget.org was decomissioned, we had tests break (I don't know if it was these tests, or different ones), which broke our builds and our ability to merge PRs, until we fixed it. In the last 2 weeks, we've had a test that makes requests to nuget.smbsrc.net (unrelated to codespaces) occasionally timeout, again breaking our builds.

So, on one hand yes, I still believe that we should change tests that make real HTTP requests to use mocked HTTP tests (or a fake HTTP source running on localhost). On the other hand, we can deal with these types or errors and flakiness when it causes problems, rather than being proactive about it.

But I still wish people would stop writing/copying tests that make real HTTP requests to remote servers.

@zivkan zivkan modified the milestones: Sprint 2021-04, Sprint 2021-05 Apr 26, 2021
@zivkan zivkan modified the milestones: Sprint 2021-05, Sprint 2021-06 Jun 7, 2021
@zivkan zivkan modified the milestones: Sprint 2021-06, Sprint 2021-07 Jul 6, 2021
@zivkan zivkan modified the milestones: Sprint 2021-08, Sprint 2021-09 Aug 2, 2021
@zivkan zivkan modified the milestones: Sprint 2021-09, Sprint 2021-10 Sep 7, 2021
@zivkan zivkan modified the milestones: Sprint 2021-10, Sprint 2021-11 Oct 4, 2021
@nkolev92
Copy link
Member

nkolev92 commented Nov 2, 2021

Is this relevant?

@zivkan
Copy link
Member

zivkan commented Nov 4, 2021

Unless you have information otherwise, I believe my comments in #10393 (comment) stands.

@aortiz-msft aortiz-msft added the Category:Quality Week Issues that should be considered for quality week label Jan 3, 2022
@zivkan zivkan modified the milestones: Sprint 2022-01, Sprint 2022-02 Jan 3, 2022
@zivkan zivkan modified the milestones: Sprint 2022-01, Sprint 2022-02 Feb 7, 2022
@zivkan zivkan removed this from the Sprint 2022-02 milestone Mar 7, 2022
@donnie-msft donnie-msft changed the title discuss/address PR feedback on codespaces work Tests should avoid real HTTP URLs Jan 19, 2024
@donnie-msft donnie-msft added TechDebt Technical debt and removed Category:Quality Week Issues that should be considered for quality week labels Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:2 Issues for the current backlog. Product:VS.Client TechDebt Technical debt Type:Test
Projects
None yet
Development

No branches or pull requests

8 participants