Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365201 - Seeking a place to post OSLC compliance baseline reports
Summary: Seeking a place to post OSLC compliance baseline reports
Status: CLOSED WONTFIX
Alias: None
Product: Lyo
Classification: Technology
Component: TestSuite (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-30 09:35 EST by Yuhong Yin CLA
Modified: 2017-11-06 12:32 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuhong Yin CLA 2011-11-30 09:35:58 EST 
Build Identifier: 

We have at least OSLC compliance baseline reports for (1) RIO-CM (2) RTC 3.0.1.1 and (3) JIRA

We are seeking a place to post them and make them available for others to read. 

One idea is to save them in a folder off the compliance toolkit structure.

Reproducible: Always
Comment 1 Steve Speicher CLA 2011-12-19 12:12:25 EST 
What format do they come in?

Could put on Eclipse Wiki or off Lyo homepage or OSLC web site or ???
Comment 2 Yuhong Yin CLA 2012-01-06 09:43:22 EST 
The report is just a html file plus a couple of png/svg files the html refers to. It should be not hard to put them to a wiki somewhere so they are more visible. 

Currently, the baseline compliance reports for JIRA, RTC3.0.1.1 and RIO-CM are stored in a directory called "saved-baseline-reports" off the compliance toolkit in the testsuite project.
Comment 3 Samuel Padgett CLA 2015-03-09 09:25:09 EDT 
Bulk update: The future focus of Lyo test suites will for OSLC 3.0, likely using the same framework as the LDP test suite. We'll evaluate 2.0 test suite improvements based on usage and need.

If you feel like this bug should not have been closed, feel free to reopen and update its status.
Comment 4 Andrii Berezovskyi CLA 2017-11-06 12:32:27 EST 
Closed due to inactivity.