Lyo Test Suite latest version

[fabian]

Hello all.

There is a nice testing suite for autogenerated code in here:

eclipse/lyo.testsuite

Is there a new version or release of this very same tool?

I am pursuing to sync the test suite to our generated code which was created 3 weeks ago on latest Lyo Designer 4.0.0 m1.

I already changed below section in pom.xml from 3.0.0-SNAPSHOT to 4.0.0-SNAPSHOT, enabled auto-import and brought new

<artifactId>testsuite-server</artifactId>
<name>OSLC Implementation Assessment Test</name>
<groupId>org.eclipse.lyo.testsuite</groupId>
<version>4.0.0-SNAPSHOT</version>

I need to know if there’s a new release as a whole frame.

Thank you for the help.

Regards

[andrew]

Hello Fabian,

To be honest, we did not enough resources to maintain the old test suite. Further, you are the first this year to ask about it.

If you try to get it running and find problems, I will be happy to help you fix them and merge fixes into the tree. If you could open the PR with the changes you started making, we could take it from there.

Cheers,
Andrew

[fabian]

@andrew

Hello Fabian,

To be honest, we did not enough resources to maintain the old test suite. Further, you are the first this year to ask about it.

If you try to get it running and find problems, I will be happy to help you fix them and merge fixes into the tree. If you could open the PR with the changes you started making, we could take it from there.

Thank you very much Andrew, then, was that the last Lyo Test Suite ever made?

Thank you

[jad]

Hi Fabian

How about you don’t change things in the pom.xml file? Try using the testsuite and please report any problems.

There should be no need for the testsuite and the servers being tested to be in synch, nor based on the same code base.
This would be the real test for OSLC, since the integration should work between independently developed systems.

I have not used the testsuite, but from reading the README.txt, it seems that the testsuite is setup for specific domains and specific tools.

Are you generating code for a specific tool? Is that tool already covered by the testsuite, or is it a whole new tool?
If you are working on a new tool, I’d assume you have to setup a new configuration under “org.eclipse.lyo.testsuite.server/config”.

Maybe that’s all you need to do, really.

It would certainly be valuable to learn how the testsuite can be used against generated servers. So, I’d be happy to help along the way

[jad]

You also mentioned using “Lyo Designer 4.0.0 m1”. Can I ask how you downloaded this particular version? The official released version of Lyo Designer is 2.4.0. And we also have the latest snapshot downloadable as instruncted under https://oslc.github.io/developing-oslc-applications/eclipse_lyo/install-lyo-designer.html.
But not 4.0.0 m1.

[andrew]

I think it was in 2013 for Lyo 2.1

[fabian]

Hi jad

Well, a coworker download it, he saw it in the pom.xml

So, your statement is 4.0 isn’t supported?

What we did is a OSLC model adapter by using Lyo designer, simple one.

Gonna work on org.eclipse.lyo.testsuite.server/config that you mentioned.

Thanks a million! guys

[fabian]

May I run Lyo Test Suite exclusively on Eclipse or is it ok to run it on IntelliJ?

Thanks

[andrew]

@fabian

May I run Lyo Test Suite exclusively on Eclipse or is it ok to run it on IntelliJ?

Totally fine to run with Maven: lyo.testsuite/org.eclipse.lyo.testsuite.server/README.md at master · eclipse/lyo.testsuite · GitHub

@fabian

So, your statement is 4.0 isn’t supported?

No, the statement is that the test suite has not been updated since 2.1. But as Jad said, OSLC key focus is on interop, so you should be able to run 2.1 test suite against your 4.0.0.M1 server (formerly called provider). As Jad also said, beware that the test suite may not be written with a generic OSLC server in mind, but with the specific interest towards RTC and a few other early OSLC implementations.

@fabian

What we did is a OSLC model adapter by using Lyo designer, simple one.

Fantastic!

@fabian

Thanks a million! guys

[fabian]

Hello all

I got a new question, I am using Lyo Test Suite Server in a Mac IOS environment, are there any problems with that?

Also, do I have to add all of the variables in org.eclipse.lyo.testsuite.server/config and the xml for each test suite?

Don’t know what to add in: value=“C:/userscripts/org.eclipse.lyo.testsuite.server/config/jira/setup.properties”

Thank you

[andrew]

@fabian

Lyo Test Suite Server in a Mac IOS environment, are there any problems with that?

Not that I know of.

@fabian

do I have to add all of the variables in org.eclipse.lyo.testsuite.server/config and the xml for each test suite?

I am afraid I have no help for you in this. Here are are some links I found that you might not find easily on Google:

• Lyo/LyoTestSuite - Eclipsepedia
• Lyo/BuildTestSuite - Eclipsepedia
• lyo.testsuite/org.eclipse.lyo.testsuite.server/assessment/documentation/HowToRunOSLCProviderTestsAndGenerateAssessmentReport.doc at master · eclipse/lyo.testsuite · GitHub

I am not sure if @jad migrated these documents anywhere. @jamsden may have more useful info in his notes. I just created a README with these links: lyo.testsuite/README.md at master · eclipse/lyo.testsuite · GitHub If you find valuable information, I would appreciate if you submit PRs towards the README. Also, the repo wiki should be available to you for editing. If you will be interested to update the POMs and the code, I will check the CI config to aid you.

[fabian]

Thank you, I truly appreciate your help.

As soon as I have sorted an authentication issue I will begin updating code and keep you posted.

Thanks again.

[isccarrasco]

Hello @andrew and @jad ,
Nice to greet you again.

I want to leverage this post to ask if there is an specific rule for the UPDATE (PUT method) of a resource

I’m using the Lyo Test Suite to validate some endpoints of an OSLC API, in the Lyo Test Suite there is a test to validate the UPDATE of a resource, using the updateTemplate.xml where the RDF resource does not have the about’s attribute.

My question is: Should the endpoint force the client to send the RDF with the about attribute? or could be accepted without this attribute?

What is the rule for this case?

Thanks in advance!

Regards!

– Mario.

[andrew]

@isccarrasco thanks for checking out the test suite! I personally prefer the PUT method to require the resource to be identical to the one that will be returned on GET, so yes, with the about URI (non-blank subject).

@jamsden @ndjc what does the Core spec say on this?

[ndjc]

The spec does not cover the details of specific RDF representations - effectively it delegates those issues to the specs for those formats. The ‘about’ attribute is specific to XML representations of RDF, so is not directly mentioned by the OSLC specs.

However, the OSLC spec does describe in several places that the normal technique for updating a resource is as Andrew describes - do a GET, save the ETag, modify the property values you want to modify or remove the ones you want to delete, but preserve everything else, then do a PUT with an If-Match header.

So one could conclude that modifying the response to remove the about attribute would be in some strange way a request to remove the URI for the resource being updated! Typically that makes no sense, so I imagine most servers would ignore that, but some might possible fail the update request.

[jad]

@isccarrasco!
Hope you got answer to your question.

I’m insterested to know if the test suite is still working as expected. We have not maintained it actively, so it would be great to hear about the status of it.

[andrew]

@fabian @jad @isccarrasco have you tried/succeeded running the test suite since? I just posted my recent attempt in Improving Lyo Test Suite. For now, I only ran it agains RIO OSLC CM server, which did not use Lyo even:

Tests run: 97, Failures: 3, Errors: 14, Skipped: 6

I am interested to see how RefImpl CM will stack up to this.