axafrance / webengine-dotnet Goto Github PK

Google has recently changed download Url for ChromeDrivers.
WebEngine Framework need to be adapted for this change.

Reference: https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints
Changes:

• Url of "Latest driver version" has been changed
• Url of "chromedriver" has been changed
• Driver are now placed in a folder inside the zip.

During the installation of a new driver, a directory is created.

If the download fails (network error etc.), the directory is not deleted. This is a problem because during the test run, the framework thinks the correct version is installed but the driver launch fails (exe not found) and it does not try to re-download it.

Advice: Do not leave a directory with an expected name if the download is not successful.

Older version of webdriver are not cleaned up, after several updates the storage starts to weigh heavily:

Advice: delete old driver versions when a newer version has successfully installed.

Today the sensitive test data, like keys and password can be encrypted using AES with customized encryptionKey, passing either via command-line or configuration file.

To make sensitive test data more safe, It is better to support also certificate and passphrase.

Issue and Steps to Reproduce

• Run a data-driven test, generate test report
• in the report execution time for Test Case is always 0
• in JUnit report, the execution time is also 0 (based on the value of TestCase)

There is an upstream bug in SafariDriver:

when GetDomProeprty is called, the driver throws an exception saying "method not yet implemented"
Investigation need to be performed.

Problem

In some cases, the identification of web element is tough,
For example: Identify an element in a cell of table, identify an element which has no usable identifier.
In these case, maybe using relative identifier would help.

That is describing an element using another element and the relation of current element.

For example:
A textbox with in the column header and row header
A button on the same y-axis of it's label....

To achieve this we need to add "relatedElement" in "ElementDescription".

WebEngine Framework supports Desktop browsers running locally. Selenium Grid is only used to executed mobile/Appium based tests.

Consider support Selenium Grid for Desktop tests.

Study the possibility of locating WebElement by Image

Requested by some test engineers, we will work on generating HTML format reports.
So the report can be viewed without the need of Report Viewer.

Review descriptive object-model:

• Use XElement to hold web elements, with actions associated.
• WebElementDescription holds only identifiers (attributes or DOM properties)
• Use XElement.Describe(WebElementDescription) to describe an element
• XElement will be the base for Buttons, Checkboxes, Textboxes etc..

Issue and Steps to Reproduce

Study on axe-core library for selenium
Integrate accessibility test with the framework

Issue and Steps to Reproduce

iFrame is a big barrier to web test automation:

• Sometimes it's hard for users to "aware" whether the element is in an iFrame.
• Switching the context between main page and iFrames are also hard to manage.

Proposition

• WebEngine Framework would review object identification strategy, and can automatically find elements within the iFrames if possible.
• The Framework handles context automatically.
• Users can just write test scripts straightly.

Support declaring a WebElementDescription via attribute, the implementation is similar to Selenium Page Objects

@FindBy(how = How.CLASS_NAME, using = "classname")
private List<WebElement> singlecriterion;

In WebEngine .NET, it will be implemented with FindsByAttribute

[FindsBy(How = How.Id, Using = "element-id1")]
public WebElementDescription SubmitButton {get;set;}

Enhancement:

• The presentation of an element is simplified for identifiable elements

Usage:

• Supported locators can be either defined in FindsByAttribute, or via its properties
• Use of FindsByAttribute is not mandatory
• It is not recommended to declare WebElementDescription in both Property and Attribute.
• If the same locator is defined in both Property and attribute, the value provided in attribute will be ignored.

Find a way to support passing webdriver options (e.g, incognito mode)

• Improve BrowserFactory.GetDriver to support passing webdriver options.
• Improve the structure of test configuration file appsettings.json to provide solution wide webdriver options for each supported browser.

Issue and Steps to Reproduce

Aujourd'hui, lorsque on utilise le report viewer pour lire nos cas de tests, on a pas l'information sur le nombre de cas de tests qui se trouvent dans le rapport

Versions

Screenshots

Expected

ça serait trés pertinent d'afficher un le nombre de cas de tests qui se trouvent dans le rapport

Actual

on a pas l'information sur combien de cas de tests lu par le rapport

Additional Details

il serait bien d'afficher ce compteur entre le champs filtre et la case Failed

• Installed packages: