Test Driven Development in AEM/CQ5

Jun 11, 20144 likes4,061 views

Presentation from RTP AEM / CQ5 Meetup by Sagar Sane. This presentation provides some of the challenges and benefits of applying Test Driven Development principles to Adobe Experience Manager (AEM)/CQ5 based projects and overview of some of the tools and technologies, including Spock & Geb, which can be used for automating test cases & execution.

What’s on the plate?
● What is Test driven development (TDD)?
● Why TDD / BDD?
● CQ backend and Spock testing framework
● Live code

Not on the plate
● Advanced testing techniques
○ Features of Spock Framework
● Much about testing your UI / JS

● Software Consultant II / Tech lead
● WEM Consultant
○ Backend development
○ Comfortable with Java (/JSP) and Groovy
● I don’t dislike front-end development :-)
About me

I became a programmer because of the
‘science’ in programming,
but, I remained a programmer because of the
‘art’ in programming.
I believe..

Some people have very strong opinions about this...

Test Driven Development
● Write Test First (extreme programming)
○ Technical meaning
○ Design your code around the tests
● Write a lot of tests
○ Milder approach

Benefits of Testing
● Find bugs early
● Make it easy for a new person on your
project
○ Read the tests if you don’t understand the code
● Improve code quality

Benefits of Testing
● Helps during code re-factoring
● A good test is worth a thousand comments
● Executable documentation

BDD
● Behavior Driven Development
● Writing tests from the customer’s /
stakeholder’s point of view
● It really is TDD done well!
● More expressive than TDD

//Variables
expected, v1, v2, ..
//Execute feature
actual = System.executeFeature(v1, v2, ..)
//The system gives output as expected
assert actual == expected

CQ/AEM and Spock
● What is Spock Framework? [ link ]
● Why is it awesome? [ link ] [ link ]
○ Is beautiful
● It can be used to test your CQ/AEM
backend!

