While we are at it, I would like to point out another issue.
I have added another custom element which is almost similar to the nature of my previous custom element (differing in only view). I have added a few test cases also for this new custom element. However, this time, some test cases threw error on xyzElement.textContent (as shown before) saying xyzElement is undefined. This resulted in below error.
Spec ‘HERE_GOES_SPEC_NAME’ has no expectations.
It seems that when all tests are ran together, they are not running in complete isolation, which may result in premature and erroneous cleanup of resources. However, this does not happen with a particular test suite every time, as can be seen below. However, when each test suites are run individually, associated test cases run fine (needless to say that the original issue regarding to i18n still remains).
