nacx commented on this pull request.
> + assertNotNull(account);
+ assertEquals("devlab1-online-vendor-devuser1", account.userName());
+ assertEquals("Donal Lunny", account.fullName());
+ assertEquals("Donal", account.firstName());
+ assertEquals("Lunny", account.lastName());
+ assertEquals("[email protected]",
account.emailAddress());
+ assertThat(account.roles().contains(Account.RoleType.create("storage")));
+ assertThat(account.roles().contains(Account.RoleType.create("primary
administrator")));
+ assertEquals("1", account.phone().countryCode());
+ assertEquals("1234567", account.phone().number());
+ assertEquals("6ac1e746-b1ea-4da5-a24e-caf1a978789d",
account.organization().id());
+ assertEquals("Eng Customer of DevLab1-homed online sign-up Vendor",
account.organization().name());
+ assertEquals("DevLab1Geo1", account.organization().homeGeoName());
+ assertEquals("apidevlab1.opsourcecloud.net",
account.organization().homeGeoApiHost());
+ assertEquals("DEVLAB1GEO1", account.organization().homeGeoId());
+ assertEquals("NORMAL", account.state());
We have 2 kinds ot tests in jclouds: mock and live tests.
Mock tests verify that we generate the requests we are expected to generate.
One could think about them as "jclouds generates exactly what the API docs say".
Live tests are integration tests that perform real requests to the target cloud
(and may cost money!). The idea is that anyone with an account should be able
to run them to have the real status of the APIs, configure them in the CI to
keep track of the changes on the provider API, etc.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/375#discussion_r107876525
