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

See also W3C Linked Data Platform WG

Specification Requirements Page

Summary of Test Methods

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

For details of test cases, see source in GitHub

• IndirectContainer-ContainerHasInsertedContentRelation

Back to Top

Test Cases Yet to be Implemented

• IndirectContainer-ConformsIcLdpContainer
• IndirectContainer-PostResource

Back to Top

Test Cases Covered Indirectly

• RdfSource-ConformsRdfSourceLdpResource
• BasicContainer-ConformsBcLdpContainer
• CommonContainer-ConformsContainerRdfResource
• DirectContainer-ConformsDcLdpContainer

Implemented Test Classes

Back to Top

Tests that Must be Tested Manually

• testReUseVocabularies
• testUseStandardVocabularies
• testRestrictClientInference
• testIsHttp11Manual

Client-Based Test Cases

No tests of this type found.

Back to Top

Test Class: org.w3.ldp.testsuite.test.RdfSourceTest

• testRelativeUriResolutionPut

  Used by Class:
  Description: LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPutReplacesResource

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: If a HTTP PUT is accepted on an existing resource, LDP servers MUST replace the entire persistent state of the identified resource with the entity representation in the body of the request.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-put-replaceall
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPutSimpleUpdate

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD allow clients to update resources without requiring detailed knowledge of server-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-put-simpleupdate
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testGetResource

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST provide an RDF representation for LDP-RSs. The HTTP Request-URI of the LDP-RS is typically the subject of most triples in the response.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-gen-rdf
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testContainsRdfType

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP-RSs representations SHOULD have at least one rdf:type set explicitly. This makes the representations much more useful to client applications that don’t support inferencing.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-gen-atleast1rdftype
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testTypeRdfSource

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: The representation of a LDP-RS MAY have an rdf:type of ldp:RDFSource for Linked Data Platform RDF Source.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-rdftype
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testReUseVocabularies

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP-RSs SHOULD reuse existing vocabularies instead of creating their own duplicate vocabulary terms. In addition to this general rule, some specific cases are covered by other conformance rules.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-gen-reusevocab
  Groups: [SHOULD, MANUAL]
  Status: WG_APPROVED
  Test Case Implementation: MANUAL
  Enabled: true

  How to Run testReUseVocabularies

  • Given a URL for a RDF Source, perform a GET using an RDF content type
  • Inspect the content to ensure standard terms are used. For example, if things like ex:label or ex:title are used, instead of DCTERMS or RDFS, then the test should fail.

Back to Main Test Class

• testUseStandardVocabularies

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP-RSs predicates SHOULD use standard vocabularies such as Dublin Core [DC-TERMS], RDF [rdf11-concepts] and RDF Schema [rdf-schema], whenever possible.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-gen-reusevocabsuchas
  Groups: [SHOULD, MANUAL]
  Status: WG_APPROVED
  Test Case Implementation: MANUAL
  Enabled: true

  How to Run testUseStandardVocabularies

  • Given a URL for a RDF Source, perform a GET using an RDF content type
  • Inspect the content to ensure standard terms are used. For example, if things like ex:label or ex:title are used, instead of DCTERMS or RDFS, then the test should fail.

Back to Main Test Class

• testRestrictClientInference

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST NOT require LDP clients to implement inferencing in order to recognize the subset of content defined by LDP. Other specifications built on top of LDP may require clients to implement inferencing [rdf11-concepts]. The practical implication is that all content defined by LDP must be explicitly represented, unless noted otherwise within this document.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-gen-noinferencing
  Groups: [MUST, MANUAL]
  Status: WG_APPROVED
  Test Case Implementation: MANUAL
  Enabled: true

  How to Run testRestrictClientInference

  • Perform a GET on a URL for the reource requesting an RDF content type
  • Inspect the results (both headers and content) for missing terms. Additionally could run an inferencing tool and compare results, seeing if needed informationshould have been explicitly listed by the server.

Back to Main Test Class

• testGetResourceAcceptTurtle

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers must respond with a Turtle representation of the requested LDP-RS when the request includes an Accept header specifying text/turtle, unless HTTP content negotiation requires a different outcome [turtle].
  Specification Section: http://www.w3.org/TR/ldp#ldprs-get-turtle
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testGetResourceAsTurtleNoAccept

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers should respond with a text/turtle representation of the requested LDP-RS whenever the Accept request header is absent [turtle].
  Specification Section: http://www.w3.org/TR/ldp#ldprs-get-conneg
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testJsonLdRepresentation

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers must respond with a application/ld+json representation of the requested LDP-RS when the request includes an Accept header, unless content negotiation or Turtle support requires a different outcome [JSON-LD].
  Specification Section: http://www.w3.org/TR/ldp#ldprs-get-jsonld
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPublishConstraintsReadOnlyProp

  Used by Class:
  Description: LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testPublishConstraintsUnknownProp covers the rest.

Back to Main Test Class

• testPublishConstraintsUnknownProp

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST publish any constraints on LDP clients’ ability to create or update LDPRs, by adding a Link header with rel='http://www.w3.org/ns/ldp#constrainedBy' [RFC5988] to all responses to requests which fail due to violation of those constraints.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-pubclireqs
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testPublishConstraintsReadOnlyProp covers the rest.

Back to Main Test Class

• testPutReadOnlyProperties4xxStatus

  Used by Class:
  Description: If an otherwise valid HTTP PUT request is received that attempts to change properties the server does not allow clients to modify, LDP servers MUST respond with a 4xx range status code (typically 409 Conflict)
  Specification Section: http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. test4xxErrorHasResponseBody covers the rest.

Back to Main Test Class

• test4xxErrorHasResponseBody

  Used by Class:
  Description: LDP servers SHOULD provide a corresponding response body containing information about which properties could not be persisted. The format of the 4xx response body is not constrained by LDP.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-put-servermanagedprops
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testPutReadOnlyProperties4xxStatus covers the rest.

Back to Main Test Class

• testPutPropertiesNotPersisted

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: If an otherwise valid HTTP PUT request is received that contains properties the server chooses not to persist, e.g. unknown content, LDP servers MUST respond with an appropriate 4xx range status code [HTTP11].
  Specification Section: http://www.w3.org/TR/ldp#ldprs-put-failed
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testResponsePropertiesNotPersisted covers the rest.

Back to Main Test Class

• testResponsePropertiesNotPersisted

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD provide a corresponding response body containing information about which properties could not be persisted. The format of the 4xx response body is not constrained by LDP. LDP servers expose these application-specific constraints as described in section 4.2.1 General.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-put-failed
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testPutPropertiesNotPersisted covers the rest.

Back to Main Test Class

• testConformsRdfSourceLdpResource

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: Each LDP RDF Source MUST also be a conforming LDP Resource as defined in section 4.2 Resource, along with the restrictions in this section.
  Specification Section: http://www.w3.org/TR/ldp#ldprs-are-ldpr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: INDIRECT
  Enabled: true

  This test is covered Indirectly by other test cases.

  Test Cases that cover this test:

  • CommonResource-GetResource
  • CommonResource-IsHttp11Manual
  • CommonResource-ETagHeadersGet
  • CommonResource-ETagHeadersHead
  • CommonResource-LdpLinkHeader
  • CommonResource-GetResponseHeaders
  • CommonResource-ConditionFailedStatusCode
  • CommonResource-PreconditionRequiredStatusCode
  • CommonResource-PutBadETag
  • CommonResource-Head
  • CommonResource-AcceptPatchHeader
  • CommonResource-Options
  • CommonResource-OptionsAllowHeader

Back to Main Test Class

Back to Top

Test Class: org.w3.ldp.testsuite.test.BasicContainerTest

• testConformsBcLdpContainer

  Used by Class: BasicContainerTest
  Description: Each LDP Basic Container MUST also be a conforming LDP Container in section 5.2 Container along with the following restrictions in this section.
  Specification Section: http://www.w3.org/TR/ldp#ldpbc-are-ldpcs
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: INDIRECT
  Enabled: true

  This test is covered Indirectly by other test cases.

  Test Cases that cover this test:

  • CommonContainer-RelativeUriResolutionPost
  • CommonContainer-PostResponseStatusAndLocation
  • CommonContainer-PostContainer
  • CommonContainer-RequestedInteractionModelCreateNotAllowed
  • CommonContainer-RequestedInteractionModelHeaders
  • CommonContainer-AcceptTurtle
  • CommonContainer-NullRelativeUriPost
  • CommonContainer-AcceptPostResponseHeader
  • CommonContainer-DeleteRemovesContainmentTriple
  • CommonContainer-PostJsonLd
  • CommonContainer-ConformsContainerRdfResource

Back to Main Test Class

• testContainerSupportsHttpLinkHeader

  Used by Class: BasicContainerTest, IndirectContainerTest
  Description: LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-linktypehdr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. DirectContainerTest.testHttpLinkHeader and IndirectContainerTest.testContainerSupportsHttpLinkHeader covers the rest.

Back to Main Test Class

Back to Top

Test Class: org.w3.ldp.testsuite.test.CommonContainerTest

• testPutToCreate

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MAY choose to allow the creation of new resources using HTTP PUT.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-put-create
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testRelativeUriResolutionPost

  Used by Class:
  Description: LDP servers MUST assign the default base-URI for [RFC3987] relative-URI resolution to be the HTTP Request-URI when the resource already exists, and to the URI of the created resource when the request results in the creation of a new resource.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-defbaseuri
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement.

Back to Main Test Class

• testNoRdfBagSeqOrList

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDPC representations SHOULD NOT use RDF container types rdf:Bag, rdf:Seq or rdf:List.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-nordfcontainertypes
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPreferContainmentTriples

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING].
  Specification Section: http://www.w3.org/TR/ldp#ldpc-prefer
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostResponseStatusAndLocation

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: If the resource was created successfully, LDP servers MUST respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-created201
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostContainer

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: When a successful HTTP POST request to an LDPC results in the creation of an LDPR, a containment triple MUST be added to the state of LDPC.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-createdmbr-contains
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testRequestedInteractionModelCreateNotAllowed

  Used by Class:
  Description: LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-createrdf
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testRequestedInteractionModelHeaders covers the rest.

Back to Main Test Class

• testRequestedInteractionModelHeaders

  Used by Class:
  Description: LDP servers that successfully create a resource from a RDF representation in the request entity body MUST honor the client's requested interaction model(s). The created resource can be thought of as an RDF named graph [rdf11-concepts]. If any model cannot be honored, the server MUST fail the request.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-createrdf
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testRequestedInteractionModelCreateNotAllowed covers the rest.

Back to Main Test Class

• testAcceptTurtle

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST accept a request entity body with a request header of Content-Type with value of text/turtle [turtle].
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-turtle
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testContentTypeHeader

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD use the Content-Type request header to determine the representation format when the request has an entity body.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-contenttype
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testNullRelativeUriPost

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: In RDF representations, LDP servers MUST interpret the null relative URI for the subject of triples in the LDPR representation in the request entity body as referring to the entity in the request body. Commonly, that entity is the model for the “to be created” LDPR, so triples whose subject is the null relative URI will usually result in triples in the created resource whose subject is the created resource.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-rdfnullrel
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostNoSlug

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD assign the URI for the resource to be created using server application specific rules in the absence of a client hint.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-serverassignuri
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testCreateWithoutConstraints

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD allow clients to create new resources without requiring detailed knowledge of application-specific constraints. This is a consequence of the requirement to enable simple creation and modification of LDPRs. LDP servers expose these application-specific constraints as described in section 4.2.1 General.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-mincontraints
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testRestrictUriReUseSlug

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers that allow member creation via POST SHOULD NOT re-use URIs.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testRestrictUriReUseNoSlug covers the rest.

Back to Main Test Class

• testRestrictUriReUseNoSlug

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers that allow member creation via POST SHOULD NOT re-use URIs.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-dontreuseuris
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testRestrictUriReUseSlug covers the rest.

Back to Main Test Class

• testAcceptPostResponseHeader

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers that support POST MUST include an Accept-Post response header on HTTP OPTIONS responses, listing post document media type(s) supported by the server.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-acceptposthdr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testRejectPutModifyingContainmentTriples

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD NOT allow HTTP PUT to update an LDPC’s containment triples; if the server receives such a request, it SHOULD respond with a 409 (Conflict) status code.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-put-mbrprops
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testRestrictPutReUseUri

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers that allow LDPR creation via PUT SHOULD NOT re-use URIs. For RDF representations (LDP-RSs),the created resource can be thought of as an RDF named graph [rdf11-concepts].
  Specification Section: http://www.w3.org/TR/ldp#ldpc-put-create
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testDeleteRemovesContainmentTriple

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: When an LDPR identified by the object of a containment triple is deleted, the LDPC server MUST also remove the LDPR from the containing LDPC by removing the corresponding containment triple.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-del-contremovesconttriple
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPatchMethod

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers are RECOMMENDED to support HTTP PATCH as the preferred method for updating an LDPC's empty-container triples.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-patch-req
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testRdfTypeLdpContainer

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: The representation of a LDPC MAY have an rdf:type of ldp:Container for Linked Data Platform Container. Non-normative note: LDPCs might have additional types, like any LDP-RS.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-typecontainer
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testServerHonorsSlug

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MAY allow clients to suggest the URI for a resource created through POST, using the HTTP Slug header as defined in [RFC5023]. LDP adds no new requirements to this usage, so its presence functions as a client hint to the server providing a desired string to be incorporated into the server's final choice of resource URI.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-slug
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostJsonLd

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers SHOULD accept a request entity body with a request header of Content-Type with value of application/ld+json [JSON-LD].
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-jsonld
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testConformsContainerRdfResource

  Used by Class: BasicContainerTest, CommonContainerTest, IndirectContainerTest, DirectContainerTest
  Description: Each Linked Data Platform Container MUST also be a conforming Linked Data Platform RDF Source.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-isldpr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: INDIRECT
  Enabled: true

  This test is covered Indirectly by other test cases.

  Test Cases that cover this test:

  • RdfSource-RelativeUriResolutionPut
  • RdfSource-PutReplacesResource
  • RdfSource-PutSimpleUpdate
  • RdfSource-GetResource
  • RdfSource-RestrictClientInference
  • RdfSource-GetResourceAcceptTurtle
  • RdfSource-JsonLdRepresentation
  • RdfSource-PublishConstraintsReadOnlyProp
  • RdfSource-PublishConstraintsUnknownProp
  • RdfSource-PutReadOnlyProperties4xxStatus
  • RdfSource-PutPropertiesNotPersisted
  • RdfSource-ConformsRdfSourceLdpResource

Back to Main Test Class

Back to Top

Test Class: org.w3.ldp.testsuite.test.CommonResourceTest

• testGetResource

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST support the HTTP GET Method for LDPRs
  Specification Section: http://www.w3.org/TR/ldp#ldpr-get-must
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testIsHttp11Manual

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST at least be HTTP/1.1 conformant servers [HTTP11].
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-http
  Groups: [MUST, MANUAL]
  Status: WG_APPROVED
  Test Case Implementation: MANUAL
  Enabled: true

  NOTE: Covers only part of the specification requirement. testIsHttp11Server covers the rest.

Back to Main Test Class

• testETagHeadersGet

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-etags
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testETagHeadersHead covers the rest.

Back to Main Test Class

• testETagHeadersHead

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP server responses MUST use entity tags (either weak or strong ones) as response ETag header values.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-etags
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testETagHeadersGet covers the rest.

Back to Main Test Class

• testLdpLinkHeader

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers exposing LDPRs MUST advertise their LDP support by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#Resource, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPR's HTTP Request-URI.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-linktypehdr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testGetResponseHeaders

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST support the HTTP response headers defined in section 4.2.8 HTTP OPTIONS.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-get-options
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPutRequiresIfMatch

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP clients SHOULD use the HTTP If-Match header and HTTP ETags to ensure it isn’t modifying a resource that has changed since the client last retrieved its representation. LDP servers SHOULD require the HTTP If-Match header and HTTP ETags to detect collisions.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-put-precond
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutBadETag covers the rest.

Back to Main Test Class

• testConditionFailedStatusCode

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].
  Specification Section: http://www.w3.org/TR/ldp#ldpr-put-precond
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testPutBadETag, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Back to Main Test Class

• testPreconditionRequiredStatusCode

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].
  Specification Section: http://www.w3.org/TR/ldp#ldpr-put-precond
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPutBadETagand testPutRequiresIfMatch covers the rest.

Back to Main Test Class

• testPutBadETag

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST respond with status code 412 (Condition Failed) if ETags fail to match when there are no other errors with the request [HTTP11]. LDP servers that require conditional requests MUST respond with status code 428 (Precondition Required) when the absence of a precondition is the only reason for rejecting the request [RFC6585].
  Specification Section: http://www.w3.org/TR/ldp#ldpr-put-precond
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testConditionFailedStatusCode, testPreconditionRequiredStatusCode and testPutRequiresIfMatch covers the rest.

Back to Main Test Class

• testHead

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST support the HTTP HEAD method.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-head-must
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testAcceptPatchHeader

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers that support PATCH MUST include an Accept-Patch HTTP response header [RFC5789] on HTTP OPTIONS requests, listing patch document media type(s) supported by the server.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-patch-acceptpatch
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testOptions

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST support the HTTP OPTIONS method.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-options-must
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testOptionsAllowHeader

  Used by Class: RdfSourceTest, BasicContainerTest, CommonContainerTest, CommonResourceTest, NonRDFSourceTest, IndirectContainerTest, DirectContainerTest
  Description: LDP servers MUST indicate their support for HTTP Methods by responding to a HTTP OPTIONS request on the LDPR’s URL with the HTTP Method tokens in the HTTP response header Allow.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-options-allow
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

Back to Top

Test Class: org.w3.ldp.testsuite.test.NonRDFSourceTest

• testPostNonRDFSource

  Used by Class: NonRDFSourceTest
  Description: LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-createbins
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testPostResourceAndGetFromContainer covers the rest.

Back to Main Test Class

• testPostResourceAndGetFromContainer

  Used by Class: NonRDFSourceTest
  Description: LDP servers may accept an HTTP POST of non-RDF representations (LDP-NRs) for creation of any kind of resource, for example binary resources.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-createbins
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. testPostNonRDFSource covers the rest.

Back to Main Test Class

• testPostResourceGetBinary

  Used by Class: NonRDFSourceTest
  Description: LDP servers may host a mixture of LDP-RSs and LDP-NRs. For example, it is common for LDP servers to need to host binary or text resources that do not have useful RDF representations.
  Specification Section: http://www.w3.org/TR/ldp#ldpr-gen-binary
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostResourceGetMetadataAndBinary

  Used by Class: NonRDFSourceTest
  Description: Each LDP Non-RDF Source must also be a conforming LDP Resource. LDP Non-RDF Sources may not be able to fully express their state using RDF.
  Specification Section: http://www.w3.org/TR/ldp#ldpnr-are-ldpr
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostResourceAndCheckLink

  Used by Class: NonRDFSourceTest
  Description: LDP servers exposing an LDP Non-RDF Source may advertise this by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#NonRDFSource, and a link relation type of type (that is, rel='type') in responses to requests made to the LDP-NR's HTTP Request-URI.
  Specification Section: http://www.w3.org/TR/ldp#ldpnr-type
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostResourceAndCheckAssociatedResource

  Used by Class: NonRDFSourceTest
  Description: Upon successful creation of an LDP-NR (HTTP status code of 201-Created and URI indicated by Location response header), LDP servers may create an associated LDP-RS to contain data about the newly created LDP-NR. If a LDP server creates this associated LDP-RS it must indicate its location on the HTTP response using the HTTP Link response header with link relation describedby and href to be the URI of the associated LDP-RS resource.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-post-createbinlinkmetahdr
  Groups: [MAY]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testDeleteNonRDFSourceDeletesAssociatedResource

  Used by Class: NonRDFSourceTest
  Description: When a contained LDPR is deleted, and the LDPC server created anassociated LDP-RS (see the LDPC POST section), the LDPC server must alsodelete the associated LDP-RS it created.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-del-contremovescontres
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testOptionsHasSameLinkHeader

  Used by Class: NonRDFSourceTest
  Description: When responding to requests whose request-URI is a LDP-NR with anassociated LDP-RS, a LDPC server must provide the same HTTP Link responseheader as is required in the create response
  Specification Section: http://www.w3.org/TR/ldp#ldpc-options-linkmetahdr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

Back to Top

Test Class: org.w3.ldp.testsuite.test.IndirectContainerTest

• testContainerSupportsHttpLinkHeader

  Used by Class: BasicContainerTest, IndirectContainerTest
  Description: LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-linktypehdr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. DirectContainerTest.testHttpLinkHeader and BasicContainerTest.testContainerSupportsHttpLinkHeader covers the rest.

Back to Main Test Class

• testConformsIcLdpContainer

  Used by Class: IndirectContainerTest
  Description: Each LDP Indirect Container MUST also be a conforming LDP Direct Container in section 5.4 Direct along the following restrictions.
  Specification Section: http://www.w3.org/TR/ldp#ldpic-are-ldpcs
  Groups: [MUST]
  Status: WG_PENDING
  Test Case Implementation: NOT_IMPLEMENTED
  Enabled: false

Back to Main Test Class

• testContainerHasInsertedContentRelation

  Used by Class: IndirectContainerTest
  Description: LDP Indirect Containers MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is ldp:insertedContentRelation, and whose object ICR describes how the member-derived-URI in the container's membership triples is chosen.
  Specification Section: http://www.w3.org/TR/ldp#ldpic-indirectmbr
  Groups: [MUST]
  Status: WG_PENDING
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostResource

  Used by Class: IndirectContainerTest
  Description: LDPCs whose ldp:insertedContentRelation triple has an object other than ldp:MemberSubject and that create new resources MUST add a triple to the container whose subject is the container's URI, whose predicate is ldp:contains, and whose object is the newly created resource's URI (which will be different from the member-derived URI in this case). This ldp:contains triple can be the only link from the container to the newly created resource in certain cases.
  Specification Section: http://www.w3.org/TR/ldp#ldpic-post-indirectmbrrel
  Groups: [MUST]
  Status: WG_PENDING
  Test Case Implementation: NOT_IMPLEMENTED
  Enabled: false

Back to Main Test Class

Back to Top

Test Class: org.w3.ldp.testsuite.test.DirectContainerTest

• testHttpLinkHeader

  Used by Class: DirectContainerTest
  Description: LDP servers exposing LDPCs MUST advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel='type') in all responses to requests made to the LDPC's HTTP Request-URI.
  Specification Section: http://www.w3.org/TR/ldp#ldpc-linktypehdr
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement. IndirectContainerTest.testContainerSupportsHttpLinkHeader and BasicContainerTest.testContainerSupportsHttpLinkHeader covers the rest.

Back to Main Test Class

• testUseMemberPredicate

  Used by Class: DirectContainerTest
  Description: LDP Direct Containers SHOULD use the ldp:member predicate as an LDPC's membership predicate if there is no obvious predicate from an application vocabulary to use.
  Specification Section: http://www.w3.org/TR/ldp#ldpdc-mbrpred
  Groups: [SHOULD, ldpMember]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testMemberResourceTriple

  Used by Class: DirectContainerTest
  Description: Each LDP Direct Container representation MUST contain exactly one triple whose subject is the LDPC URI, whose predicate is the ldp:membershipResource, and whose object is the LDPC's membership-constant-URI. Commonly the LDPC's URI is the membership-constant-URI, but LDP does not require this.
  Specification Section: http://www.w3.org/TR/ldp#ldpdc-containres
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testMemberRelationOrIsMemberOfRelationTripleExists

  Used by Class: DirectContainerTest
  Description: Each LDP Direct Container representation must contain exactly one triple whose subject is the LDPC URI, and whose predicate is either ldp:hasMemberRelation or ldp:isMemberOfRelation. The object of the triple is constrained by other sections, such as ldp:hasMemberRelation or ldp:isMemberOfRelation, based on the membership triple pattern used by the container.
  Specification Section: http://www.w3.org/TR/ldp#ldpdc-containtriples
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testActAsIfInsertedContentRelationTripleExists

  Used by Class: DirectContainerTest
  Description: LDP Direct Containers MUST behave as if they have a (LDPC URI, ldp:insertedContentRelation , ldp:MemberSubject) triple, but LDP imposes no requirement to materialize such a triple in the LDP-DC representation.
  Specification Section: http://www.w3.org/TR/ldp#ldpdc-indirectmbr-basic
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testPostResourceUpdatesTriples

  Used by Class: DirectContainerTest
  Description: When a successful HTTP POST request to an LDPC results in the creation of an LDPR, the LDPC MUST update its membership triples to reflect that addition, and the resulting membership triple MUST be consistent with any LDP-defined predicates it exposes.
  Specification Section: http://www.w3.org/TR/ldp#ldpdc-post-createdmbr-member
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testDeleteResourceUpdatesTriples

  Used by Class: DirectContainerTest
  Description: When an LDPR identified by the object of a membership triple which was originally created by the LDP-DC is deleted, the LDPC server MUST also remove the corresponding membership triple.
  Specification Section: http://www.w3.org/TR/ldp#ldpdc-del-contremovesmbrtriple
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

Back to Main Test Class

• testConformsDcLdpContainer

  Used by Class: DirectContainerTest
  Description: Each LDP Direct Container MUST also be a conforming LDP Container in section 5.2 Container along the following restrictions.
  Specification Section: http://www.w3.org/TR/ldp#ldpdc-are-ldpcs
  Groups: [MUST]
  Status: WG_APPROVED
  Test Case Implementation: INDIRECT
  Enabled: true

  This test is covered Indirectly by other test cases.

  Test Cases that cover this test:

  • CommonContainer-RelativeUriResolutionPost
  • CommonContainer-PostResponseStatusAndLocation
  • CommonContainer-PostContainer
  • CommonContainer-RequestedInteractionModelCreateNotAllowed
  • CommonContainer-RequestedInteractionModelHeaders
  • CommonContainer-AcceptTurtle
  • CommonContainer-NullRelativeUriPost
  • CommonContainer-AcceptPostResponseHeader
  • CommonContainer-DeleteRemovesContainmentTriple
  • CommonContainer-PostJsonLd
  • CommonContainer-ConformsContainerRdfResource

Back to Main Test Class

• testPreferMembershipTriples

  Used by Class: DirectContainerTest
  Description: LDP servers SHOULD respect all of a client's LDP-defined hints, for example which subsets of LDP-defined state the client is interested in processing, to influence the set of triples returned in representations of an LDPC, particularly for large LDPCs. See also [LDP-PAGING].
  Specification Section: http://www.w3.org/TR/ldp#ldpc-prefer
  Groups: [SHOULD]
  Status: WG_APPROVED
  Test Case Implementation: AUTOMATED
  Enabled: true

  NOTE: Covers only part of the specification requirement.

Back to Main Test Class

Back to Top