This provides a workaround for the connection issue.

Need to mock out Gapic and compare constructors

…odejs-datastore into use-http-fallback

The harness mocks out the constructor and calls reach the constructor as well as the get function. So now we can see what values get passed into the constructor and get function.

Add a working test that makes sure the rest parameter gets passed down to the gapic layer.

Proper describe blocks make it easier for the code to be arranged so that with and without rest tests can be incorporated into the code.

Remove the datastore mock. It is not necessary.

Make a programmatic link to the data type so that the intent is clearer.

Parameterized tests will allow us to delete half the tests. A new type is created for the test parameters.

Explain the purpose of the class. This will make it useful for testing.

This type is only used once so inline it.

Changes to system tests are not necessary. Remove them.

assert resolves to falsy in tests. See if this solves the issue.

Add console logs and assert checks back in.

This should allow the unit tests to pass in the continuous integration environment.

The title of the describe block should match the file. Remove console logs too.

This parameter more specifically describes the change.

This system test should show how the rest parameter is being used.

This allows the test to pass with a simple assertion check.

Fallback type is more specific . Use it instead.

…odejs-datastore into use-http-fallback