This folder contains examples which are also used for testing. These examples cover multiple QUnit scenarios (eg. async, nested modules) and QUnit versions (eg. v1.18, v2.22). They also cover the usage of WDIO QUnit Service with other services (eg. Static Server, Code Coverage), and in SAP Fiori / UI5 apps.
wdio.conf.js contains specs and suites properties allowing to run many combinations of tests. See WebdriverIO Grouping Test Specs in Suites and WDIO Qunit Service config.
wdio.no-specs.conf.js contains the configuration to run tests without any .spec or .test file. See WDIO QUnit Service config. The property baseUrl is set, therefore there is no need to repeat http://localhost:4567 in all paths mapped into the service config.
wdio.features.conf.js is used to test WDIO QUnit Service with other services such as monocart for code coverage.
All QUnit folders execute the same generic tests, except qunit-fail and qunit-preconfiguration. The generic folders are used to test WDIO QUnit Service with different QUnit versions.
The folder qunit-fail will execute tests that fail on purpose, just to see how it's reported back into the service.
The folder qunit-iframes will execute QUnit tests in iframes, similar to what happens in UI5 - webapp/test/testsuite.qunit.html.
The folder qunit-preconfiguration will execute tests for QUnit Preconfiguration method.
There are two ways to use QUnit to test SAP Fiori/UI5 apps. Loading the QUnit from an HTML file (like any other regular QUnit usage) or loading it via Test Starter, an UI5 module to orchestrate QUnit and OPA5 tests.
In both cases all WDIO QUnit Service features are supported. Using spec/test files or configuration only is an option, pick the one you prefer.
The folder openui5-sample-app-no-specs loads QUnit and the tests from an HTML file as described here: https://ui5.sap.com/1.120/#/topic/e1ce1de315994a02bf162f4b3b5a9f09
In this scenario, the configuration only (no spec/test files) is used. Therefore, there's just a new file created in the UI5 project, the configuration file wdio.conf.js itself.
The folder openui5-sample-app loads QUnit and the tests from an HTML file as described here: https://ui5.sap.com/#/topic/e1ce1de315994a02bf162f4b3b5a9f09
In this scenario, spec/test files are used. Three new files are created in the UI5 project, the configuration file wdio.conf.js, the unit.test.js and the opa.test.js.
This method is preferred because it gives more flexibility on which tests should be executed via suites. See the suites unit and opa defined in wdio.conf.js, the unit.test.js. For instance, rather than executing all tests, one could run only unit tests with $ wdio run ./webapp/test/wdio.conf.js --suite unit