Dear Sergio, I've completed the code of LdpServiceSPARQLImpl.exist() for RDF resource. The unit test has been made as well. Please check my last 2 commits: https://github.com/confidencesun/marmotta/commits/MARMOTTA-444
However, the unit test seems to be ugly. You can see in LdpServiceSPARQLImplTest.testResourceExist() that I directly new the object of LdpServiceSPARQLImpl. Is there other more elegant way to test LdpServiceSPARQLImpl? Also, I find that LdpServiceSPARQLImpl uses LdpBinaryStoreService, ConfigurationService and ldpContext. How can I make the unit test by injecting them into LdpServiceSPARQLImpl? Best regards, Qihong Lin On Tue, May 20, 2014 at 4:47 PM, Sergio Fernández <wik...@apache.org> wrote: > Hi Qihong, > > > On 20/05/14 10:30, Qihong Lin wrote: >> >> I've already set up the development environment. I'm ready to begin >> coding in that fork. > > > Great. > > >> The test suite and the test cases were removed from the code >> repository on 5th May. Could you please tell me why? Any problems with >> the tests? Can I reuse the removed test cases in my fork to ensure the >> expected behaviors of my code? > > > The work on the test suite has been moved to github in collaboration with > other member of the LDP WG: > > https://github.com/w3c/ldp-testsuite > > I've closed MARMOTTA-438 accordingly. > > Anyway, it still needs to be stabilized until it reports proper results. In > the meantime you can use our custom unit tests, that's more than enough for > the earlier phases. > > > Cheers, > > -- > Sergio Fernández > Senior Researcher > Knowledge and Media Technologies > Salzburg Research Forschungsgesellschaft mbH > Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria > T: +43 662 2288 318 | M: +43 660 2747 925 > sergio.fernan...@salzburgresearch.at > http://www.salzburgresearch.at
