Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Lyo/LyoTestSuite"

< Lyo
m
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
= Lyo OSLC Test Suite =
+
= Lyo OSLC Test Suite =
  
== Goals ==
+
== Goals ==
The goal of the Lyo OSLC Test Suite is to provide a suite of tests which will test OSLC domain provider implementations against the specification.  An initial suite is now available in the project Git repository.  The suite is under development and does not provide full coverage of the implementations it tests at this time.  The goals of the OSLC Test Suite are to:
+
* provide conformance tests for each of the OSLC domains
+
** priority is to cover MUST items first followed by SHOULD and then MAY items
+
** provide reporting to show provider implementations how conforming they are.
+
* provide a tool to find bugs in OSLC providers and improve their quality
+
  
== Areas for Improvement ==
+
The goal of the Lyo OSLC Test Suite is to provide a suite of tests which will test OSLC domain provider implementations against the specification. A JUnit-based test suite is now available in the project Git repository. The suite is under development and does not provide full coverage of the implementations it tests at this time. The goals of the OSLC Test Suite are to:
* Increased coverage for currently supported specifications
+
* Coverage for OSLC specifications not currently tested
+
* Integrated reporting
+
* Improved query tests
+
* Improved OAuth tests
+
  
== Building and running the OSLC Test Suites ==
+
*provide assessment tests for each of the OSLC domains
 +
**priority is to cover MUST items first followed by SHOULD and then MAY items
 +
**provide reporting to show provider implementations an assessment report of coverage and successful execution.
 +
*provide a tool to find bugs in OSLC providers and improve their quality
  
See [[BuildTestSuite | Building and running the OSLC Test Suites]]
+
== Areas for Improvement  ==
See [[BuildTestSuite| Building and running the OSLC Test Suites]]
+
 
 +
*Increased coverage for currently supported specifications
 +
*Coverage for OSLC specifications not currently tested
 +
*Integrated reporting
 +
*Improved query tests
 +
*Improved OAuth tests
 +
 
 +
== Building and running the OSLC Test Suites and Reports  ==
 +
 
 +
* [http://git.eclipse.org/c/lyo/org.eclipse.lyo.testsuite.git/tree/org.eclipse.lyo.testsuite.server/compliance/rtc/documentation/HowToRunOSLCProviderTestsAndGenerateComplianceReport.doc Detailed documentation] for the OSLC Test Suite and Reports in MS Word format.
 +
  * Overview of the test suites
 +
  * How to run the tests
 +
  * How to create reports
 +
* [[Lyo/BuildTestSuite| For Developers: Building and running the OSLC test suite]]

Revision as of 14:11, 29 August 2012

Lyo OSLC Test Suite

Goals

The goal of the Lyo OSLC Test Suite is to provide a suite of tests which will test OSLC domain provider implementations against the specification. A JUnit-based test suite is now available in the project Git repository. The suite is under development and does not provide full coverage of the implementations it tests at this time. The goals of the OSLC Test Suite are to:

  • provide assessment tests for each of the OSLC domains
    • priority is to cover MUST items first followed by SHOULD and then MAY items
    • provide reporting to show provider implementations an assessment report of coverage and successful execution.
  • provide a tool to find bugs in OSLC providers and improve their quality

Areas for Improvement

  • Increased coverage for currently supported specifications
  • Coverage for OSLC specifications not currently tested
  • Integrated reporting
  • Improved query tests
  • Improved OAuth tests

Building and running the OSLC Test Suites and Reports

  * Overview of the test suites
  * How to run the tests
  * How to create reports

Back to the top