-
Notifications
You must be signed in to change notification settings - Fork 2
Tests #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests #28
Conversation
pheyvaer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the "Testing" section of the README up to date?
No, I have updated it in commit 1d852c1 |
Did you try every step yourself? |
Just did again, it works for me |
Weird, because when I do the second step with |
Ah, yes, my bad, I have custom npm commands configured so I didn't notice. You would probably get the same for I have updated it in commit 362d13e |
pheyvaer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Log in and execute query on private data" and "Querying resource with "bad" cors header, though a proxy should work" doesn't work for me. I think it's related to the fact that when the app starts immediately the first query is executed. There is a PR #31 to fix this.
|
@AronBuzogany Can you merge |
they still all succeed |
|
Ok. Can you remove all DBpedia data sources from the tests? It's best not to rely on remote resources for testing. |
|
Yes, in that case I will just replace all the queries which don't query locally hosted resources |
They are now all removed except for the ask query as it is not implemented yet #22 All tests still succeed |
|
I see there is |
Correct, I haven't got there yet. It is now however in the README and a script in Should we do something about the number of processes running up? Or is it okay as is? |



This PR fixes #21