You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Custom output directory not created for HTML report #130
If a custom OutputPath is specified in a custom DefaultHtmlReportConfiguration, when that directory doesn't exist the test still runs and passes but no report is created because the path doesn't exist.
Should the directory be automatically created by BDDfy if it doesn't exist?
For example, the following won't produce report output if the dir "MyReps" doesn't exist:
Yes, I saw you highlight that issue in your Pluralsight video. Thanks for raising the issue here as I agree it seems like unexpected behaviour. The report should be created in whatever location is specified in OutputPath, and it should attempt to create the directory if it does not exist. Not sure what it should do if it could not create the directory for some reason though...?
The directory should be created if it doesn't exist. This is encapsulated in FileWriter and is very easy to fix.
If the directory cannot be created we cannot do anything because the report is being created on appdomain unload which is too late to do anything meaningful. Perhaps we could create it on the default path but that would be confusing too.
Activity
mwhelan commentedon May 2, 2014
Yes, I saw you highlight that issue in your Pluralsight video. Thanks for raising the issue here as I agree it seems like unexpected behaviour. The report should be created in whatever location is specified in OutputPath, and it should attempt to create the directory if it does not exist. Not sure what it should do if it could not create the directory for some reason though...?
MehdiK commentedon May 2, 2014
The directory should be created if it doesn't exist. This is encapsulated in
FileWriterand is very easy to fix.If the directory cannot be created we cannot do anything because the report is being created on appdomain unload which is too late to do anything meaningful. Perhaps we could create it on the default path but that would be confusing too.