Тест по TestNG (en). Часть 3

Yes, all AfterMethod annotations will be executed after each test method

Yes, but only one AfterMethod can be executed per test method

No, TestNG does not allow multiple AfterMethod annotations in a class

No, AfterMethod annotations can only be used once in a test class

@BeforeSuite

@BeforeTest

@BeforeClass

@BeforeMethod

TestNGRunner

PageFactory

WebDriver

WebElement

The dependent method is skipped

The dependent method is still executed

The entire test suite is aborted

The dependency is automatically resolved by TestNG

It signifies that the method should be executed after every test method

It specifies that the method should be executed after a specific test method

It ensures that the method runs after all configuration methods

It signals that the method should be executed before any test methods

By using the @FindBy annotation with a unique locator

By using the @FindByAll annotation with multiple locators

By using the @FindBys annotation with multiple locators

TestNG Page Factory does not support List

onTestSuccess

onTestFailure

onTestSkipped

onTestStart

All the methods annotated with @BeforeTest will be executed, but their order of execution is undefined

Only the first method annotated with @BeforeTest will be executed, and the rest will be ignored

It is not allowed to have multiple methods annotated with @BeforeTest in a test class

The execution behavior is unpredictable and may vary depending on the TestNG version

Lazy initialization

Eager initialization

Conditional initialization

It depends on the specific use case

It is used to mark a method that should be executed before each test method

It is used to mark a method that should be executed before all the test methods in a test class

It is used to mark a method that should be executed after each test method

It is used to mark a method that should be executed after all the test methods in a test class

Yes, but only the first method will be executed

No, only one method can be annotated with @BeforeSuite

Yes, all the annotated methods will be executed in the order of their declaration

Yes, but the execution order is not guaranteed

TestNG automatically resolves cyclic dependencies

Cyclic dependencies are not allowed in TestNG

Use the priority attribute to break cyclic dependencies

Use the dependsOnGroups attribute to break cyclic dependencies

@AfterSuite

@AfterTest

@AfterClass

@AfterMethod

Yes, you can use the “default” attribute in the @Parameters annotation

No, TestNG does not support specifying default values for parameters

Yes, you can define default values in the testng.xml file using the tag

No, TestNG always requires explicit values for parameters

@BeforeTest

@BeforeSuite

@BeforeClass

@BeforeMethod

The order is random and cannot be determined

The order is based on alphabetical sorting of the methods

The order is based on the method declaration order

TestNG does not support multiple BeforeSuite annotations

It is used to mark a method that should be executed before each test method

It is used to mark a method that should be executed before all the test methods in a test class

It is used to mark a method that should be executed before all the test methods in a test suite

It is used to mark a method that should be executed after all the test methods in a test class

Separate the method names with a comma (,)

Use the dependsOn attribute with an array of method names

Define a separate @Test annotation for each dependency

Use the @DependsOnMethods annotation

assertEquals()

assertTrue()

assertEqual()

verifyEquals()