DevOps World | Jenkins World 2019 San Francisco

In any mature Agile or DevOps implementation, there are various testing activities triggered by both developers and testers. In most cases, developers will trigger a Jenkins job per each code change to perform a sanity test for their new feature or recent defect fix. In other use cases, test engineers and business testers schedule via Jenkins their complete sanity or regression testing for their apps (mobile, web, both). In today’s reality, such jobs trigger a mix of test automation tasks. Some are using code-based test frameworks, like Selenium and Appium, but some uses codeless AI-driven test scripts. In this session, Eran Kinsbruner, Chief evangelist and author at Perfecto, will explain how these two testing types vary, and why there is a significant importance in visualizing both in a single dashboard. Join the session to learn: - What are the benefits of business testers and developers embracing codeless test automation? - What are the recommended tests to trigger CI using code vs. codeless? - How can both test types be connected into a single CI dashboard?