Organize HttpStore backend tests #30
Comments
|
Are the HTTP backend tests now fine? |
|
Should be fine now. |
|
The test case is still called |
…sary) #30 HttpTest now checks for each test, if the target store supports graph creation/deletion and triple querying/creation/deletion. If not, the test will be marked as skipped. The according check-method called getRights is very basic and you could end up with empty graphs, just created to test something. Unless, there is no better way how to check all the stuff, the method will not be part of the constructor.
|
From now on, all HTTP related tests will be skipped if the adapter is not able to create/drop graphs or update or query triples. The test for that is still a little bit basic and stupid, but it works. Because you did not have configured your Virtuoso properly to act as a read/write endpoint, all HTTP tests should skip for you @white-gecko. What remains here:
|
|
Could we maybe add some instructions for the correct configuration of the HTTP endpoint? |
Can you please tell me if the following (fresh new) guide is enough? http://safting.github.io/doc/phpframework/backends/httpstore/ |
|
I documented that behavior here. |
Make out of
HttpAbstractTestandHttpUnitTestoneHttpTestwhich extends theStoreAbstractTest. If some of the tests inHttpUnitTestare needed, migrate them toStoreAbstractTest.The text was updated successfully, but these errors were encountered: