Running tests: "disabling legacy extension" [Juris-M]

[Frank Bennett]

I'm back to tilling the Juris-M field this week, and I've hit a stump.

After merging changes to bring Juris-M level with 5.0.34.6, I have a problem running the test suite:

1. `cd ./test`

2. `./runtests.sh -b -c browserTest`

All seems well in the terminal:

```

Mozilla Firefox 58.0.1

Running JS build process

> zot...@5.0.0 build /media/storage/src/JM/jurism

> node ./scripts/build.js

Success: [browserify] 0 files processed [108ms]

Success: [copy] 0 files processed (out of total 45 matched) [360ms]

Success: [js] 0 files processed (out of total 641 matched) [423ms]

Success: [sass] 0 files processed [19ms]

Success: [symlink] 0 files processed (out of total 1241 matched) [421ms]

Success: [symlink] 0 files processed (out of total 2 matched) [413ms]

Success: [cleanup] 0 files processed [426ms]

Total build time 448ms

```

But in the JS console that pops up, there is this:

```

Could not read chrome manifest 'file:///usr/lib/firefox/chrome.manifest'.

1517788825387 addons.xpi WARN disabling legacy extension zoter...@zotero.org

1517788825415 addons.xpi WARN disabling legacy extension jur...@juris-m.github.io

1517788825708 addons.xpi WARN disabling legacy extension zoter...@zotero.org

1517788825708 addons.xpi WARN disabling legacy extension jur...@juris-m.github.io

1517788825721 addons.xpi WARN disabling legacy extension zoter...@zotero.org

1517788825722 addons.xpi WARN disabling legacy extension jur...@juris-m.github.io

No chrome package registered for chrome://zotero-unit/content/runtests.html

```

It seems to mean what it says. The terminal cursor blinks, and that's about it.

Any idea what incantation might be needed to persuade Firefox to run the extension?

Frank

[Frank Bennett]

Ah, nevermind. Looks like I just need to adjust the Firefox version.

[Duncan Paterson]

I asked about these in here before, so by adjusting you mean to download FF 54?

[Frank Bennett]

Yep, that did the trick. There is a path variable in runtests.sh, you can replace "firefox" with an explicit path to FF54.

On Feb 5, 2018 6:24 PM, "Duncan Paterson" <dunc...@gmail.com> wrote:

I asked about these in here before, so by adjusting you mean to download FF 54?

--
You received this message because you are subscribed to the Google Groups "zotero-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zotero-dev+unsubscribe@googlegroups.com.
To post to this group, send email to zoter...@googlegroups.com.
Visit this group at https://groups.google.com/group/zotero-dev.
For more options, visit https://groups.google.com/d/optout.

[Duncan Paterson]

well there is a lot of firefox 54 version for macOS, which one should it be, the `Firefox Unbranded.app` is nowhere to be found on mozillas site. Shouldn't this work with the firefox bin in standalone-build/xulrunner ? (it doesn't)

[Frank Bennett]

In config.sh of zotero-standalone-build, Mac is set to use "54.0.1"

[Dan Stillman]

You have to run the tests against an unbranded build of Firefox in order
for the extension to load. (The version in zotero-standalone-build is
what we build the client with, but that's not for running directly.)

Unbranded builds are here:

https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds

But you need a 54.0 version. The listed ones broke at some point but I
think the one here is what I use:

https://wiki.mozilla.org/index.php?title=Add-ons/Extension_Signing&oldid=1173603#Unbranded_Builds

For Linux and Windows you need a Firefox 52 unbranded build to test
something approximating the ESR version we build with (which is why we
test both versions on Travis).