When the authentication token is not available, the tests in the ReleaseNotesBuilderIntegrationTests class fail with a ArgumentNullException: Value cannot be null. (Parameter 'token').
This is different than how other integration tests behave. More specifically: GitHubProviderIntegrationTests and GitLabProviderIntegrationTests check for the presence of the token in their respective "one time setup" and assert that tests are inconclusive if the token is missing.
I suggest that, for the sake of consistency, ReleaseNotesBuilderIntegrationTests should behave exactly like the other integration test classes.
When the authentication token is not available, the tests in the
ReleaseNotesBuilderIntegrationTestsclass fail with a ArgumentNullException:Value cannot be null. (Parameter 'token').This is different than how other integration tests behave. More specifically:
GitHubProviderIntegrationTestsandGitLabProviderIntegrationTestscheck for the presence of the token in their respective "one time setup" and assert that tests are inconclusive if the token is missing.I suggest that, for the sake of consistency, ReleaseNotesBuilderIntegrationTests should behave exactly like the other integration test classes.