S-RAMP 1.0 spec compliance and TCK (ARTIF-462)

[ARTIF-168] Create a TCK test suite Created: 07/Mar/13  Updated: 03/Nov/14  Resolved: 03/Nov/14

Status: Closed
Project: Artificer
Component/s: Distro
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: Kurt Stam Assignee: Brett Meyer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Adding a Technical Compatibility Kit.

  • add examples from spec docs
  • add tests to validate the implementation adheres to the spec


Comment by Brett Meyer [ 07/Jul/14 ]

Remove the current tck from s-ramp. Create a new tck repo in Overlord (Governance/s-ramp-tck). The tck should have no dependencies on overlord whatsoever. Keep it limited to simple REST, xmlunit, xpath, etc.

Comment by Brett Meyer [ 08/Jul/14 ]

See subclasses of AbstractResourceTest for RESTEasy-based client examples

Comment by Brett Meyer [ 03/Nov/14 ]

The TCK is created in a separate repo (Governance/s-ramp-tck). Will continue to improve it as SRAMP-462 progresses. Closing this. No fix release since it's outside of the actual project.

Generated at Fri Nov 16 03:44:56 EST 2018 using Jira 7.12.1#712002-sha1:609a50578ba6bc73dbf8b05dddd7c04a04b6807c.