I get null pointer exceptions when trying to test ...
# ktor
n
I get null pointer exceptions when trying to test websockets - the documentation is sparse on this; but all modules should be being loaded as set in a
.conf
- has anyone encountered this?
a
n
similar yes - I think it’s somewhat confusing as to what the testApplication is doing; in my case it was getting a 406 which lead to the exception - ofc would be nicer if I could have seen that error hehe; it was because the testApp needed ContentNegotiation installed, with my app the serializers vary by route so there wasn’t a global one set up That said, this route works fine outside of the test app