[RTC-208] Add server socket tests

[mickel8]

No description provided.

[codecov]

Codecov Report

Merging #33 (4499386) into main (47e181d) will increase coverage by 8.35%.
The diff coverage is 81.25%.

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   80.76%   89.12%   +8.35%     
==========================================
  Files          31       32       +1     
  Lines         364      377      +13     
==========================================
+ Hits          294      336      +42     
+ Misses         70       41      -29     

Impacted Files	Coverage Δ
lib/jellyfish_web/peer_socket.ex	86.79% <66.66%> (+9.01%)	⬆️
lib/jellyfish_web/server_socket .ex	85.71% <100.00%> (+82.14%)	⬆️
test/support/ws.ex	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

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

[LVala]

Would be possible to also test peer/component crashes?

[mickel8]

Unfortunately, we are not able to get engine endpoint pid at the moment

[LVala]

I would wrap tests about connecting to the server (valid/invalid token, no peer etc.) in one describe (describe "connecting to server"?) and the two last test in describe "sends a message" or something similar.

[mickel8]

TBH, I don't see any benefits from using describe here. We will just introduce more nesting 🤔

[LVala]

I think is creates nice visual distinction between connection tests, receiving information from socket tests etc., but I don't care about it that much.

[LVala]

As we mentioned offline, it's probably possible to move some tests from peer socket unit tests here.

[LVala]

👍, but maybe it would be nice to add a comment somewhere why we don't test peer/component crashes (membrane_rtc_engine limitations).