Skip to content

Conversation

@marcphilipp
Copy link
Member

Resolves #8.

@marcphilipp marcphilipp self-assigned this Jul 19, 2021
@marcphilipp marcphilipp force-pushed the marc/8-config-params branch 2 times, most recently from db60ef9 to 69ba89c Compare July 19, 2021 07:30
README.adoc Outdated
maximum number of threads to use for running data providers in parallel, if enabled via `@DataProvider(parallel = true)` (default: `10`)
+
`testng.parallel` (methods|tests|classes|instances|none)::
TestNG's parallel execution mode for running tests in separate threads (default: `"none"`)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does Test Distribution support all of these - or if none is set, it will only disable TestNG's parallelism (as stated), but keep TDs?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only about the parallelism within a partition which will still be supported (similar to Spock's or Jupiter's parallelims support).

README.adoc Outdated
TestNG's parallel execution mode for running tests in separate threads (default: `"none"`)
+
`testng.preserveOrder` (boolean)::
whether classes and methods should be run in a predictable order (default: `true`)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TD can't keep this promise

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They would still be executed in the order TD passes them to TestNG when this flag is used.

README.adoc Outdated
whether classes and methods should be run in a predictable order (default: `true`)
+
`testng.threadCount` (integer)::
maximum number of threads for running tests in parallel, if enabled via `testng.parallel` (default: `5`)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the relation between this and dataProviderThreadCount?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's unrelated as far as I could tell.

`testng.listeners` (comma-separated list of fully-qualified class names)::
custom listeners that should be registered when executing tests (default: `""`)
+
`testng.outputDirectory` (file path)::
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does it have to be an absolute one?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, not necessarily.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't we define the base for relative paths in that case?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think using the working dir as a base is fine.

README.adoc Outdated
+
`testng.verbose` (integer)::
TestNG's level of verbosity (default: 0)
TestNG's level of verbosity (default: `0`)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we add a link here describing what the level means - or add some description such as:

The verbosity level is between 0 and 10 where 10 is the most detailed. You can specify -1 and this will put TestNG in debug mode (no longer slicing off stack traces and all).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a links to the most relevant sections in the TestNG docs to each config param now.

@marcphilipp marcphilipp force-pushed the marc/8-config-params branch from 69ba89c to e11de25 Compare July 19, 2021 15:12
@marcphilipp marcphilipp merged commit e11de25 into main Jul 19, 2021
@marcphilipp marcphilipp deleted the marc/8-config-params branch July 19, 2021 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for standard TestNG options as configuration parameters

4 participants