Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367036 - Verify application/json support in test suite
Summary: Verify application/json support in test suite
Status: CLOSED FIXED
Alias: None
Product: Lyo
Classification: Technology
Component: TestSuite (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Yuhong Yin CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-18 16:34 EST by Michael Fiedler CLA
Modified: 2015-03-09 09:51 EDT (History)
1 user (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 Michael Fiedler CLA 2011-12-18 16:34:56 EST 
Build Identifier: 

The current test suite spreadsheet states the following requirement is untested.   However,  I believe the current JSON tests cover it.   This bugzilla is to investigate current test suite support in this area and determine if we should be claiming this requirement is covered or not.

When CM Consumers request: application/json CM Providers MUST respond with JSON representation as defined in the OSLC Core Representations Guidance. 


Reproducible: Always
Comment 1 Yuhong Yin CLA 2012-01-06 09:48:40 EST 
Started to look into this.
Comment 2 Yuhong Yin CLA 2012-01-06 10:15:34 EST 
There are tests for create and update using JSON, but there is no test to cover basic GET request in JSON format. I will add them.
Comment 3 Yuhong Yin CLA 2012-01-09 16:23:38 EST 
I have added ChangeRequestJsonTests.java and added some helper methods. Should be ready to commit the change soon. 

Tested change against RTC 3.0.1.1 and ClearQuest. Both worked well.
Comment 4 Yuhong Yin CLA 2012-01-10 10:27:19 EST 
I've pushed the change and submitted a pull request.
Comment 6 Samuel Padgett CLA 2015-03-09 09:51:27 EDT 
Bulk update: Closing out Lyo bugs fixed long ago. Feel free to reopen if you feel your bug was closed in error.