Skip to content

Releases: launchdarkly/dotnet-test-helpers

2.0.0

17 Aug 19:17
Compare
Choose a tag to compare

[2.0.0] - 2022-08-17

Changed:

  • Removed EOL target frameworks .NET Core 2.1, .NET Framework 4.5.2, and .NET 5.0. Lowest compatible platform versions are now .NET Core 3.1, .NET Framework 4.6.2, .NET 6.0, and .NET Standard 2.0.
  • There is no longer a dependency on JSON.NET; all JSON helpers are now implemented via System.Text.Json.

1.5.0

02 Feb 19:19
Compare
Choose a tag to compare

[1.5.0] - 2022-02-02

Added:

  • In HttpTest, SimpleJsonService.SetJsonConverters. This is necessary because Json.Net doesn't automatically know how to serialize the LaunchDarkly SDK types that are used in our test services (System.Text.Json would know, but we can't use that because we need to be able to use this test code in .NET Framework 4.5.2).

1.4.0

02 Feb 18:18
Compare
Choose a tag to compare

[1.4.0] - 2022-02-02

Added:

  • The following are all in the LaunchDarkly.TestHelpers.HttpTest namespace:
  • HttpServer.Start overload that takes a specific port.
  • IRequestContext.GetPathParam
  • RequestRecorder.Enabled for turning off the default behavior of recording requests.
  • SimpleJsonServer and SimpleResponse helpers for implementing basic test services.

1.3.0

04 Nov 19:57
Compare
Choose a tag to compare

[1.3.0] - 2021-11-04

Added:

  • Handlers.SequentialWithLastRepeating

Fixed:

  • AsMessageHandler() did not work properly with streaming responses in Xamarin.

1.2.0

28 Oct 18:14
Compare
Choose a tag to compare

[1.2.0] - 2021-10-28

Added:

  • In HttpTest, Handlers.AsMessageHandler() and Handlers.Error().
  • More API documentation about how and why to use HttpTest types with either an embedded server or a message handler.

1.1.0

10 Sep 20:55
Compare
Choose a tag to compare

[1.1.0] - 2021-09-10

Added:

  • Assertions, BuilderBehavior, EventSink, JsonAssertions, TypeBehavior

1.0.2

03 May 18:24
Compare
Choose a tag to compare

[1.0.2] - 2021-05-03

Fixed:

  • The HttpHelpers methods Handlers.BodyString, Handlers.BodyJson, and Handlers.StartChunks no longer include a charset in the Content-Type header if you did not specify an encoding. BodyString and BodyJson will still default to using UTF-8 to actually encode the content, since it is necessary to use some encoding, but since charset is not a mandatory part of Content-Type it's appropriate to be able to simulate a condition where the server does not specify it.

1.0.1

27 Apr 19:04
Compare
Choose a tag to compare

[1.0.1] - 2021-04-27

Fixed:

  • Fixed a rare intermittent problem where HttpServer.Start could fail due to a port not becoming available immediately after closing a listener.

1.0.0

27 Apr 18:30
Compare
Choose a tag to compare

[1.0.0] - 2021-04-27

Initial release.