Good morning,

When checking in, the full path and name of the test is not viewable, even though  there is space in the window.

 

 

Thanks

 

Ruth

Adding an event listener to an input element to catch Oninput and OnChange events isn't working. 

When attempting to get data related to what is being displayed in the RadCartesianChart I cannot read the nested properties under the Path's Tag field. When retrieving the Tag property it is returned as a string and appears to be pre-populated in the propsBag as a String property

The Path WebAii element has a Data field which returns nested properties for the Geometry, but I do not see similar functionality for the Tag field.  Is this supported or is there guidance on implementing a custom AutomationObject to provide deserilazation and access to the nested properties?  If not can you provided details on the difference to why Data is supported, but not Tag?  Thank you!

in a specific situation with old OnBeforeUnload dialogs appearing, if you have a test list with setting to HandleAndFail execution on unexpected dialog appearing, what happens upon execution is that dialog is handled, but test passes instead of failing, in execution log there is nothing logged that unexpected dialog is shown and handled, but in test studio log there is a strange log that indicates OnBeforeUnload dialog is added to collection, while there is no dialog defined in the test:

Test Studio recorder is not successfully attached to the second window of a WPF application, when the first (login) window is closed in the same time. There is not enough time for Test Studio to attach the recorder before the connection is lost and we are not able to record any steps or use the highlighter.

Pre-requisite: Upgrade to 2019.1.212.0 from 2018.3.1004.0

1. Select the Test List tab

2. Click the List button and add a new Test List with appropriate tests.

3. Click Save

4. Notice the "Storage service unreachable." message pop-up.

5. Click "OK" on the pop-up.

6. Notice that the Test List and Tests are saved as expected.

 

**This issue did not happen on the previous version of Test Studio

After changing the project name and assembly name, the remote execution is failing with FileNotFoundException for the assembly_name.dll. The execution is referring to the old assembly name, even though the correct one is generated in the bin folder.

Additionally there is not such error in local execution.

The workaround for this behavior is to also change the namespace.

While recording the custom web app, there are multiple exceptions in the log file, highlighting isn't working consistently, recording hangs. 

Specific customer's project cannot be compiled. Elements with a specific name generates error in the Pages.g.cs file. 

Details shared internally! 

How do I get rid of this message panel that occupies almost half of the edit window? It's there every time I got to edit an element I have to constantly drag it off to one side.

I don't need to see it every time I edit. This is very annoying. 

 

 

'Validate Expression' button in the Find Expression Builder is not showing the correct element after changing the find expression and not reloading the opened element's pane. 

Steps to reproduce: 

1. Open an element and edit its find expression

Actual: Regardless if saved or not. validating the element still shows the previous element. 

Expected: Validating the element to highlight the correct element. 

Workaround: The issue could be avoided with reopening the element to be edited. 
1. Open the element and edit the find expression. 

2. Save and close the edit element pane. 

3. Open that again to validate the element - the correct one will be highlighted. 

Both the embedded API and Test studio compiled, but the assemblies in API bin folder are not rebuilt. The tests are failing with the following error: 

In order to fix it, we had to manually delete the files in the Embedded API bin files.

Check log below.

Overall Result: Fail

------------------------------------------------------------
'14/02/2019 12:50:56' - Executing test: 'Space_AreaAvailability', path: 'SmokeTest\Space\Space_AreaAvailability.tstest.'
'14/02/2019 12:50:56' - Using .Net Runtime version: '4.0.30319.42000' for test execution. Build version is '2019.1.212.0'.
'14/02/2019 12:50:56' - Starting execution....
'14/02/2019 12:51:01' - Detected custom code in test. Locating test assembly: CAPlusSmokeTest.dll.
'14/02/2019 12:51:01' - Assembly Found: C:\Shireburn\Testing\Shireburn.Testing\CAPlus\TestStudio\CAPlusSmokeTest\bin\CAPlusSmokeTest.dll
'14/02/2019 12:51:01' - Loading code class: 'CAPlusSmokeTest.Space_AreaAvailability'.
------------------------------------------------------------
Overall Result: Fail
------------------------------------------------------------
'14/02/2019 12:51:01' - Detected custom code in test. Locating test assembly: CAPlusSmokeTest.dll.
'14/02/2019 12:51:01' - Assembly Found: C:\Shireburn\Testing\Shireburn.Testing\CAPlus\TestStudio\CAPlusSmokeTest\bin\CAPlusSmokeTest.dll
'14/02/2019 12:51:01' - Loading code class: 'CAPlusSmokeTest.SetCookie'.
------------------------------------------------------------
------------------------------------------------------------
'14/02/2019 12:51:01' - Enabling Html Popup Tracker. Test expecting Popups.
'14/02/2019 12:51:01' - Using 'Chrome' version '72.0.3626.109' as default browser. 
'14/02/2019 12:51:01' - Using 'http://<valid url name>.com' as base url.
'14/02/2019 12:51:01' - LOG: Executing API Test as Step: '.\User Session Token', arguments: 'test --verbose-variables -p "C:\Shireburn\Testing\Shireburn.Testing\CAPlus\TestStudio\CAPlusSmokeTest\ApiTests" -t ".\User Session Token" -v "base-url="XXXXXXXXXX"'" -v "username="XXXXXXXXXX"'" -v "password=XXXXXXXXXX"'
'14/02/2019 12:51:02' - LOG: 12:51:02.659 [INFO]  Project compile started.
'14/02/2019 12:51:02' - LOG: 12:51:02.676 [INFO]  Project compile completed.
'14/02/2019 12:51:02' - LOG: 12:51:02.725 [INFO]  [START]   Test Case 'User Session Token' [.\User Session Token]
'14/02/2019 12:51:02' - LOG: 12:51:02.742 [ERROR] Could not load file or assembly 'Telerik.ApiTesting.Framework, Version=2018.3.927.1751, Culture=neutral, PublicKeyToken=5a31053920bb0a73' or one of its dependencies. The system cannot find the file specified.
'14/02/2019 12:51:02' - LOG: 12:51:02.745 [ERROR] [FAILED]  Test Case 'User Session Token' [28 ms] [.\User Session Token]
'14/02/2019 12:51:02' - LOG: 12:51:02.750 Finished.
'14/02/2019 12:51:02' - 'Fail' : 1. Execute API test 'User Session Token'
------------------------------------------------------------
Failure Information: 
~~~~~~~~~~~~~~~
API test execution failed.
Test error log:
12:51:02.745 [ERROR] [FAILED]  Test Case 'User Session Token' [28 ms] [.\User Session Token]

------------------------------------------------------------
'14/02/2019 12:51:02' - Detected a failure. Step is marked 'ContinueOnFailure=False' aborting test execution.
------------------------------------------------------------
'14/02/2019 12:51:02' - Overall Result: Fail
'14/02/2019 12:51:02' - Duration: [0 min: 1 sec: 397 msec]
------------------------------------------------------------

In customer's application a custom Save Image dialog cannot be handled. 

Details shared internally! 

Button to save a step.  Currently you have to navigate to file menu, use Ctrl-S or Run the Script.

JSON viewer/ XML viewer for the responses detected based on the ACCEPT as JSON or XML for example
    Could really expand on this.  Click on a JSON key/pair and automatically add to verification.  (ie. That element must be this)

Manager.ActiveBrowser.Cookies.DeleteCookie(cookie); doesn't delete the cookie in all cases.

When recording a test on our WPF application, a specific UI control (toggleButton) causes the tested application to crash (Windows Event "APPCRASH").

It only happens when recording a test, and not during normal operation of the application or test execution.

Building the step manually from the DOM explorer doesn't result in a crash.

Rename failure screenshots to reflect parent test that was executed during Test List execution when there are test as step tests. Currently screenshots are named after the test which has the failing step instead of the parent test.

Test Studio's Step Failure Details dialog manages failure data correctly. The possible confusion comes when you explore the stored data in [projectFolder]\Results\[testListName] from windows explorer for example.

Include support for Shadow DOM in Chrome and Firefox

Currently Performance test results can be exported for a single test in a test list only. It will be useful to add the ability to export these for a whole test list result (similar to the web test list results).