Task records as returned by the Query API have 'name' parameter
equal to the 'operation_name' parameter of the Model object (and
OperationName value of the get_task request)
This commit documents that difference in the test, and corrects
the get_execute_query Mock to mirror the behaviour.
Preloads :id, and :name if available. Leaves everything else up to lazy-loading, though optionally can call a per-collection function to add more values if available
fence_mode can be 'isolated' (disconnected from EdgeGateway) or
'natRouted' (connected to NatService on EdgeGateway).
The network types differ significantly enough to have a separate
set of tests, to be expanded later.
This has also fixed an issue where undefined attributes in the
request output were not being unmarked as NonLoaded. Test adjusted
accordingly.
In addition, highlighted that we need the ensure_list! hack on
IpRanges->IpRange.
Largely based on the vapp tests, except for explicitly
trying to find a suitable network to test against rather than
just blindly picking the first.
Test lazy loading is working, and that values loaded match
our data from the raw service request.
Lazy loading unfortunately complicates testing as per the
current implementation - determining that the loading has
happened is on a field-by-field basis, which leaves fields
that are undefined in vCloud in a 'NonLoaded' state. Possibly worth
revisiting this logic in a separate commit.
- add tags for `rake test`
- use `tests/.fog` not bespoke environment variables
- vapp_life_cycle_tests made pending; extra requests arise after
71a303415b
