Alexandre Patelli

Assert an html element is on page optionally with attributes ```gherkin the page contains 'cssSelector' (visible) (with attributes 'key1:value1', 'key2:value2'...) ``` Assert html elements are on page providing yaml list...

Perform an action (CLICK, FILL...) with optional parameters on one or multiple elements. ```gherkin we perform a 'action' (with 'parameters...') on 'cssSelector' (waiting 'cssSelector' (visible)) ``` Perform a list of...

Navigate to an url with the possibility to wait for an element ```gherkin browser navigate to 'url' (waiting 'cssSelector' (visible)) ``` Assert what browser url is ```gherkin browser url is...

This module must take into account that tests could be run in parallel so we need to develop proper thread isolation with browser.

### Import User needs only to import tzatziki-front and an implementation (tzatziki-playwright) ### Browser configuration Browser type can be setup using env variable : TZATZIKI_BROWSER\ Some others parameters could also...

This root module defined 3 important interfaces that will be used to interact with front components : **Browser**\ Interface that expose method to manipulate the browser * **get(url)** : navigate...

This submodule needs to implement all the interfaces provided by tzatziki-front module using the playwright engine.

In a lot of scenario, you want to check on the same type of html element across multiple tests. \ Those css selectors are some times really complex and really...

We want to propose generic gherkins steps that can be used to manipulate and assert on the browser so user don't have the need to create custom steps that manipulate...