Mihai,
Even without the font mapping test wouldn't we get a runtime error in the application (Rainbow) when the font mapping is accessed? If that's true I think the tests are useful because at least we see an error during build vs runtime.
Jim
--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/CAK69zbnuX9u5gd19fDR7q%2B6FxCTjxSsx4K96mJQiF7rfRZVfyQ%40mail.gmail.com.
Seems like disabling (@Ignore) the test is the best way forward
- not worth the hassle as you say.
Hi Mihai,
Thank you for digging into this!
My initial intention was to make a test suite which would cover
the main cases of new UI usage. And actually, I was wondering why
there were no tests for the Core UI module at all... Could you
please let me know what makes it different from other places in
the code base and what are the "unwritten rules"?
I do not have macOS to try out the mentioned -XstartOnFirstThread option.
Does it help to pass the tests or we have look for another
solution?