I want to unit test a repository for CMIS 1.0 compatibility.
If I use the latest CMIS Workbench, then the TCK button runs the unit tests for CMIS 1.1 (which fails, since the repository only supports CMIS 1.0).
Is there some way to run the TCK CMIS 1.0 unit tests even with the latest CMIS Workbench?
If not, what version of CMIS Workbench was the last before they switched to the CMIS 1.1 TCK unit tests?
The TCK automatically adapts to the repository. If the repository reports (in the repository info) that it is a CMIS 1.0 repository, only CMIS 1.0 tests will be executed. If the repository reports that it is a CMIS 1.1 repository, then CMIS 1.1 tests will be executed. All CMIS Workbench versions since 0.9.0-beta-1 do that.
If a TCK test fails, it's either a repository issue or the repository reports the wrong CMIS version.
Related
I'm using Selenium with C#, specflow and NUnit 3 to create my automated tests. Now I am looking for reporting tool like Allure. Can anyone guide me, how to configure Allure report please?
Thanks,
Check https://www.nuget.org/packages/Specflow.Allure/
Make sure you're using NUnit 3 version which supports TextFixtureSetUp/TextFixtureTearDown (like 3.2), because SpecFlow uses old NUnit and this attributes became deprecated in newer NUnit versions.
Specflow.Allure currently supports SpecFlow 2.1 and will support 2.2 as soon as my PR will be approved.
I have always thought that DotCMIS supports both CMIS 1.0 and CMIS 1.1 repositories.
But now I am being told otherwise, that DotCMIS (by extension: CmisSync) does not support CMIS 1.0.
How is it actually?
Do recent versions of DotCMIS still support CMIS 1.0 repositories?
DotCMIS only supports CMIS 1.0 repositories. It might work with CMIS 1.1 repositories, but that's not a supported scenario.
Current dotCMIS versions support only CMIS 1.0
If you are interested in using dotCMIS with CMIS 1.1 you should follow the instructions on this link: https://issues.apache.org/jira/browse/CMIS-742
Its just a "partial patch" but better than nothing.
Hope it might help someone...
Which is the compatible Hector version to connect to cassandra? I have apache cassandra 1.2.5
Is it Core 0.8.0-2 / 1.0-1 or
Test 1.0-1 or
HOM 1.1-02/2.0-01/3.0-01
Which one I need to use if it is apache-cassandra 1.2.5
Thanks!
You want the latest core version (to get the very latest clone the git repository and build it using maven, or the much simpler option, use hector's maven repository and add the dependency which can be found below). The test version is unit tests, but building the whole git repository and including the tests along side the core driver shouldn't be a problem.
<dependency>
<groupId>me.prettyprint</groupId>
<artifactId>hector-core</artifactId>
<version>1.0-5</version>
</dependency>
So from the dependency you can see the latest version is 1.0-5. For latest Cassandra pick the latest driver, if that fails get their last known 'production ready' version which in this case would appear to be 1.0-5.
But on a side note, pick a better driver, Hector is known for being difficult to work with and datastax advise use of cql drivers for new Cassandra applications.
Does anybody know if there is any differences between CMIS (http://www.mulesoft.org/muleforge/cmis-cloud-connector) and SharePoint (http://www.mulesoft.com/cloud-connectors/sharepoint) connectors in Mule ESB?
Since CMIS only is supported in SharePoint server 2010 I'm wondering if Mule has a solution for previous versions of SharePoint.
Thanks,
Mohammad
I got the following response from a contact in MuleSoft:
"Regarding SharePoint – you actually use the CMIS connector for that. CMIS is the underlying technology of SharePoint"
what are the performance improvement are done on Groovy1.7 to groovy 2.0-beta release, i working on the 1.7.2 release, need to upgrade to groovy 2.0 beta version
Groovy 2.0 Beta 1 Release Notes
Groovy 2.0 Beta 2 Release Notes