AnalyzeRe.Client.Test 1.45.9214.35056

• • AnalyzeRe.Client (>= 1.45.9214.35055)
  • Newtonsoft.Json (>= 13.0.1)
  • NUnit (>= 3.12.0)
  • NUnit.Console (>= 3.9.0)
  • NUnit3TestAdapter (>= 3.10.0)
  • RestSharpSigned (>= 105.2.3)

An extensible unit testing framework that ensures all features of the client library work against your target Analyze Re API server. Facilitates testing of new custom features and libraries built off of the Analyze Re Client package.

1.44
- Added support for Machine-To-Machine authentication workflow.

1.44
- Now targets .NET Framework 4.8.

1.42
- Reflection class instances can now be seeded to make their behaviour deterministic.
- Removed the NestedLayerLossSet (now obsolete) from the set of Loss Set types to randomly generate and include in a variety of input-fuzzing tests. Backwards-compatibility tests remain in place.
- Added rules to the random property value generation routines that not only result in a resource valid to Post, but also one that is valid to use in a simulation.

1.41
- Fixed test runs affecting the 'default server URL' in the current user's registry settings.
- Made the sample PortfolioView resources more complex by giving them 3 layer_views rather than 1.

1.40
- Base tests and sample resources added for new layer models (such as ValueAllocator, BackAllocatedLayer, Policy and Fee features)
- Added an additional loss set to each sample layer type to improve the variety of sample resources and coverage.
- Added a base test for random resource generation with validation enabled, which includes assurances that any resource property can either be randomly modified, or can identify whether and why that is not possible (useful for hash collision testing).
- Clarified the AssertAPI.AllPropertiesEqual helper method usage by splitting into 3 methods, with explicit methods for testing POST and PUT responses.

1.39
- Base resource testing suite has been overhauled in a major and backwards-incompatible way:
-- Test methods that used to expect a test resource factory method now just take a reference to a constructed instance.
-- Resources with data upload component are managed more simply, without having to provide a getter for the data endpoint.
-- Tests no longer attempt to toggle client request logging on and off. Instead, more detailed logs are written if and when a test failure occurs.
-- Removed a variety of obsolete constructs such as attempt to cleanup resource by deleting them following a test.
- Some `GenericTest` methods have been removed, renamed or consolidated with the
- Any tests for Layer or LayerView POST success now also assert that metrics can be retrieved on the new analysis without issues.
- Fixed an issue with using the unit testing library using the NUnit test runner on some systems.
- Fixed random resource generation producing invalid resources due to inlined nested filter definitions that contained embedded layer_view references more than one level deep.

1.38
- Fixed random resource generation creating invalid IAPIAnalysis resources due to mixing currencies for which there were no exchange rates available in the linked analysis profile.

1.36
- Adapts to the client-side changes that allow nested layers to reference layers or layer_views in some cases.
-- Reflection-based random resource generation and assertions have been adjusted in accordance. In most cases, helper methods are now more flexible, supporting any ICollection{T} arguments, rather than just List{T} arguments.
- Expanded on Reflection based resource generation utilities in to allow for more in-depth input fuzzing tests.

1.31
- New class `MockResponse.cs` used to mock RestSharp responses for testing without actually making a request.
- Setting the RUN_OFFLINE environment variable to true changes the behaviour of Samples (InjectibleResources) and base test methods to no longer rely on a server connection. Tests requiring a connection will return Inconclusive in this mode.
- Fixed a subtle error in the AssertAPI.AllPropertiesEqual test helper method when it recursed on resources.

1.27
- New TypedLockGuard class reduces contention for thread-safe shared sample resources and improves test performance.
- Source updated to take advantage of modern C#7 language features and their associated performance improvements.
- Reduced logging when the Reflection class is used to generate property values for trivial types.
- Adapt to new best-practices for resolving references introduced in version 1.27 of the client library.

1.26
- Test infrastructure changes to support new types and more numeric limits.
- Changes to default test assumptions surrounding updated platform features.

1.25
- Added additional testing infrastructure for collections.

1.21
- Updated usage and tests for IStoredAPIResource_WithStatus resources to respect the need to do status polling before considering the POST complete.

1.17
- Layer tests reconfigured to also test attributes of layers when inlined within LayerViews
- Reflection-based tests made to ignore resources tagged with the NotSaveable attribute.

1.15
- Added TestSuite_SimulationOptions for detailed tests on Reporting Period and other options.

1.14
- Fixed the TestSuite_LargeDataUpload.YELTStream returning 0 bytes if the requested buffer size was smaller than the first row generated.

1.11
- Removed LossNetOfOccurrenceTerms as an input and output perspective.

1.10
- Adapts to refactoring and namespace changes made in the client library.
- Modified the root namespace to fall outside of AnalyzeRe's core client library.
- Improvements and bug fixes to documentation

1.9:
- Includes source and symbols for debugging.
- Should no longer require projects to also add Json.NET or RestSharp as dependencies.

1.8:
- Backwards incompatible overhaul of unit test framework to simplify resource injection.

1.7:
- Now targets .NET Framework 4.5 to make use of improvements to native compression algorithms.

1.6 and earlier features:
- Injectable test resources for all of the resource types defined by the AnalyzeRe API
- Optional caching and injected resource re-use to allow integration tests to run quickly and in parallel.
- Tests which can serve as examples of every piece of functionality in the library and illustrate a number of error scenarios.
- Reflection-based utilities for generating random valid resources.