Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #2 Ensuring features are parsed before formatters are initialised #652

Closed
wants to merge 1 commit into from
Closed

Conversation

tmullender
Copy link
Contributor

Following the discussion in #651 it was suggested that reports should not be created until we know if there are syntax errors.

The formatters that use a URLOutputStream with a file protocol will all create their report files when the factory creates the formatter which at the moment is done when RuntimeOptions are created

I have added a test to demonstrate this and attempted to fix it.
See https://github.com/tmullender/cucumber-jvm/issues/2 for some explanation of the approach

@@ -156,12 +156,24 @@ private void printUsage() {
public List<CucumberFeature> cucumberFeatures(ResourceLoader resourceLoader) {
return load(resourceLoader, featurePaths, filters, System.out);
}

protected List<Formatter> formatters() {
if (formatters.isEmpty()){
Copy link
Contributor

Choose a reason for hiding this comment

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

Both the TestNG and the Android modules add additional formatters to the formatters list (using the getFormatters method), so in those cases the formatters list will be non-empty, even thought the formatters has not yet been created from the formattersNames list. A boolean field (formattersCreated?) is needed to keep track whether formatters has be created from the formattersNames list.

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
mpkorstanje pushed a commit that referenced this pull request Sep 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants