1 Answer
- Newest
- Most votes
- Most comments
0
I understand the problem. for a test class like :
@FixMethodOrder(MethodSorters.NAME_ASCENDING)
public class Class1 {
@Test
public void method1() {....}
@Test
public void method2() {....}
@BeforeClass
public static void setUp() {
driver = new AndroidDriver(new URL(URL), getCapsAndroidEmulAut2());
}
@AfterClass
public static void tearDown() {
driver.quit();
}
}
AWS Device Farm considers Class1 as a suite, each method as a class. According to the results: Farm executes setUp(), then method1(), then tearDown() (this is the first suite) Then Farm executes a new suite : setUp(), then method2(), then tearDown().
While the standard behavior of JUnit is Class1 is a class, il execute setUp(), method1(), method2(), and tearDown().
Any help ?
answered a year ago
Relevant content
- asked 5 years ago
- asked a year ago
- Accepted Answerasked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago