|
8 | 8 |  |
9 | 9 |
|
10 | 10 | ``` |
11 | | - ____ _____ _ ____ _ |
12 | | -| _ \ _ _ |_ _| ___ ___ | |_ | __ ) ___ | |__ __ _ __ __ ___ |
13 | | -| |_) || | | | | | / _ \/ __|| __|| _ \ / _ \| '_ \ / _` |\ \ / / / _ \ |
14 | | -| __/ | |_| | | | | __/\__ \| |_ | |_) || __/| | | || (_| | \ V / | __/ |
15 | | -|_| \__, | |_| \___||___/ \__||____/ \___||_| |_| \__,_| \_/ \___| |
16 | | - |___/ |
| 11 | + ____ ____ _ ____ _ _ |
| 12 | +| _ \ _ _ | __ ) ___ | |__ __ _ __ __ ___ / ___| ___ | | ___ _ __ (_) _ _ _ __ ___ |
| 13 | +| |_) || | | || _ \ / _ \| '_ \ / _` |\ \ / / / _ \ _____ \___ \ / _ \| | / _ \| '_ \ | || | | || '_ ` _ \ |
| 14 | +| __/ | |_| || |_) || __/| | | || (_| | \ V / | __/|_____| ___) || __/| || __/| | | || || |_| || | | | | | |
| 15 | +|_| \__, ||____/ \___||_| |_| \__,_| \_/ \___| |____/ \___||_| \___||_| |_||_| \__,_||_| |_| |_| |
| 16 | + |___/ |
17 | 17 | ``` |
18 | 18 |
|
19 | | -**PyTestBehave** is a powerful test automation framework designed to provide a comprehensive solution for testing user interfaces and APIs. It leverages the power of `Behave` framework, `Python` programming language and `Selenium` `WebDriver` to allow the creation robust and maintainable automated tests. |
| 19 | +**PyBehave-Selenium** is a powerful test automation framework designed to provide a comprehensive solution for testing user interfaces and APIs. It leverages the power of `Behave` framework, `Python` programming language and `Selenium` `WebDriver` to allow the creation robust and maintainable automated tests. |
20 | 20 |
|
21 | 21 | ### Key Features |
22 | 22 | 1. **Behaviour-Driven Development (BDD) Support** - allows testers to write tests in a human-readable format using `Gherkin` syntax, making it easier to collaborate with stakeholders and ensure test coverage. |
@@ -48,17 +48,17 @@ The design is split into two sections - **Test Suite** and **Framework Layer**. |
48 | 48 | |-----------|-------------| |
49 | 49 | | **features** | The `Gherkin` style feature files for defining BDD tests | |
50 | 50 | | **features/steps** | The step definitions backing the `Gherkin` tests | |
51 | | -| **features/support/actions** | Test logic actions potentially interacting across one or more pages (Facade) | |
52 | | -| **features/support/pageactions** | The specific page actions, inheriting common actions from the `BasePage` | |
53 | | -| **features/support/core** | The core `ElementAction` which performs all the lower level selenium functionality | |
54 | | -| **features/support/locators** | Locator descriptors and types used for identifying web elements | |
55 | | -| **features/support/builder** | The templating builders to create supporting test data | |
| 51 | +| **features/environment.py** | Default test environment, can be overridden and customised | |
| 52 | +| **support/facades** | Test logic facade actions potentially interacting across one or more pages | |
| 53 | +| **support/pageactions** | The specific page actions, inheriting common actions from the `BasePage` | |
| 54 | +| **support/core** | The core `ElementAction` which performs all the lower level selenium functionality | |
| 55 | +| **support/locators** | Locator descriptors and types used for identifying web elements | |
| 56 | +| **support/builder** | The templating builders to create supporting test data | |
| 57 | +| **support/test_settings.json** | Default test settings, can be overridden and customised | |
56 | 58 | | **drivers** | The web drivers for supported browsers | |
57 | 59 | | **reports** | The json files generated with Allure reports | |
58 | 60 | | **screenshots** | The screenshots taken from failed tests | |
59 | 61 | | **requirements.txt** | File containing all the Python package dependencies | |
60 | | -| **test_settings.json** | Default test settings, can be overridden and customised | |
61 | | -| **environment.py** | Default test environment, can be overridden and customised | |
62 | 62 |
|
63 | 63 | ## **Running the Tests** |
64 | 64 |
|
|
0 commit comments