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

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 suite

By using the @Report annotation in the test classes

By adding custom attributes to the test methods

By using listeners and implementing report customization logic

Additional information cannot be included in TestNG HTML reports

@BeforeEach

@Setup

@BeforeTest

@BeforeMethod

To generate test data dynamically during test execution

To provide a source of test data for one or more test methods

To define the order of test method execution

TestNG does not support using Data Provider methods

testName

name

testId

id

A mechanism for passing test data to test methods

A way to define dependencies between test methods

A feature for running tests in parallel

TestNG does not support Data Providers

Reports generated in the HTML format for test execution results

Reports containing source code documentation

Reports for tracking project progress and milestones

Reports used for code coverage analysis

By using the @InitPage annotation

By calling the initElements() method from the PageFactory class

By extending the PageObject class

By defining the Page Object configuration in testng.xml

Assert

Verify

Assertion

HardAssert

Yes, by setting the thread-count attribute in the testng.xml file

No, TestNG automatically determines the number of threads based on available resources

Yes, by using the @ThreadCount annotation in the test class

No, TestNG does not provide options for controlling the number of threads

It runs after every test method in a test class

It runs after the execution of any test method in a test class

It runs after the entire test suite

It runs after every test method in a test suite

By extending the PageFactory class

By using the @PageObject annotation

By implementing the ITestNGPage interface

By creating a regular Java class with element locators and methods

To define common setup and teardown methods for multiple test classes

To define test data for parameterized testing

To configure the test suite settings

TestNG does not support creating a base class

To pass test data to test methods

To define test dependencies

To control the execution order of test methods

TestNG does not support using parameters

NoSuchElementFoundException

ElementNotFoundException

PageObjectException

NoSuchElementException

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

Yes, all BeforeMethod annotations will be executed before each test method

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

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

Use the tag inside the tag

Use the attribute in the tag

It defines the test methods in a test class

It specifies the test data for parameterized tests

It groups multiple test classes into a test suite

It configures the test execution settings for a specific test class

By using the @DataProvider annotation with the test method

By specifying the Data Provider name in the testng.xml file

By using the @Test(dataProvider) annotation with the test method

TestNG does not support linking Data Providers to test methods