Giter Site home page Giter Site logo

Comments (3)

GoogleCodeExporter avatar GoogleCodeExporter commented on September 2, 2024
The author told me (via email) that is Ok. I asked for OReilly permissions but 
still no response. Anyway, reading their policies [1] I believe there's no 
problem at all. 

I will submit the first set of tests soon. 

[1] http://www.oreillynet.com/pub/a/oreilly/ask_tim/2001/codepolicy.html

Original comment by [email protected] on 21 Feb 2014 at 3:59

  • Changed state: Started

from cumulusrdf.

GoogleCodeExporter avatar GoogleCodeExporter commented on September 2, 2024
Hi Andrea,

I think we should do the SPARQL testing in a much more structured fashion. 
Maybe we should reuse the SPARQL test cases/data from W3C [1]. This way, we are 
sure that we have all SPARQL 1.1 features reflected/tested in our tests.

In general, we should revisit the overall tests and see that we can improve the 
test coverage. I think some the test classes (especially in the core module) 
should be revised.

What do you think?

Kind regards
Andreas

[1] http://www.w3.org/2009/sparql/docs/tests/

Original comment by andreas.josef.wagner on 29 Jun 2014 at 1:32

from cumulusrdf.

GoogleCodeExporter avatar GoogleCodeExporter commented on September 2, 2024
Yes, nice idea.
The data provided in the book is good because it is already packed in 
different files (the exNN.* you see in the test/resources). There are a 
lot of other files in the source code associated with the book and I'm 
doing that gradually.

But (I think) we can do both, using also code and tests from W3C. The 
current test data is under a folder learningSPARQL and the test is 
called LearningSPARQLTest. We could have a similar structure for W3C.

In general, that's the reason why I left open this issue: it is a 
cross-cutting issue, it can be completed, improved and integrated with 
other things, relase by release.

Yes, I agree, also here we could have something like a cross-cutting 
issue because I think a good coverage is a long term goal. The 
dictionary implementation for example, should have a good coverage but 
tests took a (moreless) good 60% of the overall effort. So thinking in 
those terms for all current tests I think is not a trivial task.

Best,
Andrea

Original comment by [email protected] on 29 Jun 2014 at 5:42

from cumulusrdf.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.