Parity between the client and server instances of the library are critical, and there are some 350+ tests for the client codebase, covering the majority of the code. There are handful of server-side tests as well covering the server-only components.
It would be really cool if we could rerun those same client-side tests on the server which would improve code coverage by making sure that everything works as expected even when run within a Node environment. A few tests only apply to the client (such as enabled and visible functionality), but the majority of the tests should run on the server. These should definitely be included into the testing process.
Parity between the client and server instances of the library are critical, and there are some 350+ tests for the client codebase, covering the majority of the code. There are handful of server-side tests as well covering the server-only components.
It would be really cool if we could rerun those same client-side tests on the server which would improve code coverage by making sure that everything works as expected even when run within a Node environment. A few tests only apply to the client (such as
enabledandvisiblefunctionality), but the majority of the tests should run on the server. These should definitely be included into the testing process.