Apache OFBiz® Selenium-WebDriver Version unspecified Table of Contents 1. Objectifs tests selenium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.4. Découpage des tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6. Tests Selenium (ex-webhelp). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.1. Ecrire des tests fonctionnels

Apache OFBiz® Selenium-WebDriver Version unspecified Table of Contents 1. Selenium tests Type and Goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TODO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.4. Tests organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . With this project it’s possible to write and run Apache OFBiz User Interface Tests, unit tests or Business Use Cases Tests (or demo). There are multiple language or technique to write / record selenium

functionality we want. • We run the test, initially it will fail. • We code the feature. • We re-run our tests, changing the code until it passes. The advantages of TDD is: • It gives us quick feedback when Development, tests are the core of ensuring software quality. Before any production code is written, a test should be written to check to see that the code does what it does. Initially, the tests will fail developed, then more tests should pass until all tests do. At this point, a feature is deemed to be implemented. Some points of note: • It is up to the developer to create tests which are appropriate

functionality we want. We run the test, initially it will fail. We code the feature. We re-run our tests, changing the code until it passes. The advantages of TDD is: It gives us quick feedback when changes Development, tests are the core of ensuring software quality. Before any production code is written, a test should be written to check to see that the code does what it does. Initially, the tests will fail is developed, then more tests should pass until all tests do. At this point, a feature is deemed to be implemented. Some points of note: It is up to the developer to create tests which are appropriate

functionality we want. We run the test, initially it will fail. We code the feature. We re-run our tests, changing the code until it passes. The advantages of TDD is: It gives us quick feedback when changes Development, tests are the core to ensuring software quality. Before any production code is written, a test should be written to check to see that the code does what it does. Initially the tests will fail is developed, then more tests should pass until all tests do. At this point a feature is deemed to be implemented. Some points of note: It is up to the developer to create tests which are appropriate in

functionality we want. • We run the test, initially it will fail. • We code the feature. • We re-run our tests, changing the code until it passes. The advantages of TDD is: • It gives us quick feedback when Development, tests are the core to ensuring software quality. Before any production code is written, a test should be written to check to see that the code does what it does. Initially the tests will fail developed, then more tests should pass until all tests do. At this point a feature is deemed to be implemented. Some points of note: • It is up to the developer to create tests which are appropriate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 10.2. Integration Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . collection of scripts written in Groovy └── test/java/ - java unit-tests ├── testdef - Defined integration-tests ├── webapp - One or more Java webapps including the control is in fact a full application as it contains entities, data, services, user interface, routing, tests, and business logic. Both core OFBiz applications as well as plugins are nothing more than components

Execute all unit tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.4.2. Execute all integration tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.4.3. Execute integration tests with a different log level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.5.1. Run all tests on a clean system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Execute all unit tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.4.2. Execute all integration tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.4.3. Execute integration tests with a different log level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.5.1. Run all tests on a clean system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating configurable keyboard shortcuts Creating a docker PyQt Signals and Slots A note on unit tests Conclusion Managing Python plugins How to install a Python plugin Caution Custom Python plugins objects, you only have to put their names between quotation marks. A note on unit tests If you want to write unit tests for your plugin, have a look at the mock krita module [https://github.com/rbreu/krita-python-mock] PYQT_SIP_DIR_OVERRIDE USE_LOCK_FREE_HASH_TABLE FOUNDATION_BUILD KRITA_ENABLE_BROKEN_TESTS LIMIT_LONG_TESTS ENABLE_PYTHON_2 BUILD_KRITA_QT_DESIGNER_PLUGINS BUILD_TESTING If set to ON, the unittests