Workflow for using Unit Tests in Oxid?

In our team we’re trying to implements unit tests for modules which we are creating. I have done some research about how it works in Oxid and I ran some tests using testing_library (
Tests are running but execution time is really long… We use only one module to test at the same time and we have disabled shops tests. Here is our test_config.yml:

# This file is auto-generated during the composer install
shop_path: source
shop_tests_path: tests
partial_module_paths: kira/skeletonmodule
shop_url: null
shop_serial: ‘’
enable_varnish: false
is_subshop: false
install_shop: false
remote_server_dir: null
shop_setup_path: null
restore_shop_after_tests_suite: false
test_database_name: null
restore_after_acceptance_tests: false
restore_after_unit_tests: false
tmp_path: /tmp/oxid_test_library/
database_restoration_class: LocalDatabaseRestorer
activate_all_modules: false
run_tests_for_shop: false
run_tests_for_modules: true
screen_shots_path: null
screen_shots_url: null
browser_name: firefox
selenium_server_port: ‘4444’
additional_test_paths: null
retry_times_after_test_fail: 2

In our case when I call runtests I must wait 20 seconds when the tests finish. Do you have the same performance problem or you are using other Unit Testing Workflow?

Now we try to use PHPUnit directly from oxid-eshop vendor for each module but in this case we can’t use testing library (I mean I can’t use extended class BaseTestCase from OxidEsales\TestingLibrary namespace) - I can use directly PHPUnit_Framework_TestCase class only without Oxid Testing Library extensions…

My main question is What does your workflow look like with creating a module and unit testing?
We are trying to find the best solution for us.