I'm getting them all over. If I record a new step it works, even though the search is the same as the existing one.
Is anyone else getting these errors?
InnerException:
System.NullReferenceException: Object reference not set to an instance of an object.
at ArtOfTest.WebAii.Win32.Annotator.Clear()
at ArtOfTest.WebAii.Headless.HeadlessMouse.ClickImpl(MouseClickType clickType, Int32 x, Int32 y, Int32 wheelDelta, Boolean relativeCoordinates)
at ArtOfTest.WebAii.Win32.Mouse.ClickElement(Element element, MouseClickType clickType, Point offset, OffsetReference reference)
at ArtOfTest.WebAii.Design.IntrinsicTranslators.Descriptors.DesktopActionDescriptor.Execute(Browser browser)
at ArtOfTest.WebAii.Design.Extensibility.HtmlActionDescriptor.Execute(IAutomationHost autoHost)
at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.ExecuteStep(Int32 order)
Rank 2
Iron
Iron
3 Answers, 1 is accepted
Rank 1
Iron
Based on some testing just now it finds the element but fails to click it, firing the error instead.
And once again a new, recorded step with the same element search works.
Hello Jim,
Thank you for sharing the complete error message - that helped us sort out the issue.
I assume you see the errors in the following state:
- The test runs with enabled annotations. For test lists this is a setting under the General tab called AnnotateExecution.
- The error appears on steps of type Desktop command: LeftClick on 'element'
- The tests are executed without extension - the checkbox in the Project settings->Browsers is unchecked.
If any of the above is not right, please, let me know.
If our assumptions are correct, we will work on implementing a fix for this error on running existing steps, but in the meantime you can use the following workarounds:
- One option is to disable the annotations - that way the error shouldn't pop up.
- The other option is applicable for the test runs in which you need the annotations - then you can enable the extension to execute the test with enabled annotations.
I hope the provided information is useful for you. Let me know in case of any additional questions one the case.
Regards,
Elena
Progress Telerik
Rank 1
Iron
- I almost always turn on Annotations and watch it as the test is run.
- I agree the error occurs when I try to left-click something. I can't say yet whether it occurs elsewhere.
- The browser extension has been turned off for months, based on your advise.
Number two above: Do you mean enable the browser extension or enable annotations? If I enable annotations why do you think it won't error out?
I don't understand the relationship between the two, if there is one.
HI Jim,
Thank you for your notes.
The issue is caused by some changes introduced with the latest release - these changes specifically concern the execution of existing desktop click steps with enabled annotations with the extensionless mode browser.
Therefore you have two possible workarounds.
1. The first one is to run the tests without the annotations. If you disable the annotations the error will no longer fail the tests.
2. The other possible workaround is to continue using the annotations enabled and run the tests in the browser mode with extension.
Having in mind your note that we have recommended to stop using the extension at some point, this second option doesn't seem feasible for you.
As a conclusion the only possible workaound for you is to disable the annotations in order to continue run the tests.
Let me know if you have any additional questions.
Regards,
Elena
Rank 1
Iron
One of you said Test Studio was moving away from the browser extension and/or said it didn't make any difference checked or un-checked. Hence my decision to uncheck it. Combined with some issue I was having. I only test in Chrome.
What is the risk of setting the browser extension to checked?
Do you have a plan to fix the bug, and if so when would I see it?
Do I have the option of reverting to the previous release? The annotation tool is really important to me.
Hi Jim,
Currently Test Studio can automate Chrome and Edge in two different modes - one uses the extension, and the other implementation doesn't use any extension. The extensionless mode was initially developed because Chrome announced that the content extensions (what the Test Studio one is) will be deprecated at some point if the future. Thus we needed to implement different way of automating the browser.
Since the extensions are still not deprecated (by Chrome) we continue supporting the two options from our perspective. This allows us to provide a possible workaround for some issues while we investigate and fix these without interrupting our customers' day to day work.
I can't recall what was about that previous discussion where the recommended solution for you was to switch to running the tests in the extensionless mode. But I assume that you might need to stick to this mode - therefore I added the note that the second suggestion about switching to the mode with extension might not be suitable.
In the general case we do not expect any differences in the test recrding and execution with or without extension. So, you can give it a try - if there is anything that bothers you, let me know.
The issue will be fixed and released with our next official service pack release. It can be expected until the end of the year.
You can install previous version of Test Studio, but I wouldn't recommend you to downgrade as there are other fixes in that latest release, which are useful for you. I'll check with the development if we can prepare a custom build with the fix in question and will contact you back.
Regards,
Elena
Rank 1
Iron
I re-wrote your response for my own clarity. Did I do it correctly?
"You can install the previous version of Test Studio, but I wouldn't recommend it.
There are fixes in the latest version which are useful for you.
I'll check with the development if we can prepare a custom build with the fix in question and will contact you back. "
What is the particular fix you think I should have?
I will add the extension and test it out.
I tried to search all of my tickets using the word 'extension'. I found the search only searches the title. I suggest you upgrade that functionality to search the body of the ticket too.
Finally, is there a way to speed up or slow down the playback if the Annotations feature can not be used? I toggle it all the time to see what is happening.
Hi Jim,
The fixes I have in mind are related to the steps pane and the operations you perform while maintaining the tests.
Your feedback about the search through the tickets is provided to the responsible team internally.
The annotations is the only way to directly slow down the quick execution of single test. Other option is to run the test as part of test list and increase the setting ExecutionDelay.
And finally, I am opening a private support ticket on your behalf where I will share further details on receiving a fix for the issue we discuss.
Regards,
Elena