1 Introduction

This document provides an overview of content provided through the Versioning conformance suite. The Versioning conformance suite is modular equal to the Versioning specification itself. The file and folder conventions described in this document are valid for all versioning modules across this conformance suite.

2 Test cases

The conformance suite is divided into two parts. The first part verifies the correct creation (folder: creation) and the second part the correct consumption (folder: consumption) of a versioning report. Creation and consumption test cases are structured by versioning module. One subfolder for each versioning module named equally as the versioning module. In the creation folder underneath each versioning module requirements as defined by the versioning requirement document are listed when applying to the specific versioning module. In the consumption part subfolders of the versioning modules are a list of error codes respectively.

Example for creation of a versioning report:

\trunk\versioningReport\conf\creation\[versioning module]\[requirement]\

Concrete example:

\trunk\versioningReport\conf\creation\versioning-base\caseU1605-mapping-rules\

Example for consumption of a versioning report:

\trunk\versioningReport\conf\consumption\[versioning module]\[error code]\

Concrete example:

\trunk\versioningReport\conf\creation\versioning-base\invalidAssignmentRef\

Subfolders of the creation folder are named by the requirement number – requirement title which is derived from the XBRL Versioning Requirements [XVR].

Inside each requirement / error code subfolder is a [folder-name].xml file. This is the description of the particular test case and contains all required information to run the conformance suite test case. The xml file can be rendered in any web browser in a human readable form. The test case file provides information about the location of the versioning report and the from-DTS and to-DTS. If further information is required in the testing scenario from the application performing the test case the information required can be found within the versioning report or the narrative description within the test file. In bellows example to create a versioning report with a user defined category the test case does state the QName of the category explicitly. It is just mentioned in the narrative <description> element. The testing program has to extract this information from the referenced versioning report in order to run the test in an automated fashion. Below an example from versioning requirement caseU1504-add-change-category:

\trunk\versioningReport\conf\creation\versioning-base\caseU1504-add-change-category\caseU1504-add-change-category-testcase.xml

3 References

XVR

XBRL International Inc.. "XBRL Versioning Requirements"
Sergio Quiróz, and Katrin Schmehl.
(See http://www.xbrl.org/Specification/versioning-requirements/PWD-2009-02-04/versioning-requirements-REQ-PWD-2009-02-04.html)

4 Intellectual property status (non-normative)

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to XBRL International or XBRL organizations, except as required to translate it into languages other than English. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).

This document and the information contained herein is provided on an "AS IS" basis and XBRL INTERNATIONAL DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The attention of users of this document is directed to the possibility that compliance with or adoption of XBRL International specifications may require use of an invention covered by patent rights. XBRL International shall not be responsible for identifying patents for which a license may be required by any XBRL International specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. XBRL International specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. XBRL International takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).

5 Acknowledgements (non-normative)

This document could not have been written without the contributions of many people.