Skip to content
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

Online Translator Tests are currently not working #1356

Closed
zuphilip opened this issue Jul 6, 2017 · 2 comments
Closed

Online Translator Tests are currently not working #1356

zuphilip opened this issue Jul 6, 2017 · 2 comments

Comments

@zuphilip
Copy link
Contributor

zuphilip commented Jul 6, 2017

The online translator tests are currently not working. As far as I can say this started after @dstillman worked on the translation-server and switched the tests from 4.0 to 5.0.

What are the further plans for the online translator tests? When will they work again?

@dstillman
Copy link
Member

dstillman commented Jul 6, 2017

Sorry, should be running again now (using current translation-server HEAD, not the 4.0 version in Docker Hub). Various things (like import translators) are still broken in the 5.0 version.

Also it looks like a lot of tests are broken due to data format changes in 5.0, most notably with tags. I'm not totally sure what the situation is there. It looks like tests generally expect just an array of strings, but the 5.0 code is producing a { tag: "foo" } object. That might make sense if it was to allow translators like Zotero RDF to create manual tags and the rest to create automatic (type: 1) tags, but it's not actually producing type: 1 tags (and it would be kind of tedious anyway, since manual tags from translators are the rare exception), so I'll look into this.

@dstillman
Copy link
Member

Tests are up again, on a new domain, and in a more stable fashion based on translation-server v2: https://translator-tests.zotero.org

As a reminder, translation-server doesn't run JavaScript, even for the initial page load, unlike the Connector, which uses XHR for subsequent requests but starts with the initial JS-rendered page, so various sites (like, say, zotero.org) won't work. We could consider fixing that, but we can discuss that elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants