-
-
Notifications
You must be signed in to change notification settings - Fork 851
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
Is it necessary to open console windows in run-tests? #558
Comments
It is dump-jpeg-coeffs.exe being executed by |
thanks. |
works.
by var process = new Process
{
StartInfo =
{
UseShellExecute = true,
CreateNoWindow = true,
WindowStyle = ProcessWindowStyle.Hidden,
FileName = DumpToolFullPath,
Arguments = args,
RedirectStandardOutput = false
}
};
process.Start();
process.WaitForExit();` |
@jongleur1983 great, thanks for the investigation! Do you want to PR it, or would you rather leave it to us? |
as you like. I didn't want to change branches yesterday to commit that change on a separate PR, but if nobody else takes this before I'll do a PR within this week, I think. |
#558: hide console windows during run-tests
Fixed in #561 |
Prerequisites
DEBUG
andRELEASE
modeDescription
the run-tests.ps1 script is used to run the unit tests.
When I run it from a powershell console window (on Windows10) repeatingly other windows pop up for some fraction of a second. These windows look like cmd console windows or similar, but I'm not sure as they close immediately.
My issue with that is: While tests are running I often would like to do other stuff in parallel, but those flashing windows not only are visually disturbing, they steal the keyboard input focus as well.
I'm not sure where they're originating, but it would be great if we could either hide them or get them opening in background instead.
Steps to Reproduce
System Configuration
The text was updated successfully, but these errors were encountered: