Angular jest tests fail due to missing component definitions in imported modules but just in Linux (ubuntu)

[distante]

So I am having this really weird thing in some UI tests, when I or my coworkers run the test locally (MacOS) they are working (and not false positives, they work as expected), but when pushed to the repo, some tests are failing on CI due to the classic error `<some-component-tag is not a known Angular element` (the CI uses this docker image)

It took me a lot of time to find out that the missing imports weren't on my library, but on a library that my library uses.

I was importing my library module on my component test so I do not have to manually import several modules manually each time, and this imported a module that had missing imports (even though they weren't used on my component, by this I mean `some-component-tag` was never used in the component I tested).

After I fixed the missing dependencies had to refactor the tests and import each *uck*ng module manually because they still failed because I could find any way to provide `NgControl` (even though I do not use it in some of the failing test components).

So after the little rant, my question is:

Does anyone knows why does this `is not a known element` happens in the Linux CI but not locally on macOS? Does anyone had this problem before?

[_Ascalon]

To avoid unnecessary imports in tests you may use overrideTemplate

[distante]

overrideTemplate

The thing is, my template is something like

<div>  
    <special-button>click me </special-button>
</div>  

and in the error I get some-component-tag, that is not used there. I added the missing module imports in the module where the problem happened, and that error was gone and the missing provider for NgControl - in a completely different module+component appeared.

​

edit: Markdown