You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2018. It is now read-only.
The tests are organized in a confusing structure and not as we usually organize them. There are a lot of redundant integration tests and some adapters lack unit tests.
1. This test suite can be used to ensure we are spec compliant. It can either be used to generate test code or parsed and tested.
2. This folder has lots of integration tests for all operations (we should remove redundancy)
3. Add integration tests for "Test" operation
4. Clean up test object model classes - simplify by adding them to test classes that use them
5. Ensure all test classes follow the Arrange, Act, Assert pattern; variable names are coherent/sensible (replace patchDoc with patchDocument, obj with object/targetObject etc.), remove unnecessary serialization and formatting of error messages
6. ExpandoObjectAdapter and PocoAdapter do not have unit tests
This PR adds a new adapter called DynamicObjectAdapter with unit tests and integration tests in a folder called IntegrationTests.
The tests are organized in a confusing structure and not as we usually organize them. There are a lot of redundant integration tests and some adapters lack unit tests.
1. This test suite can be used to ensure we are spec compliant. It can either be used to generate test code or parsed and tested.ExpandoObjectAdapter
andPocoAdapter
do not have unit testsThis PR adds a new adapter called
DynamicObjectAdapter
with unit tests and integration tests in a folder calledIntegrationTests
.cc @rynowak
The text was updated successfully, but these errors were encountered: