-
Notifications
You must be signed in to change notification settings - Fork 43
Handle Invalid Output Directory #303
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please add back the unittest in consoleoutputtest.
@@ -178,7 +178,11 @@ | |||
|
|||
//setting defaults for optional parameters outside RunTestAsync | |||
var testResult = await testEngine.RunTestAsync(testPlanFile, environmentId, tenantId, outputDirectory, domain, queryParams); | |||
Console.WriteLine($"Test results can be found here: {testResult}"); | |||
if (testResult != "InvalidOutputDirectory") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In PAC CLI >> when we update the TE version with this fix included, reminder to make this change there.
Description
If output directory exists but is invalid, such as a drive doesn't exist, handle this properly so this doesn't throw an unknown error up the chain.
Checklist