TestBase.HttpClient.Fake 4.2.0

dotnet add package TestBase.HttpClient.Fake --version 4.2.0
NuGet\Install-Package TestBase.HttpClient.Fake -Version 4.2.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="TestBase.HttpClient.Fake" Version="4.2.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add TestBase.HttpClient.Fake --version 4.2.0
#r "nuget: TestBase.HttpClient.Fake, 4.2.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install TestBase.HttpClient.Fake as a Cake Addin
#addin nuget:?package=TestBase.HttpClient.Fake&version=4.2.0

// Install TestBase.HttpClient.Fake as a Cake Tool
#tool nuget:?package=TestBase.HttpClient.Fake&version=4.2.0

TestBase gives you a flying start with

  • fluent assertions that are simple to extend
  • sharp error messages
  • tools to help you test with “heavyweight” dependencies on
    • AspNetCore.Mvc, AspNet.Mvc 3-5, or WebApi Contexts
    • HttpClient
    • Ado.Net
    • Streams & Logging
  • Mix & match with your favourite test runners & assertions.

TestBase.HttpClient.Fake

//Arrange
var httpClient = new FakeHttpClient()
                .SetupGetUrl("https://host.*/").Returns(request=> "Got:" + request.RequestUri)
                
                .SetupGetPath("/uri[Pp]attern/").Returns("stringcontent")
                
                .SetupPost(".*").Returns(response)

                .SetupPost(".*", new byte[]{1,2,3}).Returns(otherResponse)

                .SetupPost(".*", "a=1&b=2")
                .Returns(
                            request => "You said : " + request.Content.ReadAsStringAsync().ConfigureFalseGetResult(),
                            HttpStatusCode.Accepted)

                .Setup(x=>x.RequestUri.PathAndQuery.StartsWith("/this")).Returns(response)
                
                .Setup(x=>x.Method ==HttpMethod.Put)
                .Returns(new HttpResponseMessage(HttpStatusCode.Accepted));

// Act
var putResponse = await httpClient.PutAsync("http://localhost/thing", new StringContent("{a=1,b=2}"));
var postResponse= await httpClient.PostAsync("http://[::1]/", new StringContent("a=1&b=2"));

//Debug
httpClient.Invocations
            .ForEach(async i =>Console.WriteLine("{0} {1}",i.RequestUri, 
                                                await i.Content.ReadAsStringAsync()));

            
//Assert
putResponse.StatusCode.ShouldBe(HttpStatusCode.Accepted);
postResponse.ShouldBe(response); // ==> SetupPost(".*").Returns(response) was the first 
                                    // matched setup. Setups are tried in first-to-last order.                                            

httpClient.Verify(x=>x.Method ==HttpMethod.Put, "Expected Put, but no matching invocations.");
httpClient.Verify(
                    x=>x.Method ==HttpMethod.Post 
                    && x.Content.ReadAsStringAsync().ConfigureFalseGetResult()=="a=1&b=2",
                    "Expected Post a=1&b=2");

httpClient.VerifyAll(); // ==> "Exception : 4 unmatched expectations"

TestBase

Chainable fluent assertions get you to the point concisely.

UnitUnderTest.Action()
  .ShouldNotBeNull()
  .ShouldEqualByValueExceptFor(new {Id=1, Descr=expected}, ignoreList )
  .Payload
  .ShouldMatchIgnoringCase("I expected this")
	.Should(someOtherPredicate);

.ShouldEqualByValue().ShouldEqualByValueExceptFor(...).ShouldEqualByValueOnMembers()
  work with all kinds of object and collections, and report what differed.
string.ShouldMatch(pattern).ShouldNotMatch().ShouldBeEmpty().ShouldNotBeEmpty()
.ShouldNotBeNullOrEmptyOrWhiteSpace().ShouldEqualIgnoringCase()
.ShouldContain().ShouldStartWith().ShouldEndWith().ShouldBeContainedIn().ShouldBeOneOf().ShouldNotBeOneOf()
numeric.ShouldBeBetween().ShouldEqualWithTolerance()....GreaterThan....LessThan...GreaterOrEqualTo ...
ienumerable.ShouldAll().ShouldContain().ShouldNotContain().ShouldBeEmpty().ShouldNotBeEmpty() ...
stream.ShouldHaveSameStreamContentAs().ShouldContain()
value.ShouldBe().ShouldNotBe().ShouldBeOfType().ShouldBeAssignableTo()...
.ShouldAll(predicate), .SingleOrAssertFail()...

See also

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp1.0 was computed.  netcoreapp1.1 was computed.  netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard1.6 is compatible.  netstandard2.0 was computed.  netstandard2.1 was computed. 
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen30 was computed.  tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on TestBase.HttpClient.Fake:

Package Downloads
FixtureBase

Don't spend hours writing code to mock a dozen dependencies, and more hours debugging it. Just write your test code, and let FixtureBase create the dependencies for you. FixtureBase constructs your UnitUnderTest to test your codebase end-to-end, with external dependencies auto-faked and automatically injected in just the right place; even constructor dependencies that are several layers deep. You just write your tests: ``` public class FixtureBaseExample : FixtureBaseWithDbAndHttpFor<AUseCase> { [Fact] public void UUTSendsDataToDb() { var newDatum = new Datum{Id=99, Name="New!" }; UnitUnderTest.InsertDb(newDatum); Db.ShouldHaveInserted("Data",newDatum); } [Fact] public void UUTreturnsDataFromDbQuerySingleColumn() { var dbData = new[] { "row1", "row2", "row3", "row4"}; Db.SetUpForQuerySingleColumn(dbData); UnitUnderTest.FromDbStrings().ShouldEqualByValue(dbData); } [Fact] public async Task UUTGetHttpReturnsDataFromService() { var contentFromService = "IGotThis!"; HttpClient .Setup(m => true) .Returns(new HttpResponseMessage(HttpStatusCode.OK) {Content = new StringContent(contentFromService)}); (await UnitUnderTest.GetHttp()).ShouldBe(contentFromService); HttpClient.Verify(x=>x.Method==HttpMethod.Get); } } ```   The included examples demonstrate FixtureBases for applications which depend on Ado.Net IDbConnections and on HttpClient network connections. - To create your own FixtureBase with your own preferred Fakes, see the examples at <https://github.com/chrisfcarroll/ActivateAnything/blob/master/FixtureBase/FixtureExample.cs.md> - For how it's done, see <https://github.com/chrisfcarroll/ActivateAnything/blob/master/FixtureBase/FixtureBase.cs> Construction is done by - [ActivateAnything](https://www.nuget.org/packages/ActivateAnything)   Faking is done by - [TestBase.AdoNet](https://www.nuget.org/packages/TestBase.AdoNet) - [TestBase.HttpClient.Fake](https://www.nuget.org/packages/TestBase.HttpClient.Fake) For more tools focussed on cutting the cost of unit testing, see also: - [TestBase](https://www.nuget.org/packages/TestBase) - [TestBase.AspNetCore.Mvc](https://www.nuget.org/packages/TestBase.AspNetCore.Mvc) - [TestBase-Mvc](https://www.nuget.org/packages/TestBase-Mvc) - [TestBase.AdoNet](https://www.nuget.org/packages/TestBase.AdoNet) - [TestBase.HttpClient.Fake](https://www.nuget.org/packages/TestBase.HttpClient.Fake) - [Serilog.Sinks.ListOfString](https://www.nuget.org/packages/Serilog.Sinks.Listofstring) - [Extensions.Logging.ListOfString](https://www.nuget.org/packages/Extensions.Logging.ListOfString)

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
4.2.0 2,965 12/2/2018
4.1.4.3 5,851 11/20/2018
4.1.4 1,768 11/5/2018
4.0.9 2,201 3/23/2018
4.0.7.1 2,025 3/22/2018
4.0.7 1,987 3/22/2018

ChangeLog
---------
4.2.0   TestBase.FakeHttpClient.SetupGet() and SetupPost() overloads
4.1.4.3 Release for both netstandard and net45
4.1.4   TestBase.FakeHttpClient stepped down to netstandard 1.2
4.1.3.1 Corrected Assertion.ToString() to show BoolWithString detail. Added ShouldEqualByValueOnMembers()
4.0.9   Removed dependency on net4 version of Mono.Linq.Expressions
4.0.8   Separated Serilog.Sinks.ListOfString and Extensions.Logging.StringListLogger
4.0.7   Added TestBase.FakeHttpClient. Added Should(predicate,...) as synonym of ShouldHave(predicate,...)
4.0.6.2 TestBase.Mvc can run controller actions on aspnetcore using controller.WithControllerContext()
4.0.5.2 TestBase.Mvc partially ported to netstandard20 / AspNetCore
4.0.4.1 StreamShoulds
4.0.3   StringListLogger as MS Logger and as Serilogger
4.0.1   Port to NetCore
3.0.3   Improves FakeDb setup
3.0.x   adds and/or corrects missing Shoulds()
2.0.5   adds some intellisense and FakeDbConnection.Verify(..., message,args) overload