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

@BeforeClass

@BeforeMethod

@BeforeSuite

@BeforeTest

It locates and initializes elements on a web page

It defines the URL of the web page being tested

It verifies the presence of an element on a web page

It captures screenshots during test execution

Yes, all AfterSuite annotations will be executed after the entire test suite

Yes, but only one AfterSuite can be executed per test class

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

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

It allows you to specify which methods should be included or excluded from test execution

It configures the TestNG framework for test execution

It defines the test methods in a test class

It groups multiple test classes into a test suite

Use the Gradle TestNG plugin

Import TestNG as a module in the project settings

Gradle does not support TestNG

Add a TestNG dependency in the build.gradle file

It reduces code duplication and improves maintainability

It allows parallel execution of test methods

It provides a way to define test data for parameterized testing

It improves the overall performance of the test suite

The dependent methods will be executed in parallel

The dependent methods will be executed sequentially

TestNG will throw an error and abort execution

The order of execution will be unpredictable

Yes, you can specify different values in the @Parameters annotation for each test method

No, TestNG requires all test methods in a class to have the same parameter values

Yes, but you need to define separate data provider methods for each test method

No, TestNG does not support using different parameter values for different test methods

order

priority

sequence

method-order

Soft assertions provide more detailed failure messages

Soft assertions are faster than hard assertions

Soft assertions are easier to write and understand

There is no advantage; hard assertions are always preferred

@AfterTest

@AfterSuite

@AfterClass

@AfterMethod

Automatically by TestNG after test execution

Manually by executing a separate command or script

By configuring the build tool or test runner

TestNG does not support HTML reports

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

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

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

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

@AfterAll

@Teardown

@AfterSuite

@AfterClass

Once before all the test methods

Once after all the test methods

Before each test method

After each test method

A design pattern for organizing test cases

A framework for parallel test execution

A mechanism for creating Page Objects in Selenium

A reporting tool for generating test reports

Use the tag with a wildcard (*) value

Use the tag inside the tag

Use the attribute in the tag

It is not possible to exclude all methods from a test class in a TestNG XML file

The order is based on alphabetical sorting of the methods

The order is based on the method declaration order

The order is random and cannot be determined

TestNG does not support multiple AfterMethod annotations

Yes, but only the first method will be executed

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

Yes, but the execution order is not guaranteed

No, only one method can be annotated with @BeforeClass