🚨🚨🚨 Test downstream integrations do not break 🚨🚨🚨

[davelab6]

Observed behaviour

It is possible for us to merge in changes to master and release them that will break tools that use fontbakery (gf-dispatcher, fontbakery-dashboard, maybe more) - and it should not be.

Expected behaviour

We need to ensure that all tools that use fontbakery (gf-dispatcher, fontbakery-dashboard, maybe more) are always capable of running the latest pypi release, or even the latest master branch, so prevent any changes from being released or merged in future that break them.

Resources and exact process needed to replicate

We need to enumerate the tools that use fontbakery, and begin writing code tests for their usage.

[felipesanches]

Thanks for reporting that. It does indeed seem to be important to protect against breaking those tools in the future. But was this issue reported after something actually breaking? Or is it only a matter of precaution?

[m4rc1e]

Dispatcher and gftools are currently py2 only.

[madig]

Great, that makes them break perpetually unless you invoke fontbakery through subprocess ;) I suggest 🐍 🐍 🐍

[felipesanches]

@m4rc1e, I suppose that at this point in time these tools were already ported to python 3, right?

[graphicore]

Dashboard/dispatcher is all py3 now. However, there are other ways Font Bakery can trouble the dispatcher, e.g. by breaking assumptions made about the file structure it's running in. Thinking about the "superfamily tests" for example.

[m4rc1e]

gftools, diffbrowsers and font diffenator are all py3 :-)