Task #1032
Story #909: Reimplement cn/resolve using nodelist for testing
upgrade integration tests (in d1_libclient_java) to adequately test resolve
Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_libclient_java
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
6.00 h
Milestone:
Product Version:
*
Story Points:
Sprint:
History
#1 Updated by Rob Nahf about 14 years ago
- Status changed from New to In Progress
- Estimated time set to 6.00
- translation missing: en.field_remaining_hours changed from 4.0 to 2.0
- Category set to d1_libclient_java
- % Done changed from 0 to 50
need to create data to resolve in order to test. Two approaches, rely on existing data (by resolving against members of a listObjects list), or creating data (using back-door mn/create on the cn.) Trying the mn/create approach first.
#2 Updated by Rob Nahf about 14 years ago
- % Done changed from 50 to 100
- Status changed from In Progress to Closed
updated D1ClientCNodeTest.java with new logic to create data on the system to resolve.
The sum difference in the D1Client resolve test of today with the one from old is the addition of an mn.create, the subsequent making public of it, the harmonization of nodeReferences between the test sysMeta, and the deployed nodelist, and addition of replica elements to the sysMeta.
