- SEE ALSO
- COPYRIGHT AND LICENCE
- DISCLAIMER OF WARRANTIES
Test::FITesque::RDF - Formulate Test::FITesque fixture tables in RDF
my $suite = Test::FITesque::RDF->new(source => $file)->suite; $suite->run_tests;
t/integration-basic.t for a full test script example.
This module enables the use of Resource Description Framework to describe fixture tables. It will take the filename of an RDF file and return a Test::FITesque::Suite object that can be used to run tests.
The RDF serves to identify the implementation of certain fixtures, and can also supply parameters that can be used by the tests, e.g. input parameters or expectations. See Test::FITesque for more on how the fixtures are implemented.
This module implements the following attributes and methods:
Required attribute to the constructor. Takes a Path::Tiny object pointing to the RDF file containing the fixture tables. The value will be converted into an appropriate object, so a string can also be supplied.
Will return a Test::FITesque::Suite object, based on the RDF data supplied to the constructor.
Will return an arrayref containing tests in the structure used by Test::FITesque::Test. Most users will rather call the
suitemethod than to call this method directly.
A IRI to use in parsing the RDF fixture tables to resolve any relative URIs.
The following must exist in the test description (see below for an example and prefix expansions):
The object(s) of this predicate lists the test fixtures that will run for this test suite. May take an RDF List. Links to the test descriptions, which follow below.
The object of this predicate points to information on how the actual test will be run. That is formulated in a separate resource which requires two predicates,
deps:test-requirementpredicate, whose object contains the class name of the implementation of the tests; and
nfo:definesFunctionwhose object is a string which matches the actual function name within that class.
The object of this predicate provides a literal description of the test.
The object of this predicate links to the parameters, which may have many different shapes. See below for examples.
This module seeks to parameterize the tests, and does so using mostly the
test:params predicate above. This is passed on as a hashref to the test scripts.
There are two main ways currently implemented, one creates key-value pairs, and uses predicates and objects for that respectively, in vocabularies chosen by the test writer. The other main way is create lists of HTTP requests and responses.
Additionally, a special parameter
-special is passed on for internal framework use. The leading dash is not allowed as the start character of a local name, and therefore chosen to avoid conflicts with other parameters.
The literal given in
test:purpose above is passed on as with the
description key in this hashref.
The below example starts with prefix declarations. Since this is a pre-release, some of the prefixes are preliminary examples. Then, the tests in the fixture table are listed explicitly. Only tests mentioned using the
test:fixtures predicate will be used. Tests may be an RDF List, in which case, the tests will run in the specified sequence, if not, no sequence may be assumed.
Then, two test fixtures are declared. The actual implementation is referenced through
test:test_script for both functions.
test:params predicate is used to link the parameters that will be sent as a hashref into the function. The <test:purpose> predicate is required to exist outside of the parameters, but will be included as a parameter as well, named
description in the
There are two mechanisms for passing parameters to the test scripts, one is simply to pass arbitrary key-value pairs, the other is to pass lists of HTTP request-response objects. Both mechanisms may be used.
The key of the hashref passed as arguments will be the local part of the predicate used in the description (i.e. the part after the colon in e.g.
my:all). It is up to the test writer to mint the URIs of the parameters, and the
param_base is used to set indicate the namespace, so that the local part can be resolved, if wanted. The resolution itself happens in URI::NamespaceMap.
@prefix test: <http://ontologi.es/doap-tests#> . @prefix deps: <http://ontologi.es/doap-deps#>. @prefix dc: <http://purl.org/dc/terms/> . @prefix my: <http://example.org/my-parameters#> . @prefix nfo: <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#> . @prefix : <http://example.org/test#> . :test_list a test:FixtureTable ; test:fixtures :test1, :test2 . :test1 a test:AutomatedTest ; test:param_base <http://example.org/my-parameters#> ; test:purpose "Echo a string"@en ; test:test_script <http://example.org/simple#string_found> ; test:params [ my:all "counter-clockwise dahut" ] . :test2 a test:AutomatedTest ; test:param_base <http://example.org/my-parameters#> ; test:purpose "Multiply two numbers"@en ; test:test_script <http://example.org/multi#multiplication> ; test:params [ my:factor1 6 ; my:factor2 7 ; my:product 42 ] . <http://example.org/simple#string_found> a nfo:SoftwareItem ; nfo:definesFunction "string_found" ; deps:test-requirement "Internal::Fixture::Simple"^^deps:CpanId . <http://example.org/multi#multiplication> a nfo:SoftwareItem ; nfo:definesFunction "multiplication" ; deps:test-requirement "Internal::Fixture::Multi"^^deps:CpanId .
To allow testing HTTP-based interfaces, this module also allows the construction of two ordered lists, one with HTTP requests, the other with HTTP responses. With those, the framework will construct HTTP::Request and HTTP::Response objects respectively. In tests scripts, the request objects will typically be passed to the LWP::UserAgent as input, and then the response from the remote server will be compared with the expected HTTP::Responses made by the test fixture. These will then be passed as arrayrefs below the
-special key with the keys
This gets more complex, please see the test data file
t/data/http-list.ttl file for example.
You may maintain client state in a test script (i.e. for one
test:AutomatedTest, as it is simply one script, so the result of one request may be used to influence the next. Server state can be relied on between different tests by using an
rdf:List of test fixtures if it writes something into the server, there is nothing in the framework that changes that.
To use data from one response to influence subsequent requests, the framework supports datatyping literals with the
dqm:regex datatype, for example:
:check_acl_location_res a http:ResponseMessage ; httph:link '<(.*?)>;\\s+rel="acl"'^^dqm:regex ; http:status 200 .
This makes it possible to use a Perl regular expression, which can be executed in a test script if desired. If present, it will supply another arrayref to the
-special key with the key
regex-fields containing hashrefs with the header field that had a correspondiing object datatyped regex as key and simply
1 as value.
Separate the implementation-specific details (such as
deps:test-requirement) from the actual fixture tables.
Please report any bugs to https://github.com/kjetilk/p5-test-fitesque-rdf/issues.
Kjetil Kjernsmo <email@example.com>.
This software is Copyright (c) 2019 by Inrupt Inc.
This is free software, licensed under:
The MIT (X11) License
THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.