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

Once before all the test methods

Once after all the test methods

Before each test method

After each test method

@BeforeTest

@BeforeSuite

@BeforeClass

@BeforeMethod

By using the @DataProvider annotation on a method

By specifying the data in the testng.xml file

By using the @Test(dataProvider) annotation on a test method

TestNG does not provide options for defining a Data Provider

name

value

provider

indices

The dependent method is skipped

The dependent method is still executed

The entire test suite is aborted

The dependency is automatically resolved by TestNG

Yes, by providing multiple method names as arguments to the @Ignore annotation

Yes, by using the @IgnoreAll annotation

No, a separate @Ignore annotation is required for each test method

Ignoring multiple test methods is not possible in TestNG

It runs after every test method in a test class

It runs after the entire test suite

It runs before every test method in a test class

It runs after every test method in a test suite

parallel=”true”

parallel=”enabled”

parallel=”parallel”

parallel=”concurrent”

Dependencies can only be specified within the same test class

Dependencies can be specified across multiple test classes

Dependencies are automatically resolved based on method names

Dependencies can only be specified using XML configuration files

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 BeforeMethod annotations

It returns all elements that match any of the specified locators

It returns the first element that matches any of the specified locators

It returns all elements that match all of the specified locators

It returns the first element that matches all of the specified locators

@FindBy

@InitElements

@PageFactory

@InitPage

A design pattern used to manage test data in TestNG

A built-in feature of TestNG for creating page objects

A framework for generating test reports in TestNG

A technique for parallel test execution in TestNG

initializeElements()

initPageElements()

initElements()

loadPageElements()

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 AfterTest annotations

Yes, but only the first method will be executed

No, only one method can be annotated with @AfterMethod

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

Yes, but the execution order is not guaranteed

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 AfterClass annotations

Categories assigned to test methods

Tags used for version control

Test cases organized into modules

Test data sets for parameterization

Yes, TestNG HTML reports are designed to be viewed in a web browser

No, TestNG HTML reports can only be viewed using specialized tools or plugins

It depends on the configuration and settings of the HTML reports

Viewing TestNG HTML reports is not supported

The test continues executing the remaining assertions

The test is marked as a failure, and the test execution stops

The test is marked as a warning, and the test execution continues

Hard assertions do not fail; they always pass

It initializes the Page Objects with element locators

It verifies the integrity of element locators

It optimizes the performance of element initialization

It caches the values of elements for faster access

name

value

provider

indices

Hard assertions are more reliable than soft assertions

Soft assertions allow the test to continue after a failure, while hard assertions halt the test

Hard assertions are recommended for critical test cases, while soft assertions are recommended for non-critical cases

Soft assertions are built-in TestNG features, while hard assertions require external libraries

Use the tag and specify the methods to be excluded

Set the enabled attribute to false for the test methods to be excluded

Use the tag and list the methods to be excluded

Define a separate XML file for excluded methods and reference it in the main XML file