A basic Spock Feature
//Spock ‘feature’
def "My component should just work"() {
given:
final variables = [ //initial conditions ]
final expected = new MyComponent(...)
when:
final actual = MyComponent.create(variables)
then:
actual == expected
}

Time for some real code...
What ‘new’ will we see?
● Mocks in spock
● setupSpec(), cleanupSpec()
● @Ignore(), @Shared

What all can you do?
● Unit tests for servlets, services
● Integration tests
● Functional tests for your rest APIs
● Even UI tests! (with Geb)

Where to go from here?
● Don’t have to start big
● Add tests to the code that is important,
needs change
● Start new implementations with TDD

This document discusses the perils of using the page object pattern for test automation frameworks. It describes the page object pattern, how it can be used to model pages in code and reduce duplication. However, it also notes limitations like tests becoming too implementation focused rather than intent focused. It then introduces a business layer page object pattern that aims to address these limitations by validating business requirements and separating concerns with abstraction layers. This allows the test pyramid to remain balanced and makes maintenance and scaling easier.

Automated Testing With Jasmine, PhantomJS and JenkinsWork at Play

The document discusses automated testing of JavaScript code using Jasmine, PhantomJS, and Jenkins. It begins with an agenda that covers an introduction to the speakers, testing JavaScript code and front-end code without a browser, and continuous integration. It then discusses Jasmine features for writing tests, using PhantomJS to run tests without a browser, and integrating testing into a continuous integration workflow with Jenkins.

Introduction to Bdd and cucumberNibu Baby

This document provides an introduction to Behavior Driven Development (BDD) with Cucumber. It discusses that BDD uses examples expressed in a way that can be automated to reduce misunderstandings. Stories are written in business language and describe requirements and acceptance criteria. Scenarios specify conditions a story must meet to be complete. Cucumber is a tool that executes plain text functional descriptions as automated tests. It supports collaboration between stakeholders and allows writing scenarios before code.

DevQA: make your testers happier with Groovy, Spock and Geb (Greach 2014)Alvaro Sanchez-Mariscal

The document discusses how a company called Odobo improved their testing process by defining a unified testing framework using Groovy, Spock, and Geb. This allowed both developers and QA engineers to write automated tests in the same framework, eliminating duplicated efforts. Key aspects of the framework included using Gradle for building, Groovy as the programming language, Spock as the testing framework, and Geb for browser automation. It provided benefits like increased code reuse and happier testers across both dev and QA teams.

Cucumber pptQwinix Technologies

Automated testing is important to reduce the time and costs of manual testing. Cucumber is a behavior-driven development framework that allows writing automated acceptance tests in plain language. It executes tests written in its own language called Gherkin. Each Cucumber feature file describes a single feature or scenario using keywords like Feature, Scenario, Given, When, Then. Benefits of Cucumber include involving business stakeholders through human-readable tests, focusing on end-user experience, and easier code reuse and test execution.

Intro to Service Worker API and its use casessatejsahu

The document introduces service workers, which are scripts that run in the background to cache assets and handle requests to provide functionality even when a network is unavailable; it discusses key service worker concepts like promises, registration, installation and activation; and it provides examples of how service workers can be used to improve performance and the offline experience on a web page.

Test Automation Framework with BDD and CucumberRhoynar Software Consulting

This presentation provides an overview of a Test Automation Framework with BDD and Cucumber. It also includes several open-source initiatives that Rhoynar Software Consulting (www.rhoynar.com) has been working on in the fields of QA Automation and DevOps. Lastly, it also includes links to some of the open-source projects that you can use right now for your work. - Continuous Integration Infra a la OpenStack - https://github.com/Rhoynar/ci-infra - An Email Verification Library in Java: https://github.com/Rhoynar/EmailVerify - Automatic Test Generation using Selenium WebDriver, Java and TestNG https://github.com/Rhoynar/AutoTestR - Barebones BDD and Cucumber Framework integrated with Java Maven and TestNG: https://github.com/Rhoynar/qa-automation

Integration Testing in AEMconnectwebex

Polyglot engineeringKlaus Salchner

Getting Started With CypressKnoldus Inc.

This session aims to shed some light on an emerging test automation tool, Cypress. Cypress resolves many of the test automation problems that a QA or a dev may face in UI Web Automation testing. And after a walkthrough, we will compare cypress with Selenium as well. Contact us: Website: https://www.knoldus.com/ Twitter: https://twitter.com/Knolspeak?ref_src... Facbook: https://www.facebook.com/KnoldusSoftw... Linkedin: https://in.linkedin.com/company/knoldus Instagram: https://www.instagram.com/knoldus_inc...

Test Automation With Cucumber JVM, Selenium, and MochaSalesforce Developers

Automated Acceptance Tests & Tool choicetoddbr

The document discusses different layers of automated acceptance testing and compares different toolsets for each layer. The three layers are: 1) Acceptance Criteria Layer which defines test scenarios in a business-readable format, 2) Test Implementation Layer which implements tests against the system under test, and 3) Application Driver Layer which executes tests against the application. Popular tools like Cucumber, Concordion and FitNesse are compared across the layers in terms of their functionality and how each layer is addressed. The document also provides references and suggestions for further exploring related testing concepts.

Cucumber BDDPravin Dsilva

This document provides an introduction to Behavior Driven Development (BDD) and the Cucumber testing framework. It discusses how BDD builds on Test Driven Development (TDD) principles by using examples and a ubiquitous language. Cucumber allows writing acceptance tests in a plain language format called Gherkin that can be executed and serves as documentation. Step definitions translate Gherkin steps into code to automate testing. The document demonstrates setting up a simple Cucumber test in Ruby and discusses expanding it to other programming languages and frameworks.

Bdd – with cucumber and gherkinArati Joshi

BDD with SpecFlow and SeleniumLiraz Shay

BDD (Behavior-driven development), also known as ATDD (Acceptance test–driven development) is a software development process that helps Agile teams design, develop, test and deliver software efficiently, it's about how to implement agile acceptance testing and binding business requirements to code. BDD helps to bridge the communication gap between stakeholders and implementation teams, build quality into software from the start, design, develop and deliver systems fit for purpose. SpecFlow is the official tool to implement BDD on the .NET platform.

Lean Quality & EngineeringMek Srunyu Stittri

The document discusses lean approaches to UI/UX testing including rapid wireframing tools, guerrilla testing, and automated A/B testing to test ideas quickly and cheaply. It then introduces Applitools, a visual automation test tool that can automate visual testing to check for issues like anti-aliasing, brightness, and sub-pixel shifts across browsers, operating systems, and screen resolutions. The document outlines Applitools' workflow for baseline creation and test execution and provides a demo. It notes challenges with visual testing and how Applitools addresses them through specialized image processing.

Test Automation Framework using Cucumber BDD overview (part 1)Mindfire Solutions

Bdd with Cucumber and MochaAtish Narlawar

The document discusses Behavior Driven Development (BDD) and its implementation. It covers BDD topics like the Agile Manifesto, acceptance criteria, Cucumber framework, automation tools like Selenium. It also provides examples of feature files and step definitions in Cucumber. The document advocates that BDD helps align stakeholders, provides executable specifications, and finds defects early through automated tests.

Role of Automation in TestingAnand Bagmar

Automation test framework with cucumber – BDD123abcda

Refactoring page objects The Screenplay Pattern RiverGlide

The document discusses the Screenplay pattern as an alternative to page object models for structuring automated test code. The Screenplay pattern models tests as interactions between actors performing tasks. This improves test code design by separating responsibilities and following SOLID principles. The pattern models the problem domain rather than the technical solution, focusing test code on key user tasks. This makes test code more maintainable, flexible and resilient to changes than traditional page object approaches.

Bulletproof design systems using storybookChen Feldman

The document discusses building and testing design systems using Storybook. It covers how component-driven development (CDD) and design systems help teams collaborate better and build reusable UI components. The presentation emphasizes setting up Storybook with addons to develop and test components, using CSF (Component Story Format) to write testable stories, and automatically generating documentation. Visual, unit and accessibility testing strategies are also covered.

Contributing to open sourceDevin Abbott

What’s new in Visual Studio 2012 & .NET 4.5Robert MacLean

Behavior Driven Testing - A paradigm shiftAspire Systems

HotelQuickly Product & EngineeringMichal Juhas

The document describes a mobile product engineering team that is building a solution for last-minute hotel booking. The team consists of various roles including product designers, Android and iOS developers, backend developers, and QA testers. The engineering practices emphasize agile methodology, continuous integration and deployment, use of best tools and technologies, and data-driven development.

Keeping code cleanBrett Child

One of the main hindrances to teams being able to respond rapidly to new features are technical problems resulting from bad coding practices, also known as technical debt. Melissa and Brett will cover Agile tools and practices that help development teams write better code and increase maintainability. Topics that will be covered include: Pair programming Automated Unit Testing Refactoring Test-Driven Development Agile Architecture

UPC Plone Testing TalkTimo Stollenwerk

The document discusses the benefits of automated testing over manual testing for software development. It notes that manual testing is boring, inefficient, and error-prone, while automated testing makes development more effective and fun by finding errors early, allowing code to be refactored with confidence, and proving that code meets specifications. The document then provides examples of different types of automated tests, such as unit tests, integration tests, and acceptance tests, that can improve the development process.

More Related Content

What's hot (20)

Test Automation Framework with BDD and CucumberRhoynar Software Consulting

Integration Testing in AEMconnectwebex

Polyglot engineeringKlaus Salchner

Getting Started With CypressKnoldus Inc.

Test Automation With Cucumber JVM, Selenium, and MochaSalesforce Developers

Automated Acceptance Tests & Tool choicetoddbr

Cucumber BDDPravin Dsilva

Bdd – with cucumber and gherkinArati Joshi

BDD with SpecFlow and SeleniumLiraz Shay

Lean Quality & EngineeringMek Srunyu Stittri

Test Automation Framework using Cucumber BDD overview (part 1)Mindfire Solutions

Bdd with Cucumber and MochaAtish Narlawar

Role of Automation in TestingAnand Bagmar

Automation test framework with cucumber – BDD123abcda

Refactoring page objects The Screenplay Pattern RiverGlide

Bulletproof design systems using storybookChen Feldman

Contributing to open sourceDevin Abbott

What’s new in Visual Studio 2012 & .NET 4.5Robert MacLean

Behavior Driven Testing - A paradigm shiftAspire Systems

HotelQuickly Product & EngineeringMichal Juhas

Test Automation Framework with BDD and CucumberRhoynar Software Consulting

Integration Testing in AEMconnectwebex

Polyglot engineeringKlaus Salchner

Getting Started With CypressKnoldus Inc.

Test Automation With Cucumber JVM, Selenium, and MochaSalesforce Developers

Automated Acceptance Tests & Tool choicetoddbr

Cucumber BDDPravin Dsilva

Bdd – with cucumber and gherkinArati Joshi

BDD with SpecFlow and SeleniumLiraz Shay

Lean Quality & EngineeringMek Srunyu Stittri

Test Automation Framework using Cucumber BDD overview (part 1)Mindfire Solutions

Bdd with Cucumber and MochaAtish Narlawar

Role of Automation in TestingAnand Bagmar

Automation test framework with cucumber – BDD123abcda

Refactoring page objects The Screenplay Pattern RiverGlide

Bulletproof design systems using storybookChen Feldman

Contributing to open sourceDevin Abbott

What’s new in Visual Studio 2012 & .NET 4.5Robert MacLean

Behavior Driven Testing - A paradigm shiftAspire Systems

HotelQuickly Product & EngineeringMichal Juhas

Similar to Test Driven Development in AEM/CQ5 (20)

Keeping code cleanBrett Child

UPC Plone Testing TalkTimo Stollenwerk

Effective TDD - Less is moreBen Lau

The document discusses techniques for making test-driven development (TDD) more enjoyable. It provides examples of conversations where a programmer asks if they can have quality assurance write tests, and whether tests are needed if code is working. The creator of TDD notes that tests should be written to reach a high level of confidence, not just to print "OK". Several rationalizations for not writing tests are debunked. The document advocates designing programs by writing tests first, and making initial tests fail on purpose in order to have the short-term goal of fixing them. This focuses effort and makes the process more fun. Less testing is needed than achieving 100% coverage; tests should be written when most useful, such as for new code

Tdd is not about testing (C++ version)Gianluca Padovani

Reliable mobile test automationVishal Banthia

This document summarizes Vishal Banthia's presentation on achieving reliable mobile test automation. It discusses the difficulties of flaky tests and inconsistent test execution environments. It then presents solutions like capturing comprehensive test reports with screenshots, videos, and logs to better diagnose flaky tests. It also recommends leveraging cloud services for scalable and accessible test execution. The presentation demonstrates these concepts through tools like Bitrise, OpenSTF, and CircleCI used in Mercari's mobile test automation pipeline.

Test Driven Development with PHPRogério Vicente

This document discusses test-driven development (TDD) and unit testing. It begins with an introduction to TDD and examples using PHPUnit. It then explores the TDD cycle, common excuses for not using TDD, and pros and cons of TDD. Next, it distinguishes unit testing from TDD and discusses unit testing frameworks like PHPUnit and SimpleTest. Finally, it provides examples of code for a simple game that could be used to learn TDD and unit testing techniques.

Unit Testing and TDD 2017Xavi Hidalgo

May 2021 Spark Testing ... or how to farm reputation on StackOverflowAdam Doyle

Software Testing Basic Conceptswesovi

The document discusses testing concepts such as code with tests vs without tests, test-oriented development, and different types of testing including unit testing, integration testing, and acceptance testing. It provides examples of test-driven development (TDD) and behavior-driven development (BDD) processes. The document also discusses tips for testing, including only testing what is necessary and identifying the appropriate types of testing for an application. Frameworks and tools for test automation and continuous integration are also mentioned.

Spock preselizhender

Spock is a Groovy-based testing framework that supports behavior-driven development (BDD). It allows writing tests as executable specifications using a Given-When-Then syntax. Spock specifications extend Specification and contain feature methods that define test scenarios. Spock has built-in support for mocking, data-driven testing, and integrating with frameworks like Geb and Spring. It aims to make testing more natural, concise, and powerful compared to traditional testing frameworks.

TDD in Go with Ginkgo and GomegaEddy Reyes

How to establish ways of working that allows shifting-left of the automation ...Max Barrass

Why Automate? Your application will grow, you will not have enough hands You are blocked by development Hidden factory costs of bug-fix cycle Why Shift-Left? More people to negate massive inspections Define measurable success early, work on good parts. Reduce occurrence of defects What is this got to do with Ways of working? Unlock capacity Make people smile Is not a Department extra cost a final oversight or a massive inspection someone else’s job Is Everyone’s responsibility Build into the ways of working Everyone’s job

Test driven development_continuous_integrationhaochenglee

This document discusses test-driven development (TDD) and continuous integration (CI). It explains that TDD involves writing tests before code to drive the design. The key steps of TDD are design, test, implement, and test again. CI involves integrating code changes frequently, usually daily, to catch errors early. TDD and CI work well together as the tests from TDD can be run automatically through CI to provide rapid feedback. The document provides an overview of how to implement TDD and CI using tools like Jenkins.

Test-Driven Development.pptxTomas561914

This document provides an overview of test-driven development (TDD). It defines TDD as a technique for building software by writing tests first before production code. The key aspects of TDD covered include the three laws of TDD, why it is used, the typical TDD process through an LED example, research on its effectiveness, designing code for testability, and best practices. Overall, TDD aims to increase code quality and catch errors early through writing automated tests before code, but requires effort and experience to apply effectively.

Test and Behaviour Driven Development (TDD/BDD)Lars Thorup

Getting started with karate dslKnoldus Inc.

Test driven development - Zombie proof your codePascal Larocque

This document discusses test driven development and how to write testable code. It recommends writing tests before writing code to prevent "zombie code" that is hard to maintain and change. Specific tips provided include using dependency injection, following SOLID principles to separate concerns, and writing fast, isolated tests using tools like PHPUnit and PHPSpec. Continuous integration is also recommended to prevent technical debt from accumulating.

Testing of React JS appAleks Zinevych

This document discusses testing React JS applications with tools like Mocha, Enzyme, and Webdriver.io. It covers why writing tests is important, provides examples of unit testing React components with Enzyme, and discusses how to do functional and integration testing with Webdriver.io. The document demonstrates testing architectures, common testing patterns like page objects, and concludes that frontend tests are important and not too costly to implement.

Writing Tests with the Unity Test FrameworkPeter Kofler

Getting started with unit and functional testingAdewale Andrade

This document discusses the importance of testing code and different types of tests. It covers unit tests, integration tests, and end-to-end tests, explaining what each tests and providing examples. It also discusses best practices for writing good unit and integration tests, including testing behavior not implementation, avoiding dependencies, and using mocking and dependency injection. The goal is to establish a culture of testing code to ensure quality and prevent bugs.

Keeping code cleanBrett Child

UPC Plone Testing TalkTimo Stollenwerk

Effective TDD - Less is moreBen Lau

Tdd is not about testing (C++ version)Gianluca Padovani

Reliable mobile test automationVishal Banthia

Test Driven Development with PHPRogério Vicente

Unit Testing and TDD 2017Xavi Hidalgo

May 2021 Spark Testing ... or how to farm reputation on StackOverflowAdam Doyle

Software Testing Basic Conceptswesovi

Spock preselizhender

TDD in Go with Ginkgo and GomegaEddy Reyes

How to establish ways of working that allows shifting-left of the automation ...Max Barrass

Test driven development_continuous_integrationhaochenglee

Test-Driven Development.pptxTomas561914

Test and Behaviour Driven Development (TDD/BDD)Lars Thorup

Getting started with karate dslKnoldus Inc.

Test driven development - Zombie proof your codePascal Larocque

Testing of React JS appAleks Zinevych

Writing Tests with the Unity Test FrameworkPeter Kofler

Getting started with unit and functional testingAdewale Andrade

Recently uploaded (20)

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Procurement Insights Cost To Value Guide.pptxJon Hansen

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including: -Artificial Intelligence Market Overview -Strategies for AI Adoption in 2025 -Anticipated drivers of AI adoption and transformative technologies -Benefits of AI and Big data for your business -Tips on how to prepare your business for innovation -AI and data privacy: Strategies for securing data privacy in AI models, etc. Download your free copy nowand implement the key findings to improve your business.

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots. 📕 Here's what you can expect: - Modeling: Build end-to-end processes using BPMN. - Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes. - Operating: Control process instances with rewind, replay, pause, and stop functions. - Monitoring: Use dashboards and embedded analytics for real-time insights into process instances. This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes. 👨‍🏫 Speaker: Andrei Vintila, Principal Product Manager @UiPath This session streamed live on April 29, 2025, 16:00 CET. Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Build Your Own Copilot & Agents For DevsBrian McKeiver

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp

HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda

Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/ HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar. Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten. In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich - Zugriff auf die Konsole - Auffinden und Interpretieren von Protokolldateien - Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS) - Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien - Nutzung der Client Clocking-Funktion

How analogue intelligence complements AIPaul Rowe

Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results. News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

Want to learn practical tips for designing systems that can scale efficiently without compromising speed? Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development. As you explore key principles of designing low-latency systems with Rust, you will learn how to: - Create and compile a real-world app with Rust - Connect the application to ScyllaDB (NoSQL data store) - Negotiate tradeoffs related to data modeling and querying - Manage and monitor the database for consistently low latencies

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts! 📕 Agenda Welcome & Introductions Orchestrator API Overview Exploring the Swagger Interface Test Manager API Highlights Streamlining Automation & Testing with APIs (Demo) Q&A and Open Discussion Perfect for developers, testers, and automation enthusiasts! 👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/ This session streamed live on April 29, 2025, 18:00 CET. Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.

AI and Data Privacy in 2025: Global TrendsInData Labs

In this infographic, we explore how businesses can implement effective governance frameworks to address AI data privacy. Understanding it is crucial for developing effective strategies that ensure compliance, safeguard customer trust, and leverage AI responsibly. Equip yourself with insights that can drive informed decision-making and position your organization for success in the future of data privacy. This infographic contains: -AI and data privacy: Key findings -Statistics on AI data privacy in the today’s world -Tips on how to overcome data privacy challenges -Benefits of AI data security investments. Keep up-to-date on how AI is reshaping privacy standards and what this entails for both individuals and organizations.

tecnologias de las primeras civilizaciones.pdffjgm517

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency. This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data. Attendees will learn: - Consumer awareness around data brokers and what consumers are doing to limit data collection - How businesses assess third-party vendors and their consent management operations - Where business preparedness needs improvement - What these trends mean for the future of privacy governance and public trust This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.

Cyber Awareness overview for 2025 month of securityriccardosl1

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Procurement Insights Cost To Value Guide.pptxJon Hansen

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Build Your Own Copilot & Agents For DevsBrian McKeiver

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp

HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda

How analogue intelligence complements AIPaul Rowe

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

AI and Data Privacy in 2025: Global TrendsInData Labs

tecnologias de las primeras civilizaciones.pdffjgm517

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Cyber Awareness overview for 2025 month of securityriccardosl1

Test Driven Development in AEM/CQ5

1. TDD in CQ5/AEM Sagar Sane

2. What’s on the plate? ● What is Test driven development (TDD)? ● Why TDD / BDD? ● CQ backend and Spock testing framework ● Live code

3. Not on the plate ● Advanced testing techniques ○ Features of Spock Framework ● Much about testing your UI / JS

4. ● Software Consultant II / Tech lead ● WEM Consultant ○ Backend development ○ Comfortable with Java (/JSP) and Groovy ● I don’t dislike front-end development :-) About me

5. I became a programmer because of the ‘science’ in programming, but, I remained a programmer because of the ‘art’ in programming. I believe..

6. Some people have very strong opinions about this...

7. No, REALLY!

8. Test Driven Development ● Write Test First (extreme programming) ○ Technical meaning ○ Design your code around the tests ● Write a lot of tests ○ Milder approach

9. What is a Unit Test in CQ/AEM?

10. Benefits of Testing ● Find bugs early ● Make it easy for a new person on your project ○ Read the tests if you don’t understand the code ● Improve code quality

11. Benefits of Testing ● Helps during code re-factoring ● A good test is worth a thousand comments ● Executable documentation

12. BDD ● Behavior Driven Development ● Writing tests from the customer’s / stakeholder’s point of view ● It really is TDD done well! ● More expressive than TDD

13. //Variables expected, v1, v2, .. //Execute feature actual = System.executeFeature(v1, v2, ..) //The system gives output as expected assert actual == expected

15. CQ/AEM and Spock ● What is Spock Framework? [ link ] ● Why is it awesome? [ link ] [ link ] ○ Is beautiful ● It can be used to test your CQ/AEM backend!

16. A basic Spock Feature //Spock ‘feature’ def "My component should just work"() { given: final variables = [ //initial conditions ] final expected = new MyComponent(...) when: final actual = MyComponent.create(variables) then: actual == expected }

17. Time for some real code... What ‘new’ will we see? ● Mocks in spock ● setupSpec(), cleanupSpec() ● @Ignore(), @Shared

18. What all can you do? ● Unit tests for servlets, services ● Integration tests ● Functional tests for your rest APIs ● Even UI tests! (with Geb)

19. What all can you do? Test Automation

20. Where to go from here? ● Don’t have to start big ● Add tests to the code that is important, needs change ● Start new implementations with TDD

21. The art of programming!

22. Thank you!

Test Driven Development in AEM/CQ5

Recommended

More Related Content

What's hot (20)

Similar to Test Driven Development in AEM/CQ5 (20)

Recently uploaded (20)

Test Driven Development in AEM/CQ5