Check for conflicting applications before running OPBM tests

[van-smith]

Upon launching a set of assessments, check to see if there are any conflicting applications on the system. If they are found, enumerate them for the user and tell the user that the applications must be uninstalled before the benchmark can run the selected tests.

[ghost]

Framework has been created to support this. Scripts need to be written to check for conflict conditions. The syntax is two new opbmCommon.au3 functions, "outputConflict()" and "outputResolution()", which must appear in a 1:1 ratio. They are scraped by the harness at each run's startup, and if found they stop the run and display a two-column listing of each conflict and each resolution side-by-side.

[ghost]

Tests for chrome, opera, ie9, office2010.

[van-smith]

Verified for Chrome.

[van-smith]

Verified for Opera.

[kathy-smith]

Verified that UAC check works.

[kathy-smith]

Cool! Conflict and Resolutions window. Verified Powerpoint 2010, Access 2010, Publisher 22010, Excel 2010, Word 2010 check works.

[kathy-smith]

Verified Auto Logon Window check.

Yes button on window does not launch official run.

No button closes Conflict and Resolutions window. Cancel button closes Conflict and Resolutions window. More... button displays sets to disable Windows 7 logon screen.

[ghost]

Works for me.

[van-smith]

What works for you?

[ghost]

Clicking the "Yes" button launches the official run.

[kathy-smith]

I am going to test the Auto Logon Window on several systems.

Last night I set-up and ran OPBM on a system that did not have Office 2010 installed on it. I got the Conflict and Resolutions window. I then went back into the system and enabled the Windows 7 login screen to see what whould happen. I tried each button with the results above. When I clicked on the Yes button, the Auto Logon window disappeared. The OPBM GUI stayed up.

I'll disable on several over systems and see what happens.

[kathy-smith]

Ran on Atom - worked when I enabled the login screen, then tried to run the official run Ran again on Atom after uninstalling Opera - worked, Auto login window appeared. Clicked on Yes. Launch started Ran again and clicked on More. The disable-windows-login.txt appeared. I closed the window. Ran again and clicked on No button. The Auto login window disappeared. Ran again and click on Cancel button. The Auto login window disappeared. Ran again and clicked on More button. The disable-windows-login.txt DID NOT APPEAR. Ran again anc clicked on Yes button. The Auto login window disappeared .LAUNCH DID NOT START.

[ghost]

What Atom were you running? When I do this for an Official Run, following your steps (yes, more, no, cancel, more, yes) everything works and I am unable to reproduce your more and yes failures.

[van-smith]

Kathy is out at the moment. She is head of the local homeschooling co-op and won't be back for a few more hours.

Her statements above mean that she ran the tests on the Atom SUT. All of her attempts were Official Runs.

She had success on her first attempts, but experienced failures on subsequent attempts. I think her description above is typical of the steps she took to promote the failure.

[kathy-smith]

Yes, I'll try this again on the atom system to see what happens. The failure occurred on the atom and then on another laptop that is not a SUT.

I documented the steps that I took to create the failure on the Atom system. I'll let you know if/when I recreate. On Oct 31, 2011, at 8:14 AM, Rick C. Hodgin wrote:

What Atom were you running? When I do this for an Official Run, following your steps (yes, more, no, cancel, more, yes) everything works and I am unable to reproduce your more and yes failures.

Reply to this email directly or view it on GitHub: https://github.com/van-smith/OPBM/issues/32#issuecomment-2576676

[ghost]

Are you exiting the app between each "Ran again"? Or are you clicking the "Official Run" link?

[kathy-smith]

I did not exit OPBM. I clicked the Official Run link.

On Oct 31, 2011, at 8:14 AM, Rick C. Hodgin wrote:

What Atom were you running? When I do this for an Official Run, following your steps (yes, more, no, cancel, more, yes) everything works and I am unable to reproduce your more and yes failures.

Reply to this email directly or view it on GitHub: https://github.com/van-smith/OPBM/issues/32#issuecomment-2576676

[ghost]

I have run this in 1.6.0_25, and 1.7 in a continuous barrage of button selections, and I cannot get it to fail.

After I click "Yes" to allow the Official Run to begin, I immediately click "Stop" to stop it, and then retry other buttons. I have not let it complete even the first conflict check atom. Is this the same as in your testing?

[kathy-smith]

I tried to recreate and couldn't get it to recreate on the atom system.

I'll try again tomorrow on several systems.

I tested by choosing Yes and stopping the run, not sure when I stopped it, then clicked the No, Cancel, More, Yes

It was on the second Yes that it failed.

I tried several iterations today with it working each time on the atom.

Kathy On Oct 31, 2011, at 7:46 PM, Rick C. Hodgin wrote:

I have run this in 1.6.0_25, and 1.7 in a continuous barrage of button selections, and I cannot get it to fail.

After I click "Yes" to allow the Official Run to begin, I immediately click "Stop" to stop it, and then retry other buttons. I have not let it complete even the first conflict check atom. Is this the same as in your testing?

Reply to this email directly or view it on GitHub: https://github.com/van-smith/OPBM/issues/32#issuecomment-2585508