Ruben Taelman

Thanks for checking @mvanbrab! So it looks like server errors occur, but do not seem to be correlated with missing results. For future reference: it would be good to repeat...

@retog I just did a quick web search, and came across this: https://www.npmjs.com/package/@rollup/plugin-node-resolve#browser Have you tried this before?

@afizzycola No one is actively working on this at the moment unfortunately. If this functionality is important for you, there is the option to place a bounty on this via...

We should also have (periodic) Travis builds for the _latest_ comunica-browser builds at https://github.com/rdfjs/comunica-browser/tree/master/versions/latest/packages/actor-init-sparql

We should also test simulated npm deployments and testing the binaries (to avoid issues like #414).

We should also test the Docker files (to avoid things like #469).

Basic integration tests done in #495. Now only testing of Docker files and binaries remaining.

Relevant for rdf-test-suite-ldf: https://netflix.github.io/pollyjs/#/README \cc @ManuDeBuck

As shown in #650, we definitely need more SPARQL-specific integration tests, as the official SPARQL 1.1 test suite does not seem to cover all functionality.

As shown in https://github.com/comunica/comunica/issues/669, we also need some tests for construct (and ask?) queries.