Instead, you should treat Business-Modules as the units you want to test. A module has a clear, explicit API (public methods as well as required interfaces). It means that all the results and side effects can be observed via the API. So in tests you can apply stimulus to the module and assert the results/side effects - that should cover all possible paths (except for time based logic, but there are other methods to cover these cases).
I was thinking of simply rendering sanitized HTML directly on the page, but that would cause a huge amount of issues - overlapping ids, conflicting styles etc. I then realized that we have a perfect tool for this - Shadow DOM. It completely eliminates these issues. All elements are isolated into their own context and don't interfere with rest of the page. It would still be possible to overflow the page, but that's the issue for CSS part.
。体育直播对此有专业解读
Банк России оценил идею о двух вариантах ставки по кредитам14:55
Бритни Спирс арестовали20:54。wps下载对此有专业解读
ВСУ запустили «Фламинго» вглубь России. В Москве заявили, что это британские ракеты с украинскими шильдиками16:45
16‑летняя дочь Юлии Пересильд снялась в откровенном образе20:42。PDF资料是该领域的重要参考