Each network has a rest client (except TTN, which needs to be created). Currently sessions are managed in the networkProtocols.js file, and passed to each network protocol method. It would be better to manage the session in the rest client because each network has different session requirements/strategies, and passing the session throughout the network protocol code get's really tedious.
When the REST clients are managing the sessions, we can import them into the tests and use the clients to reduce all the HTTP request boilerplate code. We could do that now, but we'd still have to manage sessions in the tests. Before using the clients in the tests, I think they should be enhanced to manage sessions.
Each network has a rest client (except TTN, which needs to be created). Currently sessions are managed in the networkProtocols.js file, and passed to each network protocol method. It would be better to manage the session in the rest client because each network has different session requirements/strategies, and passing the session throughout the network protocol code get's really tedious.
When the REST clients are managing the sessions, we can import them into the tests and use the clients to reduce all the HTTP request boilerplate code. We could do that now, but we'd still have to manage sessions in the tests. Before using the clients in the tests, I think they should be enhanced to manage sessions.