<% String version = (String)request.getAttribute("d1_version"); String revision = (String)request.getAttribute("d1_revision"); String buildTime = (String)request.getAttribute("d1_buildTime"); String sourceBranch = (String)request.getAttribute("d1_sourceBranch"); %>
DataONE Member Node Web Service Tests:
Test Version: <%=version%>
Source Branch: <%=sourceBranch%>
Test Revision: <%=revision%>
Build Time: <%=buildTime%>
This service was designed to offer member node developers an independent way to test their Member Node API implementations prior to the more focused and thorough testing done in partnership with DataONE team members in order to register the member node into the DataONE network. Accordingly, the scope of tests is limited to those that can be run without interaction with other member or coordinating nodes, mostly looking to check the correctness of responses for all of the given API call.
Tests are organized by API Tier level, and further organized to run slower tests last within each tier. For each API method, one or more test is run to cover common expected situations, even checking for proper exceptions as appropriate. Foreach Tier, a summary result is given (pass / fail). Each test case also attempts to provide a descriptive exception message, but not every circumstance can be anticipated, so the stack trace is provided for further inspection.
URL of DataONE Member Node Web Service*:
Tier-2 Node Test Object series suffix override** (optional):
Tier(s) to test:
* not including version path segment. (e.g. "http://my.server.org/mn" rather than "http://my.server.org/mn/v1" )
** Tier 2 Member Nodes need to have content owned by specific test subjects pre-loaded in order to pass Tier 2 tests. The series designator is the number or letter added as a suffix to the end of the testObject base name, put there to allow the set of test objects to evolve over time, or to supplant defective testObjects. For example, if you created a 'TierTesting:testObject:Public_Read.1', you need to set the value in the input field to "1" so the tester looks for that object and its cohort. Tier 3 and higher nodes do not need to specify a suffix, as the WebTester will create the test objects it needs for Tier 2 tests.