> +import org.jclouds.openstack.nova.v2_0.internal.BaseNovaApiLiveTest;
> +import org.testng.annotations.Test;
> +
> +import java.util.Set;
> +
> +import static org.testng.Assert.assertTrue;
> +
> +/**
> + * Tests for link {@code FloatingIPPoolApi}
> + */
> +@Test(groups = "live", testName = "FloatingIPPoolApiLiveTest")
> +public class FloatingIPPoolApiLiveTest extends BaseNovaApiLiveTest {
> +
> + @Test
> + public void testListFloatingIPPools() throws Exception {
> + for (String zoneId : api.getConfiguredRegions()) {
This may simply be following a pattern from other tests, in which case I'm fine
with this, but would it make sense to use the test property
[`regions`](https://github.com/jclouds/jclouds/blob/master/apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/internal/BaseNovaApiLiveTest.java#L55)
here?
That way, users could limit the live test to a specific region if desired.
/cc @zack-shoylev @jdaggett @everett-toews
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/570/files#r18748059