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
Failure Dump is a useful feature to provide various output data in the form of files to the person inspecting tests. However, we sometimes want to provide such output even if the test passes. There are two cases already:
Accessibility reports, see AccessibilityCheckingConfiguration.CreateReportAlways. This has special treatment now in UITestExecutor.
Security scan reports, see SecurityScanningConfiguration.CreateReportAlways. This is not even working until this issue is completed.
So, rename Failure Dump (and everything related to it in the code, docs, and in LGHA) to Test Dump and change how it works:
Always generate it if UITestContext.FailureDumpContainer (which should be renamed) is non-empty.
Remove the special treatment of AccessibilityCheckingConfiguration.CreateReportAlways.
Make SecurityScanningConfiguration.CreateReportAlways public and remove the note from its docs about this issue.
Failure Dump is a useful feature to provide various output data in the form of files to the person inspecting tests. However, we sometimes want to provide such output even if the test passes. There are two cases already:
AccessibilityCheckingConfiguration.CreateReportAlways
. This has special treatment now inUITestExecutor
.SecurityScanningConfiguration.CreateReportAlways
. This is not even working until this issue is completed.So, rename Failure Dump (and everything related to it in the code, docs, and in LGHA) to Test Dump and change how it works:
UITestContext.FailureDumpContainer
(which should be renamed) is non-empty.AccessibilityCheckingConfiguration.CreateReportAlways
.SecurityScanningConfiguration.CreateReportAlways
public and remove the note from its docs about this issue.Related: xunit/xunit#2457
Jira issue
The text was updated successfully, but these errors were encountered: