[WIP] run tests with SSR compiler, where possible

[Rich-Harris]

As suggested in #248, runs the DOM compiler tests with the SSR compiler. Doesn't make sense in all cases (e.g. onrender doesn't run, in an SSR context), so we'll probably need some kind of 'skip this test' flag, but it should help our coverage a bit

[PaulBGD]

Is the WIP marking tests as client only and skipping them in the SSR tests? I can go through and do that, if you want.

[Rich-Harris]

@PaulBGD not sure to be honest! I made a start on this but then had to work on some other stuff, so I haven't looked into the various ways the tests might fail. In some cases they might even indicate a bug, so I wasn't ready to just mark them as invalid without digging further — but if you're able to look into them that'd be awesome 👍 😀

[PaulBGD]

@Rich-Harris Just opened #261 that works on skipping tests that shouldn't be ran on SSR.

[PaulBGD]

So then what's left is

• raw-mustaches test should have an equivalent SSR version and we skip the generator one
• two way binding needs to be fixed for the server
• server needs to be able to handle yield in a top-level component
• text-node-top-level gets compiled without the SSR compiler for some reason.. that needs to be fixed. I tried to debug it for 20 minutes and I couldn't figure it out.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@d5648df).

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d5648df...b8790d1. Read the comment docs.

[Rich-Harris]

Added a separate issue for the component two-way binding bug: #275