Skip to content

fix broken link #1222

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 11, 2016
Merged

fix broken link #1222

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/core/testing/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ dependencies on infrastructure. These tend to make tests slower and
more brittle, and thus should be reserved for integration tests. You
can avoid these hidden dependencies in your application code by following
the [Explicit Dependencies Principle](http://deviq.com/explicit-dependencies-principle/)
and using [Dependency Injection](https://docs.asp.net/en/latest/standard/dependency-injection.html)
and using [Dependency Injection](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection)
to request your dependencies from the framework. You can also keep your
unit tests in a separate project from your integration tests, and ensure
your unit test project doesn’t have references to or dependencies on
Expand Down