The exhausting creation of test scripts, which are also limited to a single browser—it stops right here! With an exciting new approach, tests for APEX applications can be created in no time and are compatible with different browser engines. A look under the hood shows how to use the APEX metadata to create test scenarios which can be executed in multiple browsers with no additional effort. In this session I will show how this is possible and which software stack is necessary.

1. Click, Click, Test -
Automated Tests for APEX
Applications
Kai Donato
Kscope19, Seattle
24th of June 2019
enabling the adaptive enterprise

3. Key Facts
Independent Technology House
with Cross-Industry Expertise
Headquarter
Ratingen
280 employed
Founded
1994
Top Company for Trainees &
Students
Privately-Owned
Corporation
Oracle Platinum
Partner
Microsoft Gold
Partner33 Mio. Euro
Revenue in 2018
Germany‘s No. 1 in
APEX
Branches
Frankfurt & Cologne
3

4. 4
• Employee at MT AG in Ratingen since January 2014
• Senior Consultant for APEX Development
• „That JavaScript Guy“
• DOAG-Initiator – JavaScript and HTML5
• Systems Integrations Specialist
UNIX-Server and Networkadministration
About me
@_KaiDonato
KaiDonato

5. 💡 apex.mt-ag.com 💡

6. 🚀 knowledgebase.mt-ag.com 🚀

7. APEX Visualizer
APEX QA-Plugin
APEX API Generator
APEX Page Generator
XLSX & PPTX Generator
Puppeteer for APEX
MT Tools@apex.mt-ag.com/en/tools

8. bit.ly/apexreleasenotes

9. Click, Click, Test—Automated
Tests for APEX Applications

11. What tools do you use to test?

12. What tools do you use to test?

13. • You need to learn a special kind of syntax to write tests
• Most of the frameworks are made to test a specific browser
• Each and every framwork needs to be installed and configurated on its own
way
Some similarities between existing Frameworks

14. How can we optimize this?
🤩

15. 15
Automatisiertes Testen mit APEX
ManifestAPEX Tool Test-Code RunningPhase
APEX-Items
Master Data
(Login, URL etc.)
Specific test input
Gathering
Meta-Data
Converting to
Test Code
Exectute on
multiple Engines
Logs, Screenshots etc.

17. Step 1
One Framework tests them all!
codecept.io

18. codecept.io
• Puppeteer
• Chrome
• WebDriverIO
• Chrome
• Internet Explorer
• Firefox
• Selenoid (div. Browser in Containern)
• Protractor
• Angular WebApps
• Non-Angular WebApps
• Nightmare
• Chrome (mit Electron)
• Appium
• Mobile Device-Tests
• You need to learn just one Syntax!*
• After the initial creation of your test-scripts you can run tests with multiple engines
• Is ment to be easily written and used as a compatibility layer between test and engine
• Compatible Engines:

19. One Syntax for all the engines!

20. Step 2
Generate reusable tests!

21. • „Code generates Code“
• Templates for predefined test-szenarios in APEX
• Component specific modules (Sign In, Interactive Report, Interactive Grid, …)
• Meta-Data from APEX in JSON as basic manifest
• Bundled in Docker Container and reachable via RESTful service
• Tests can be regenerated when some of the testing modules were changed/updated
handlebars

22. Step 3
Combine Step 1 and Step 2 … 🤔

25. Demo

26. Thank you!Questions?!

29. https://www.linkedin.com/in/kaidonato
https://www.xing.com/profile/Kai_Donato
enabling the adaptive enterprise
Kai Donato
Phone: +49 2102 30961 – 0
kai.donato@mt-ag.com
@_KaiDonato