Ignore:
Timestamp:
2023-08-08T21:24:36+02:00 (20 months ago)
Author:
taylor.smock
Message:

See r18798: Actually use the @Territories annotation

This also fixes some tests that fail with specific options, but were passing due
to run order.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/test/unit/org/openstreetmap/josm/tools/RightAndLefthandTrafficTest.java

    r17275 r18799  
    44import static org.junit.jupiter.api.Assertions.fail;
    55
    6 import org.junit.jupiter.api.extension.RegisterExtension;
    76import org.junit.jupiter.api.Test;
    87import org.openstreetmap.josm.data.coor.LatLon;
    9 import org.openstreetmap.josm.testutils.JOSMTestRules;
     8import org.openstreetmap.josm.testutils.annotations.Projection;
     9import org.openstreetmap.josm.testutils.annotations.Territories;
    1010
    11 import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
    1211import net.trajano.commons.testing.UtilityClassTestUtil;
    1312
     
    1514 * Unit tests of {@link RightAndLefthandTraffic} class.
    1615 */
     16@Projection
     17@Territories
    1718class RightAndLefthandTrafficTest {
    18     /**
    19      * Test rules.
    20      */
    21     @RegisterExtension
    22     @SuppressFBWarnings(value = "URF_UNREAD_PUBLIC_OR_PROTECTED_FIELD")
    23     public JOSMTestRules rules = new JOSMTestRules().projection().territories();
    24 
    2519    /**
    2620     * Tests that {@code RightAndLefthandTraffic} satisfies utility class criteria.
Note: See TracChangeset for help on using the changeset viewer.