Cody Gibson

Only scroll to visible the target element when necessary

Currently when a test step is set to SimulateRealClick or SimulateRealTyping, the target element is unconditionally scrolled to the top of the browser window, even in cases where the element is already visible.
It would be more efficient to test if the target element is already fully visible and only scroll when needed.
Feature Request by Cody Gibson Status: Not Done Comments: 3 Last update: 2017-11-17T13:49:01 by Bart Drewoux
0
Daniel Djambov
Team Member

Test As Step called in code does not populate all inner exceptions

when executing test as step from code and there is exception in the executed test, not all exception information is populated back to parent test.
Feedback by Daniel Djambov Status: Not Done Comments: 0 Last update: 2017-11-17T07:13:00 by Daniel Djambov
0
Elena Tsvetkova
Team Member

Add the option to compile the project for the execution with ArtOfTest Runner

It would be useful to have the functionality to build the project from command line.
Feature Request by Elena Tsvetkova Status: Reviewed by QA Comments: 0 Last update: 2017-11-14T11:56:10 by Ivaylo Todorov
0
Elena Tsvetkova
Team Member

In dev flag does not work as expected when 'Revert to Server version' is used in SC

Steps to reproduce:

1. Create a sample project and connect it to source control. Perform the initial check-in

2. Set a test with the In Development flag and save the project. This will mark the Settings file as pending change

3. Revert the Settings file to Server version

Expected: The Settings file is reverted and there are no tests listed In Development and this reflected in the UI as well.

Actual: The Settings file is reverted and there are no tests listed In Development. But the file initially flagged is still displayed in red and its context menu allows you to remove the In Development.
Feedback by Elena Tsvetkova Status: Reviewed by QA Comments: 0 Last update: 2017-11-14T11:54:52 by Ivaylo Todorov
0
Boyan Boev
Team Member

Add an option for calibrating in Test Studio Runtime

It will be much easier and faster to configure the browsers if we have such functionality in case you don't have installed Test Studio Standalone version.
Feature Request by Boyan Boev Status: Done Comments: 12 Last update: 2017-11-10T20:35:42 by George Nelson
0
Elena Tsvetkova
Team Member

Wait/Verify NOT exists step for element with data driven expression does not throw exception for missing variable

Please find attached a sample project demonstrating the below listed issue.

Details shared internally
Feedback by Elena Tsvetkova Status: Not Done Comments: 0 Last update: 2017-11-10T09:26:07 by Elena Tsvetkova
0
Elena Tsvetkova
Team Member

Unable to select table of excel data source due to Windows update

Multiple customers reported that after applying a Windows update KB4041676 on a windows 10 system all excel files bound as data source in a Test Studio project stopped working as expected - the file stayed bound but no tables appear to select any of these.

It would be good to investigate what that update causes.
Feedback by Elena Tsvetkova Status: Won't Fix Comments: 8 Last update: 2017-11-09T13:58:42 by Dhruv Parekh
0
Elena Tsvetkova
Team Member

Verify or Wait for element to ExistNot do not refer the element from the repository when converted to code

Steps to reproduce:

1. Create a sample project and add the following steps:

- Verify element Exists

- Verify element ExistsNot

- Wait element Exists

- Wait element ExistsNot

2. Convert these to code and double check that the ExistsNot steps refer to an element with the current find expression. In contrary the Exists steps refer the element from the Pages file directly.

That way editing the find expression of the element will be updated and referred in the Exists steps. But the ExistsNot steps in code should be manually updated.

Expected: The elements in all converted steps to be referred from the elements' repository.
Feedback by Elena Tsvetkova Status: Not Done Comments: 0 Last update: 2017-11-09T13:51:04 by Elena Tsvetkova
0
Elena Tsvetkova
Team Member

Converting Verify or Wait step to code generates the same line of code

Steps to reproduce:

1. Create a Verify element Exists and Wait for element exists steps

2. Converting both to code generates Pages.Element.Wait.ForExists(30000);

Expected would be that the Verify element Exists step rely on the global project elements timeout or alternatively verifies immediately.

Actual: The current implementation is that the Verify step takes the default wait timeout for a wait step.
Feedback by Elena Tsvetkova Status: Not Done Comments: 0 Last update: 2017-11-09T13:41:58 by Elena Tsvetkova
0
Nikolay Petrov
Team Member

During execution an element could not be located for a customer specific application

Steps to reproduce and access to the application are in the internal description.
Problem by Nikolay Petrov Status: Reviewed by QA Comments: 4 Attachments: 2 Last update: 2017-11-08T14:13:41 by Briar Parmer
0
Displaying items 1 - 10 of 2154