Mapper tests use inline expected context data rather than shared test cases from engine-test-data repository. ## Acceptance criteria - [ ] mapper_test_cases pass (see Flagsmith/engine-test-data#46) - [ ] Remove inline expected context JSON from MappersTest.cs ## Technical context Current implementation uses inline JSON: https://github.com/Flagsmith/flagsmith-dotnet-client/pull/177/files#diff-f851c822fa0e162b75312b6b9ab5dc31d3631179a33360ec77bbb83f4ae7c50eR12-R140 Shared test data: https://github.com/Flagsmith/engine-test-data/pull/46 Related issues: - Flagsmith/flagsmith-python-client#181 - Flagsmith/flagsmith-ruby-client#93 - Flagsmith/flagsmith-java-client#197 - Flagsmith/flagsmith-nodejs-client#228 - Flagsmith/flagsmith-go-client#196 - Flagsmith/flagsmith-rust-flag-engine#26
Mapper tests use inline expected context data rather than shared test cases from engine-test-data repository.
Acceptance criteria
Technical context
Current implementation uses inline JSON:
https://github.com/Flagsmith/flagsmith-dotnet-client/pull/177/files#diff-f851c822fa0e162b75312b6b9ab5dc31d3631179a33360ec77bbb83f4ae7c50eR12-R140
Shared test data: Flagsmith/engine-test-data#46
Related issues: