Slide 1

Slide 1 text

© 2024 CGI Inc. 1 Code or Low- Code Navigating the test automation options Maaret Pyhäjärvi November 2024

Slide 2

Slide 2 text

© 2024 CGI Inc. 2 Hyperautomation – automating everything that can be automated Shared tools Open source prevents licenses from becoming limitation Opportunity cost Time used on warning about test automation is time away from succeeding with it Continuity Executable documentation worth having, when I am gone Explore to build Shift left and shift down, combine into contemporary exploratory testing Collecting key points from years with projects of various states of test automation. 01 03 02 04

Slide 3

Slide 3 text

© 2024 CGI Inc. 3 3 Programming language = system of notation for writing computer programs Low code / No code = using intuitive drag-and-drop tools that reduce need for traditional developers

Slide 4

Slide 4 text

© 2024 CGI Inc. 4 Agenda for learning 1 Differences in learning Code and Low code 2 Minimal knowledge for useful contributions Learning in layers 3 Writing and reading Reading on failures NEW

Slide 5

Slide 5 text

© 2024 CGI Inc. 5 Differences in learning Code and low code 5

Slide 6

Slide 6 text

© 2024 CGI Inc. 6 Polyglot and polytool is a lot of work 6

Slide 7

Slide 7 text

© 2024 CGI Inc. 7 7 Photo by Clay Banks on Unsplash Can’t you just tell us which one to use? Anti-toolist worldwiew Realize that features in tools can be copied. Looking for the one best tool makes little sense. We need to protect our time to a partner of choice. 02

Slide 8

Slide 8 text

© 2024 CGI Inc. 8 With code 8

Slide 9

Slide 9 text

© 2024 CGI Inc. 9 9

Slide 10

Slide 10 text

© 2024 CGI Inc. 10 10

Slide 11

Slide 11 text

© 2024 CGI Inc. 11 11

Slide 12

Slide 12 text

© 2024 CGI Inc. 12 12

Slide 13

Slide 13 text

© 2024 CGI Inc. 13 13

Slide 14

Slide 14 text

© 2024 CGI Inc. 14 14

Slide 15

Slide 15 text

© 2024 CGI Inc. 15 Minimal knowledge for useful contribution Learning in layers 15

Slide 16

Slide 16 text

© 2024 CGI Inc. 16 For test automation, you choose a language Tradeoffs • Visual / Robot Framework / Gherkin / TypeScript / Python / Java / C# / … • Enable ownership over time when people change positions • Granularity: feedback to where things got broken • Reuse and integrations Usual choice: automation in the language of the implementation.

Slide 17

Slide 17 text

© 2024 CGI Inc. 17 It’s not just the language / tools 03 02 01 04 Tools Language + Libraries. CI/CD pipeline. Test warehouse of results. Environments Conceptual home for where tests run, with needs different for automation. Test Data Business systems, business data. Varying degrees of logic impact and complexity. Long flow knowledge Multiple business expert to test real end to end flow. Analyze and enhance tests It’s a system you react to. Fix and adjust. Enhance with functionality.

Slide 18

Slide 18 text

© 2024 CGI Inc. 18 Learning in Layers Hello World to Proof of Value Learning enough to operate. Installing and upgrading Change with new people and new versions. Integrations Automation belongs to pipeline. Results belong to warehouse. Knowledge beyond syntax Locators and semantic HTML. Object-oriented programming. Property- based testing. Model-based testing.

Slide 19

Slide 19 text

© 2024 CGI Inc. 19 Writing and reading Reading on failures 19

Slide 20

Slide 20 text

© 2024 CGI Inc. 20 Failing automation is invitation to explore 20 Photo by Jon Tyson on Unsplash

Slide 21

Slide 21 text

© 2024 CGI Inc. 21 After AI-enabled automation of 80% of the work, the 20% that remains is the portion that requires skills 21 Photo by Austin Distel on Unsplash

Slide 22

Slide 22 text

© 2024 CGI Inc. 22 Looking inside the box …or building up the box so that we know what the box contains? 22

Slide 23

Slide 23 text

© 2024 CGI Inc. 23 Key insights Whole team ownership Sharing tests with developers is essential. “The 10 years of success turned into failure within a month after the creator left” Incremental strategy One reliable test already running is better than plans. “The plan for what to automate was obsolete after automating the first scenario" Design for automation Decomposing feedback for automation. “We have 5000 tests and half of them are failing. Can you recommend AI that fixes them?”

Slide 24

Slide 24 text

© 2024 CGI Inc. 24 Test automation gives us more than regression Specification Examples shared before implementation act as specification. Feedback We know when it works as we’re implementing the progress. Regression We safeguard our past intent over lifetime of system ownership. Granularity We know when and what changed without extensive analysis. Documenting Capture examples whenever we discuss them. Extending reach Time. Environments. Data. Alerting to attend Changes, both intended and unintended. Guiding to detail Drives attention to details humans do repair for.

Slide 25

Slide 25 text

© 2024 CGI Inc. 25 Insights you can act on Founded in 1976, CGI is among the largest IT and business consulting services firms in the world. We are insights-driven and outcomes-based to help accelerate returns on your investments. Across hundreds of locations worldwide, we provide comprehensive, scalable and sustainable IT and business consulting services that are informed globally and delivered locally. cgi.com