I am using a tool for verifying if app is compliant with windows accessibility feature
Tool web link - https://accessibilityinsights.io/downloads/
Test tool have simple MFC combo box .
Tool says "No Failure was detected",
Insight tool shows a error icon.
Below are steps to get above state.
Launch app
Launch Insight tool
select what to test = element
Mouse hover on combo box
expand the combobox
mouse hover on item
click on brush icon on right
It will enter the state described abovewith no error but with error icon
Isolation:
Issue doesn't repro when "Entire App" is selected.
When "Entire App" is selected, tool does not show any error or any error icon. App pass accessiblity
Question is if this tool is reporting valid error ?
What is the error as tool says " No failure was detected."
What you're seeing here is an artifact of trying to capture a transient state. Combobox content goes away when the combobox closes, and that happens as soon as you start the scan. Accessibility Insights for Windows allows you to trigger a scan using a timer, as documented at https://accessibilityinsights.io/docs/windows/getstarted/automatedchecks/#running-automated-checks-with-a-timer. The "short version" is that you start the timer, then open the combobox while the timer is counting down, and the checks will run when the timer reaches zero. The combobox will still be fully opened at this point, so the tests will apply to the combobox contents.
My personal recommendation is to set the scope to the entire application when using the timer, just because transient controls sometimes have multiple layers and trying to have the scope of just the element can tend to hide children of the layers in question.
Thanks for using Accessibility Insights
--DaveTryon
Accessibility Insights team
I have a console application that I can't seem to make launch properly on system startup.
I've debugged it by putting together a really simple console application that's simply just
Sub Main()
Console.WriteLine("This is a console application")
Console.ReadLine()
Environment.Exit(0)
End Sub
And even that won't work. The application is launching, I can see it in the task list. But the console interface isn't displaying, and that's the problem.
I've tried both using the Start Up folder and Windows Task Scheduler to get it to come up, neither seem to work.
Is there some registry setting somewhere I might change?
Any help would be awesome.
Thanks.
According to Microsoft, the task will only run interactively if the "Run only when user is logged in" radio button is selected.
"You can specify that a task should run even if the account under which the task is scheduled to run is not logged on when the task is triggered. To do this, select the radio button labeled Run whether user is logged on or not . If this radio button is selected, tasks will not run interactively. To make a task run interactively, select the Run only when user is logged on radio button."
Source: https://technet.microsoft.com/en-us/library/cc722152.aspx?f=255&MSPPError=-2147217396
I want to show "Welcome Back" popup after auto-signIn process as stated in the following documentation(FAQ part) :
https://developers.google.com/games/services/branding-guidelines
I have tried some methods like reconnecting etc. but it couldn't work. How can I show Welcome popup without signing out the user and showing account selection popup again?
What you are asking does not appear to be possible. According to the documentation at Google Developer
public GamesClient.Builder setShowConnectingPopup (boolean showConnectingPopup)
Sets whether a "connecting" popup should be displayed automatically at the start of the sign-in flow. By default this is enabled.
Note that this call will use the default gravity for the "connecting" popup, which will display the popup at the center of the screen. If you prefer that the popup appear in a different section of the screen, you can use setShowConnectingPopup(boolean, int), and provide a Gravity value.
Parameters
showConnectingPopup Whether or not to show a "connecting" popup at the beginning of the sign-in flow. Default behavior is for this to be true.
Returns
This Builder.
In watching the log output during a reconnect, I can find no discernible difference if performing it after backing out and immediately reconnecting (without logging out the user). Only if the user if forcibly disconnected.
Yet, looking at the flow, and this documentation, and the branding guidelines, the behavior Should be to show the "Welcome" popup as long as the setShowConnectingPopup is set to true.
It would be nice if Bruno (hint hint) or any other Google Play Services could weigh-in on this, as it would appear we are violating the branding guidelines if we DON'T have the "Welcome" on each sign in (even though this is a new requirement as worded by Google, along with some of the other branding stuff)
As far as I can tell my original answer StackOverflow link is still the only way to do this "Every" time, but if a user has multiple accounts, then yes the account selection will popup.
(my tests are on multiple devices, running from 4.1.32 and before.)
I have a Windows Server 2008 with scheduled tasks running, mainly .bat files calling PHP files. I have 2 users on the server, one Admin and the other is a Standard user.
I used the Standard User to clear the history log in the Task Scheduler History tab using the Event Viewer. Now it won't record any history anymore. All of the scheduled tasks no longer have history in the History tab. However, the Last Run Result returns 0x0 and the schedulers are working fine.
Please advise.
Step 1: Open an elevated Task Scheduler (ie. right-click on the Task Scheduler icon and choose Run as administrator)
Step 2: In the Actions pane (right pane, not the actions tab), click Enable All Tasks History
That's it. Not sure why this isn't on by default, but it isn't.
I have another possible answer for those wondering why event log entries are not showing up in the History tab of Task Scheduler for certain tasks, even though All Task History is enabled, the events for those tasks are viewable in the Event Log, and all other tasks show history just fine. In my case, I had created 13 new tasks. For 5 of them, events showed fine under History, but for the other 8, the History tab was completely blank. I even verified these tasks were enabled for history individually (and logging events) using Mick Wood's post about using the Event Viewer.
Then it hit me. I suddenly realized what all 8 had in common that the other 5 did not. They all had an ampersand (&) character in the event name. I created them by exporting the first task I created, "Sync E to N", renaming the exported file name, editing the XML contents, and then importing the new task. Windows Explorer happily let me rename the task, for example, to "Sync C to N & T", and Task Scheduler happily let me import it. However, with that pesky "&" in the name, it could not retrieve its history from the event log. When I deleted the original event, renamed the xml file to "Sync C to N and T", and imported it, voila, there were all of the log entries in the History tab in Task Scheduler.
The adjustment in the Task Scheduler app actually just controls the enabled state of a certain event log, so you can equivalently adjust the Task Scheduler "history" mode via the Windows command line:
wevtutil set-log Microsoft-Windows-TaskScheduler/Operational /enabled:true
To check the current state:
wevtutil get-log Microsoft-Windows-TaskScheduler/Operational
For the keystroke-averse, here are the slightly abbreviated versions of the above:
wevtutil sl Microsoft-Windows-TaskScheduler/Operational /e:true
wevtutil gl Microsoft-Windows-TaskScheduler/Operational
I think the confusion is that on my server I had to right click the Task Scheduler Library on left hand side and right click to get the option to enable or disable all tasks history.
Hope this helps
Here is where I found it on a Windows 2008R2 server.
Elevated Task Scheduler
Click on "Task Scheduler Library"
It appears as an option on the right hand "Actions" panel.
This may help others where there is no option to Enable/Disable the history anywhere in Task Scheduler.
Open Event Viewer (either in Computer Management or Admin Tools > Event Viewer).
In Event Viewer make sure the Preview Pane is showing (View > Preview Pane should be ticked)
In the left hand pane expand Application and Service Logs then Microsoft, Windows, TaskScheduler and then select Operational.
You should have Actions showing in the preview pane with two sections - Operational and below that Event nnn, TaskScheduler. One of the items listed in the Operational section should be Properties. Click this item and the Enable Logging option is on the General tab.
My problem was that the maximum log size had been reached and even though the overwrite old events option was selected it wasn't logging new events. I suspect that might have been a permissions issue but I changed it to Archive when full and all is now working again.
Hope this helps someone else out there. If you don't have the options I've mentioned above I'm sorry, but I don't know where you should look.
Win 8.1 Pro
Brian Clark's answer above worked for me, but I'm posting here for those who may have to follow a slightly different sequence as I did.
When I ran Control Panel > Administrative Tools > Right Click Task Scheduler - 'Run as Administrator', I found the Actions pane to already contain the following action:
Disable All Tasks History
So my machine already had History enabled. But my machine needed to disable history first, then go back and 'Enable All Tasks History'. After that, my History showed up and I received no more errors. I'm assuming that action performed some type of initialization or setup that was never done properly from all the way back to OS installation.
I will also add that I had to exit Task Scheduler and reenter it before I could toggle the History Enable/Disable setting back and forth.
As noted earlier, there is an option to turn on or off History provided you open up task manager under the elevated "Administrator" mode (right click on the Task Scheduler program/shortcut and choose "Run As Administrator"). Then under "Tasks" is your spot to stop or start History.
I'm using Selenium Web driver for testing, but can't ecen get past login page. The code I'm using:
driver.Navigate().GoToUrl(baseURL + "URL");
driver.FindElement(By.Id("loginForm:username")).SendKeys("uName");
driver.FindElement(By.Id("loginForm:password")).SendKeys("pass");
driver.FindElement(By.Id("loginForm:login")).Click();
Element locators are correct and login click is happening, but after that I am not logged in, but page is just stuck there - no error or something. Same code worked in IDE.
I'm using IE9 and also there is changed settings:
var options = new InternetExplorerOptions();
options.IntroduceInstabilityByIgnoringProtectedModeSettings = true;
driver = new InternetExplorerDriver(options);
Any advices how to overcome this problem?
This happens with me very often, but not sure if it is the same reason for you.
When you run the tests locally, all the actions (sendkeys, click etc) take place really quickly. The loginForm:login button could be kept disabled until the user enters text in fields loginForm:username and loginForm:password. So there is a possibility that the button loginForm:login could have not been active when it is being clicked.
So I would recommend using an explicit wait to check if the element id loginForm:login is displayed before clicking it.
This step is basically useless but all it does is simply waste some time between "sending keys" to the password text box field and clicking submit.
Also for a quick check you could also do something similar to sleep 2 (make the script sleep for 2 seconds) after entering the password and before clicking the login button.
IF you eventually plan to run this on a remote machine, you dont need to do any of the above two steps, the time delay due to communication between the machines will be sufficient for the whole process to work smoothly.
(The same problem occurs on the linkedin login page- Login button is disabled unless Username and password is entered, but the speed at which the webdriver performs each step, The login button is not active when being clicked on.)