KEMBAR78
Low-Code Testing Tool | PDF
Low Code Testing for APEX
Kai Donato
28. September 2020
enabling the adaptive enterprise
• 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
codecept.io
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:
One Syntax for all the engines!
• „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
10
Automatisiertes Testen mit APEX
ManifestAPEX Tool Test Code RunningPhase
APEX Items
Master Data
Login URL etc
Specific test input
Gathering
Meta Data
Con erting to
Test Code
E ectute on
multiple Engines
Logs Screenshots etc
Demo

Low-Code Testing Tool

  • 1.
    Low Code Testingfor APEX Kai Donato 28. September 2020 enabling the adaptive enterprise
  • 3.
    • You needto 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
  • 4.
  • 5.
    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:
  • 6.
    One Syntax forall the engines!
  • 7.
    • „Code generatesCode“ • 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
  • 10.
    10 Automatisiertes Testen mitAPEX ManifestAPEX Tool Test Code RunningPhase APEX Items Master Data Login URL etc Specific test input Gathering Meta Data Con erting to Test Code E ectute on multiple Engines Logs Screenshots etc
  • 11.