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

Re-introduce changes from #1814 #1818

Merged
merged 2 commits into from Feb 1, 2019

Conversation

Projects
None yet
4 participants
@adam3smith
Copy link
Collaborator

adam3smith commented Feb 1, 2019

But this time without breaking stuff...

adam3smith added some commits Feb 1, 2019

Re-introduce changes from #1814
But this time without breaking stuff...
@adam3smith

This comment has been minimized.

Copy link
Collaborator

adam3smith commented Feb 1, 2019

@retorquere could you give this a quick look to make sure I have this right -- I'm just taking your old change & testing for extraFields, but really don't want to mess up twice. It works fine in my tests.

@retorquere

This comment has been minimized.

Copy link
Contributor

retorquere commented Feb 1, 2019

Yeah sorry about that! I've just woken up here, I'll look at those and run some tests of my own, and report back in a bit.

@retorquere

This comment has been minimized.

Copy link
Contributor

retorquere commented Feb 1, 2019

(not that it's any kind of excuse for my error, but why didn't the test suite pick this up?)

@retorquere

This comment has been minimized.

Copy link
Contributor

retorquere commented Feb 1, 2019

I see now, travis only does a lint check. This looks good to me.

@adam3smith

This comment has been minimized.

Copy link
Collaborator

adam3smith commented Feb 1, 2019

Yeah, more advanced CI for translators would be nice, especially since most translators already have built in unit tests (wouldn't have helped here because export translators don't). @zuphilip and @dstillman talked about this briefly when they implemented the current CI but I forgot where that was left. Obviously the overhead to run the tests is pretty significant, so this isn't a trivial problem.

@adam3smith adam3smith merged commit 4a58261 into zotero:master Feb 1, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@adam3smith adam3smith deleted the adam3smith:bibtex-extra branch Feb 1, 2019

@retorquere

This comment has been minimized.

Copy link
Contributor

retorquere commented Feb 1, 2019

Already working on both. Current tests run in a second or two.

@retorquere

This comment has been minimized.

Copy link
Contributor

retorquere commented Feb 1, 2019

(and I've already found a few errors in existing translators)

@zuphilip

This comment has been minimized.

Copy link
Collaborator

zuphilip commented Feb 1, 2019

There is a ticket for supporting export translators in Scaffold zotero/scaffold#103 and I would appreciate also automatic tests for export translators.

I guess that now with the new translation-server it is more easily possible to include to run also automatically the test cases for each pull request or commit. As most PR are changing only a single translator, it is enough to test these test cases and that shouldn't take that long.

@dstillman

This comment has been minimized.

Copy link
Member

dstillman commented Feb 1, 2019

Already working on both. Current tests run in a second or two.

Not sure what you're referring to here, but we have a ticket for CI-based testing of translator commits. This would be separate from the existing daily translator tests, though it would use the same Node-based testing functionality. (Web translators can easily fail when run that way because JS isn't run, but import/export tests should never fail.)

If you're working on this, it might be worth posting to that ticket to make sure you're not doing unnecessary work.

@retorquere

This comment has been minimized.

Copy link
Contributor

retorquere commented Feb 1, 2019

Done. I started working on it because I saw an easy path to do it, I had some time, and I'm really, really bummed (and sorry) that I submitted a PR to the translators that broke things.

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