W3C Linked Data Platform (PAGING) Test Suite: Test Cases Coverage Report

See also W3C Linked Data Platform WG

Specification Requirements Page

Test Suite Revision: ${buildNumber}

Updated: Nov 3, 2014

Summary of Test Methods

Totals

Coverage

Not Implemented

31 Total Tests

0 Approved
31 Pending
0 Extension
0 No longer valid
0 Needs to be clarified with WG

0 Ready for Approval

0 / 31 of Total Tests Automated
0 / 31 of Tests Possible to Automate

26 Requirements Covered

15 MUST
4 SHOULD
7 MAY

0 Requirements Automated

0 / 15 MUST
0 / 4 SHOULD
0 / 7 MAY

0 Tests Indirectly Covered

31 of the Unimplemented Tests

31 of the Tests Yet to be Coded
0 of the Total are Client-Based Tests
0 of the Total must be Tested Manually

From the Total,

0 of the Total are Client-Based Tests
26 Requirements not Implemented

15 MUST
4 SHOULD
7 MAY

Description of the Chart Information

Test Status

Approved - the working group has approved this test case
Pending approval (default) - no official recommendation from the working group supporting the specification being tested by this test suite
Extension - valuable test case but not part of the approved set
Deprecated - no longer recommended by the working group
Clarification - requires further clarification from the working group

Test Implementation

Automated - implementation complete
Not Implemented (default) - possible to implement, just not done
Client Only - test is only client-side, this test suite doesn't test it
Manual - server test but not automated

Test Cases Ready for Approval

No test cases awaiting approval.

Test Cases Yet to be Implemented

Test Cases Covered Indirectly

No Indirect Test Cases.

Implemented Test Classes

org.w3.ldp.paging.testsuite.tests.PagingTest
Test Case Status

Test Case Implementation

Total Tests	Coverage	Status	Implementation
31	MUST: 17 SHOULD: 6 MAY: 8	Pending: 31	Not Implemented: 31

Tests that Must be Tested Manually

No tests of this type found.

Client-Based Test Cases

No tests of this type found.

Test Class: org.w3.ldp.paging.testsuite.tests.PagingTest

testClientAdvertise
Used by Class: PagingTest
Description: LDP Paging clients MUST advertise their ability to support LDP Paging on all retrieval requests that normally result in a response containing a representation.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpp-client-advertise
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testPagingTraversal
Used by Class: PagingTest
Description: LDP Paging clients MUST be capable of at least one of forward traversal and/or backward traversal.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpp-client-traversal
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSequenceChange
Used by Class: PagingTest
Description: LDP Paging clients MUST NOT assume that any in-sequence page resource's paging links will remain unchanged when the in-sequence page resource is retrieved more than once. Such an assumption would conflict with a server's ability to add pages to a sequence as the paged resource changes, for example.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-sequences-change
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testPagingAccess
Used by Class: PagingTest
Description: LDP Paging clients MUST NOT assume that any in-sequence page resource's paging links will always be accessible.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#dfn-ldp-paging-client
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testResourcePresentation
Used by Class: PagingTest
Description: LDP Paging clients SHOULD NOT present paged resources as coherent or complete, or make assumptions to that effect.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpp-client-paging-incomplete
Groups: [SHOULD, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testLargePage
Used by Class: PagingTest
Description: LDP Paging servers SHOULD allow clients to retrieve large LDP-RSs in pages.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-page-large
Groups: [SHOULD, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testResourcePaging
Used by Class: PagingTest
Description: LDP Paging servers MAY treat any resource (LDP-RS or not) as a paged resource.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#dfn-ldp-paging-server
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSplitPaging
Used by Class: PagingTest
Description: LDP Paging servers MAY vary their treatment of any resource (LDP-RS or not) as a paged resource over time. In other words, given two attempts to retrieve the same resource at different points in time, the server can choose to return a representation of the first page at one time and of the entire resource at a different time. Clients distinguish between these cases based on the status code and response headers.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-split-any-time
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testPreferredPaging
Used by Class: PagingTest
Description: LDP Paging servers SHOULD respect all of a client's LDP-Paging-defined hints, for example the largest page size the client is interested in processing, to influence the amount of data returned in representations.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpp-prefer
Groups: [SHOULD, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testPreferUnrecognized
Used by Class: PagingTest
Description: LDP Paging servers MAY ignore a page size of zero, or unrecognized units, and process the request as if no maximum desired size was specified; in the latter case the server can select whatever page size it deems appropriate, or choose not to page the resource at all.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpp-prefer-unrecognized
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testPagingGet
Used by Class: PagingTest
Description: LDP Paging servers SHOULD respond with HTTP status code 2NN Contents of Related to successful GET requests with any paged resource as the Request-URI when the request indicates the client's support for that status code [2NN], although any appropriate code such as 303 See Other MAY be used.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-status-code
Groups: [SHOULD, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testShowUnchanged
Used by Class: PagingTest
Description: LDP Paging servers MUST ensure that all state present in the paged resource throughout a client's entire traversal operation is represented in at least one in-sequence page resource. In other words, whatever subset of the paged resource that is not added, updated, or removed during the client's traversal of its pages has to be present in one of the pages.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-guarantee-show-unchanged
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testDetectChange
Used by Class: PagingTest
Description: LDP Paging servers MUST enable a client to detect any change to the paged resource that occurs while the client is retrieving pages by including a HTTP Link header on all successful HTTP GET responses.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-notify-changes
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testPagingHeaders
Used by Class: PagingTest
Description: LDP Paging servers SHOULD include the same header on all 4xx status code responses. The link's context URI identifies the in-sequence page resource being retrieved, target URI identifies the paged resource, link relation type is canonical [REL-CANONICAL], and link extension parameters include the parameter name etag and a corresponding parameter value identical to the ETag [RFC7232] of the paged resource.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-notify-changes
Groups: [SHOULD, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testInSequencePaging
Used by Class: PagingTest
Description: LDP Paging servers MAY add or remove in-sequence page resources to a paged resource's sequence over time, but SHOULD only add pages to the end of a sequence.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-sequences-change
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testPageAddEnd
Used by Class: PagingTest
Description: LDP Paging servers SHOULD only add pages to the end of a sequence.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-sequences-change
Groups: [SHOULD, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testAllowFirstLink
Used by Class: PagingTest
Description: LDP Paging servers MAY provide a first page link when responding to requests with any in-sequence page resource as the Request-URI.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-first-allowed-onpages
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testAllowLastLink
Used by Class: PagingTest
Description: LDP Paging servers MAY provide a last page link in responses to GET requests with any in-sequence page resource as the Request-URI.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-last-allowed-onpages
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSequenced
Used by Class: PagingTest
Description: LDP Paging servers MUST provide a next page link in responses to GET requests with any in-sequence page resource other than the final page as the Request-URI. This is the mechanism by which clients can discover the URL of the next page.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#dfn-in-sequence-page-resource
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testRestrictFinalLink
Used by Class: PagingTest
Description: LDP Paging servers MUST NOT provide a next page link in responses to GET requests with the final in-sequence page resource as the Request-URI. This is the mechanism by which clients can discover the end of the page sequence as currently known by the server.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-lastnext-prohibited
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testGetPreviousLink
Used by Class: PagingTest
Description: LDP Paging servers MAY provide a previous page link in responses to GET requests with any in-sequence page resource other than the first page as the Request-URI. This is one mechanism by which clients can discover the URL of the previous page.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-prev-allowed
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testRestrictFirstLink
Used by Class: PagingTest
Description: LDP Paging servers MUST NOT provide a previous page link in responses to GET requests with the first in-sequence page resource as the Request-URI. This is one mechanism by which clients can discover the beginning of the page sequence as currently known by the server.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-firstprev-prohibited
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testGetPageReq
Used by Class: PagingTest
Description: LDP Paging servers MUST provide an HTTP Link header whose target URI is http://www.w3.org/ns/ldp#Page, and whose link relation type is type [RFC5988] in responses to GET requests with any in-sequence page resource as the Request-URI. This is one mechanism by which clients know that the resource is one of a sequence of pages.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-page-type-reqd
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testGetOnlyPagingClients
Used by Class: PagingTest
Description: LDP Paging servers MUST NOT initiate paging unless the client has indicated it understands paging. The only standard means defined by LDP paging for a client to signal a server that the client understands paging is via the client preference defined for this purpose; other implementation-specific means could also be used.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-only-paging-clients
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testMembershipSequence
Used by Class: PagingTest
Description: LDP Paging servers MUST ensure that the membership triple and containment triple for each member are part of the same in-sequence page resource, whenever both triples are present in the page sequence for a paged LDPC.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpc-onsamepage
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSortMembers
Used by Class: PagingTest
Description: LDP Paging servers MAY communicate the order it uses to allocate LDPC members to in-sequence page resources as part of the pages' representations; LDP Paging does not specify ordering for pages of LDPRs in other cases.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpc-sortcriteriaobj
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSortTriples
Used by Class: PagingTest
Description: If the server communicates this (ordering), it MUST specify the order using a triple whose subject is the page URI, whose predicate is ldp:containerSortCriteria, and whose object is a rdf:List of ldp:containerSortCriterion resources. The resulting order MUST be as defined by SPARQL SELECT’s ORDER BY clause [sparql11-query]. Sorting criteria MUST be the same for all pages of a representation; if the criteria were allowed to vary, the ordering among members of a container across pages would be undefined.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpc-sortcriteriaobj
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSortCriteria
Used by Class: PagingTest
Description: LDPC page representations ordered using ldp:containerSortCriteria MUST contain, in every ldp:containerSortCriterion list entry, a triple whose subject is the sort criterion identifier, whose predicate is ldp:containerSortPredicate and whose object is the predicate whose value is used to order members between pages (the page-ordering values).
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpc-sortliteraltype
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSortOrder
Used by Class: PagingTest
Description: LDPC page representations ordered using ldp:containerSortCriteria MUST contain, in every ldp:containerSortCriterion list entry, a triple whose subject is the sort criterion identifier, whose predicate is ldp:containerSortOrder and whose object describes the order used. LDP defines two values, ldp:Ascending and ldp:Descending, for use as the object of this triple. Other values can be used, but LDP assigns no meaning to them and interoperability will be limited.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpc-sortorder
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testSortCollation
Used by Class: PagingTest
Description: LDPC page representations ordered using ldp:containerSortCriteria MAY contain, in any ldp:containerSortCriterion list entry, a triple whose subject is the sort criterion identifier, whose predicate is ldp:containerSortCollation and whose object identifies the collation used.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpc-sortcollation
Groups: [MAY, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class

testRestrictCollation
Used by Class: PagingTest
Description: The ldp:containerSortCollation triple MUST be omitted for comparisons involving page-ordering values for which [sparql11-query] does not use collations.
Specification Section: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpc-sortcollation
Groups: [MUST, PAGING]
Status: WG_PENDING
Test Case Implementation: NOT_IMPLEMENTED
Enabled: true

Back to Main Test Class