The testUtils.js file is not intended to be modified by the user, yet it is currently part of the prototype directory that gets copied over to the new project, just like transform.js and connection.js. This is unnecessary.
It should be moved to be a part of the main sgt-utils project, and exported as a property so it can be accessed from the sgt project. This way, if the file changes, it will automatically take effect without the developer having to manually update it.
Acceptance criteria:
[] testUtils can be accessed by requiring sgt-utils
[] update prototype and examples
[] update existing sgts - conn pool, heimdall, trust, hbase, keystone, message queue
The testUtils.js file is not intended to be modified by the user, yet it is currently part of the prototype directory that gets copied over to the new project, just like transform.js and connection.js. This is unnecessary.
It should be moved to be a part of the main sgt-utils project, and exported as a property so it can be accessed from the sgt project. This way, if the file changes, it will automatically take effect without the developer having to manually update it.
Acceptance criteria:
[] testUtils can be accessed by requiring sgt-utils
[] update prototype and examples
[] update existing sgts - conn pool, heimdall, trust, hbase, keystone, message queue