OpenUI5 modified sample app to demonstrate UI5 testing concepts
- copied from openui5-sample-app
- Uses OData Model to manipulate todo items
- Relies on MockServer to simulate backend
- Fully tested with OPA
"If it's not tested, it doesn't work." UI5 includes a testing framework that gives developers the power to assess their code by automating the UI and simulating the back-end. In this presentation, a complete example of test automation will be given, illustrating the best practices when using waitFor, simulating back-end APIs and providing keys to handle complex scenario (such as data generation, error simulation...).
- The UI5 CLI of the UI5 Build and Development Tooling.
- For installation instructions please see: Installing the UI5 CLI.
-
Install Node.js (from nodejs.org).
-
Clone the repository and navigate into it
git clone https://github.com/ArnaudBuchholz/training-ui5con18-opa.git cd training-ui5con18-opa -
Install all npm dependencies you might need to have administrator rights
npm install
-
Start a local server and run the application (http://localhost:8080/index.html)
npm start
Run npm run serve to start a local server with your application at http://localhost:8080.
Run npm run watch to also execute your unit tests automatically after every change.
Run npm run lint to run static code checks on your project.
Run npm test to execute all tests and get a coverage report.
Run npm run serve and open http://localhost:8080/test/integration/opaTests.qunit.html to run the OPA tests in your browser.
Run npm build to build a deployable version of your app to /dist.
Despite the 100% coverage, there are still issues in the application:
- In the dialog, the date/time pickers could be bound to an invalid property, no test will fail
- In the dialog, the "Due date" date/time picker is not validated. If one enters an invalid date, no error is shown. Worse, the dialog is not refreshed properly when re-opened.
- In the dialog, when the server throws an error, the dialog is closed. But it would be better to keep the dialog opened to allow the user to change the value. For instance: what if the backend rejects empty titles?