Unit tests are difficult when libraries depend on external resources (like a running NSoT server). This should be a motivation for writing simple, one purpose methods but should still be able to test end-to-end that a result is expected.
Maintaining extensive mocks is counter-productive so the real answer should be itests. Unfortunately we lose ability to run them via cloud CI servers but that's OK for now.
Unit tests are difficult when libraries depend on external resources (like a running NSoT server). This should be a motivation for writing simple, one purpose methods but should still be able to test end-to-end that a result is expected.
Maintaining extensive mocks is counter-productive so the real answer should be itests. Unfortunately we lose ability to run them via cloud CI servers but that's OK for now.