Removing reliance on testserver and dummy vcd instance about go-vcloud-director HOT 7 CLOSED

I think we should retain the ability of using a mock server (which should be the default,) in addition to testing with a real server. That would allow developers to work without need for a constant connection to the real vCD.

from go-vcloud-director.

If we keep it I would like to remove the Mozilla license dependency. It's triggering for some legal teams. Can we find something that's Apache 2.0 licensed?

from go-vcloud-director.

Your point is very valid, but I feel that developers should be testing on a real vcd anyways before merging code. Also the time difference between the real vcd and the mock server shouldn't be a huge issue as a user can specify which test he wants to run if he doesn't want to run all the tests. We can discuss this in our monday meeting. For now I will hold off on pushing code that removes the mock server. If we keep the test server I can update the xml for the org and vdc.

from go-vcloud-director.

I agree with Ankith that it does not seem all that helpful to use a mock server. Mocks will become increasingly hard to maintain as we add more API calls in future.

from go-vcloud-director.

I understand the challenge.
I was thinking of using a mock server like mockingjay-server (MIT license) that can be easily enhanced.

from go-vcloud-director.

We decided to remove any kind of mocking tests in favour of tests with real API calls.

from go-vcloud-director.

Solved with commit 6b69953 and #35

from go-vcloud-director.