What is Agile Testing?

•

4 gostaram•1,600 visualizações

Dr. Alexander Schwartz

A Lightning Talk presented on an internal unconference at HERE (a Nokia business) in Berlin.

Tecnologia Educação

What is Agile Testing?
Alex Schwartz, HERE Berlin

Agile Testing is…
I found a
conference for
Agile Testing!

me

colleague

Agile Testing is…
I found a
conference for
Agile Testing!

me

Why?
Agile Testing is nonsense!

colleague

Agile Testing is… nonsense
I found a
conference for
Agile Testing!

me

Why?
Agile Testing is nonsense!

colleague

Agile Testing is…
- Testing in the context of
Agile Development

Agile Testing is…
- Testing in the context of
Agile Development
- often one of the harder challenges
during an Agile Transition

What is special about Agile Testing?
1.

When?

What is special about Agile Testing?
1.

2.

When?

Who?

What is special about Agile Testing?
1.

2.

When?

3.

Who?

How?
What?

When?
Late testing approach
Design
Planning

Release

Dev
Test /
Hardening

When?
Late testing approach
Design
Planning

risk for schedule
Release

Dev
Test /
Hardening

When?
When we have good quality?
Late testing approach
Design
Planning

risk for schedule
Release

Dev
Test /
Hardening

When?
When we have good quality?
Late testing approach
Design
Planning

Quality
Level

risk for schedule
Release

Dev
Test /
Hardening

time

When?
When we have good quality?
Late testing approach
Design
Planning

Release

Dev

Quality
Level

risk for schedule

Test /
Hardening

Quality/Verification Debt

time

When?
When to test & to fix?

Design
Planning

Release

Dev
Test /
Hardening

When?
When to test & to fix?
Scale
Design
Planning

Release

Dev
Test /
Hardening

When?
When to test & to fix?
Scale
Design
Planning

Earlier

•
•
•
•
•

Release

Dev
Test /
Hardening

TDD/ATDD
Continuous Integration
Requirements discussions
Early Feedback
…

When?
When to test & to fix?
Scale
Design
Planning

measure, observe, …

Release

Dev

Earlier

•
•
•
•
•

Learn from production

Test /
Hardening

TDD/ATDD
Continuous Integration
Requirements discussions
Early Feedback
…

Don’t do

Are all your tests helpful?

Asynchronous activities
•
•

e.g. quarterly security tests
…

When?
When we have good quality?
Late vs. early testing approach
Design
Planning

Release

Dev

Quality
Level

Test /
Hardening

early testing
late testing

time

Who?

Testing
Test

QA/Tester

Automation
Verifying
Requirements

Who?

All of us.
Testing
Test

QA/Tester

Automation
Verifying
Requirements

Who?

All of us.
Testing
Test

QA/Tester

Automation
Verifying
Requirements

QA = consultant for quality

What?
What is quality?

Source:
Gojko Adzic

correct, functional

What?
What is quality?

performant, etc.
Source:
Gojko Adzic

correct, functional

What?
What is quality?
useful
usable

performant, etc.
Source:
Gojko Adzic

correct, functional

What?
What is quality?

successful

useful
usable

performant, etc.
Source:
Gojko Adzic

correct, functional

Agile Testing is… natural

Agile = Testing

Agile Testing is… natural

Agile = Testing

all the time.

Agile Testing is… natural

Agile = Testing

all the time.
all of us.

Mais conteúdo relacionado

Mais procurados

Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum. The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.

Agile testing principles and practices - Anil Karade

IndicThreads

Software Testing with Agile Requirements Practices

A B M Moniruzzaman

Introducing QA Into an Agile Environment

Joseph Beale

Agile Testing by Example

Mikalai Alimenkou

Introduction to Agile Testing

vodQA

Agile tester 3.0

Daniel Amorim

Guide to Agile testing

Subrahmaniam S.R.V

Until now there have been two camps for Application Quality Management (AQM) systems. Traditional Tools like HP QC that have proved inflexible for agile developments and maintenance heavy, or new agile tools from Version One or Rally Software, which are agile specific tools and not suitable for use outside agile environments or corporate-wide where teams are using a mix of processes. With many organisations moving to or experimenting with Agile, Original Software has been acclaimed by the analyst community as the best solution for supporting Agile. [Original Software nominated Agile Best Tool Award] Just as improvements in developer's software tools and methods have enabled a shift in development approaches, next generation technology for test automation is similarly reframing the opportunities for testers to automate earlier in the delivery cycle without incurring the heavy burden of script maintenance so often associated with traditional automation tools. This means that not only can an agile environment be adopted, application quality is maintained and the total testing time reduced. - See more at: http://www.origsoft.com/solutions/agile-software-testing/

Optimising Quality Assurance in an Agile World

Original Software

ISTQB agile tester exam - Conclusions about Certification

Michał Dudziak

Presentation on Agile Testing

1Solutions Pvt. Ltd.

Agile Testing: The Role Of The Agile Tester

Declan Whelan

Scrum Testing Methodology

Gaya1985

Slides from a session presented by Fadi Stephan from Kaizenko at the 2019 Global Scrum Gathering in Austin, TX on 05/20/2019 DC. Also see the blog series on Agile Testing at https://www.kaizenko.com/agile-testing/ Abstract: Many teams struggle with fitting in testing activities inside of a Sprint. They end up doing primarily development activities in a Sprint and push testing activities to run in dedicated testing Sprints following the coding Sprints or have a coding and testing Sprint running in parallel. However, in Scrum, the output of every Sprint is a potentially shippable product increment. This means the product increment should be well tested within the Sprint and ready to be delivered. Come to this presentation to learn how to tackle testing on an Agile team, what kind of tests to execute, what to automate and what not to automate, the different test responsibilities, and when to run which tests. Leave with a testing strategy that you can start applying the next day to gradually get a team to start testing from day 1 of the Sprint and deliver a true product increment at the end of each Sprint.

Agile testing - Testing From Day 1

Kaizenko

Introduction to Agile Testing

Raymond Adrian (Rad) Butalid

A Concise QA Process

Arslan Ali

Agile Testing – embedding testing into agile software development lifecycle

Kari Kakkonen

Agile Testing Process

Intetics

Agile testing presentation

Komal Garg

Role Of Qa And Testing In Agile 1225221397167302 8

a34sharm

Agile Testing Strategy

tharindakasun

Mais procurados (20)

Agile testing principles and practices - Anil Karade

Software Testing with Agile Requirements Practices

Introducing QA Into an Agile Environment

Agile Testing by Example

Introduction to Agile Testing

Agile tester 3.0

Guide to Agile testing

Optimising Quality Assurance in an Agile World

ISTQB agile tester exam - Conclusions about Certification

Presentation on Agile Testing

Agile Testing: The Role Of The Agile Tester

Scrum Testing Methodology

Agile testing - Testing From Day 1

Introduction to Agile Testing

A Concise QA Process

Agile Testing – embedding testing into agile software development lifecycle

Agile Testing Process

Agile testing presentation

Role Of Qa And Testing In Agile 1225221397167302 8

Agile Testing Strategy

Semelhante a What is Agile Testing?

Agile test

Ma Xuebin

No such thing called agile testing

Shrinivas Kulkarni

Agile has flipped the traditional software development lifecycle on its head. For the QA specialist, the waterfall-driven "testing stage"—where testers execute a pre-defined set of tests within a pre-defined timeline—has been redistributed and re-framed within Agile. I would even say it's been reborn. Topics: Is Agile changing the quality game? How are QA thought leaders attempting to redefine our space? What are some tips/tricks/mindmaps I can use to do QA right on an agile team?

Agile QA: Redefining Quality in the Wild West

Ford Prior

Agile in Action - Agile Overview for Developers

Matt Cowell

Agile testing

tanvir afzal

Iakiv Kramarenko: “Quality Driven Development”

Dakiry

Test Improvement is all about giving an organization or a team the “means they can use” to help achieve their goals. Means that are in line with their skills and they can use in their context. That’s why successful Test Improvement requires leadership and management. In this presentation I share experiences in Test Improvement in a wide variety of environments, using different models and approaches.

Test Improvement - Any place, anytime, any where

Ruud Teunissen

2015 06-03 ti4 agile presented at ncs

Ruud Teunissen

TDD in Agile

Atish Narlawar

Continuous delivery is more than dev ops

Agile Montréal

Agile Mëtteg #5: Agile Testing

Agile Partner S.A.

Testing and DevOps Culture: Lessons Learned

LB Denker

Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya...

Scrum Bangalore

SDLC & DevSecOps

Irina Kostina

Software testing with examples in Angular (and AngularJS)

Paweł Żurowski

Design is a process, not a Document

Trisha Gee

Scrum best practices

Shuchi Singla AKT,SPC4,PMI-ACP,ITIL(F),CP-AAT

The Patterns to boost your time to market - An introduction to DevOps

Brice Argenson

The patterns to boost your time to-market

CleverToday

Testing in agile

KYarli

Semelhante a What is Agile Testing? (20)

Agile test

No such thing called agile testing

Agile QA: Redefining Quality in the Wild West

Agile in Action - Agile Overview for Developers

Agile testing

Iakiv Kramarenko: “Quality Driven Development”

Test Improvement - Any place, anytime, any where

2015 06-03 ti4 agile presented at ncs

TDD in Agile

Continuous delivery is more than dev ops

Agile Mëtteg #5: Agile Testing

Testing and DevOps Culture: Lessons Learned

Scrum_BLR 11th meet up 13 dec-2014 - SDET - They Way to go for Testers - Jaya...

SDLC & DevSecOps

Software testing with examples in Angular (and AngularJS)

Design is a process, not a Document

Scrum best practices

The Patterns to boost your time to market - An introduction to DevOps

The patterns to boost your time to-market

Testing in agile

Mais de Dr. Alexander Schwartz

Talk for the Agile Testing Days 2023. Mel Conway published in 1968 the observation that the communication structure of a company has an impact on the architecture of the produced software components. Nowadays many organizations use the “feature team approach”, that is, a preference for cross-functional teams which deliver value without depending on other teams. An implication is that several feature teams are going to work on the same components, which implies that the traditional concepts of strong component ownership are no longer applicable. This generates a myriad of challenges, e.g. teams waiting for code review from other teams. In this talk we first revisit Conway’s Law and then explore what is required to ensure success of feature teams working on shared components. First and foremost, does the architecture, the processes, etc. really support the requirement of ease of changing a shared component?

Wrestling with Conway's Law: How to support cross-functional teams working on...

Dr. Alexander Schwartz

Talk presented at the Agile Tour Vienna 2016 conference. http://agiletourvienna.at/#scheduleModal-does-agile-mean-we-have-less-time-for-testing ABSTRACT: In the last decade, the speed of our industry has increased greatly. Agile Development, DevOps and Continuous Delivery are the main drivers for this paradigm shift which has now become widely accepted. Ten years ago, it was common to only release a couple of new versions a year. Today, there are companies delivering hundreds of software deployments per day. This isn’t only true in IT, but also e.g. for Tesla-Automobile, which delivers its software updates a few times a week. Where does quality happen when we’re releasing this often? Is it possible to have proper quality management and is there enough time for testing? How can we reduce what could be weeks of testing to deliver new features to our clients on a daily basis? Alex is a long-term enthusiast for this topic. Based on his experiences with various products and companies, he’ll share his insights into the mystery of “faster testing”. The key questions are: - When – When do we test? - What – What should we test? - Which quality aspects are important? - How – How do we test? Which techniques are helpful? - Who – Who is involved in testing, test automation, etc.? - How much – How much should we test? Furthermore, we discuss the financial benefits of Agile Testing and aiming for Continuous Quality. Last but not least we explore if it only exists in fairy tale land or if it is real.

#AT16VIE: Does Agile mean we have no time for testing?

Dr. Alexander Schwartz

Talk provided at ASQF meetup "Fachgruppentreffen" in Braunschweig, 18th August 2016 In the last decade, the speed of our industry has increased greatly. Agile Development, DevOps and Continuous Delivery are the main drivers for this paradigm shift which has now become widely accepted. Ten years ago, it was common to only release a couple of new versions a year. Today, there are companies delivering hundreds of software deployments per day. This isn't only true in IT, but also e.g. for Tesla-Automobile, which delivers its software updates a few times a week. Where does quality happen when we're releasing this often? Is it possible to have proper quality management and is there enough time for testing? How can we reduce what could be weeks of testing to deliver new features to our clients on a daily basis? Alex is a long-term enthusiast for this topic. Based on his experiences with various products and companies, he'll share his insights into the mystery of "faster testing". The key questions are: How can we guarantee quality When do we test? How do we test? How often do we test and what don't we test? and finallyt: Who does the testing? Together we will discuss our common problems, approaches and best practices.

Does agile mean having even less time for testing?!

Dr. Alexander Schwartz

User Stories Schneiden mit Elefanten-Carpaccio (Scrum-Day 2016)

Dr. Alexander Schwartz

Hilfe, wir haben keine Zeit zum Testen!

Dr. Alexander Schwartz

Slides of a workshop facilitated by Fanny Pittack and Alex Schwartz at the conference Agile Testing Days 2015 in Potsdam. Main Statement: Change dojos are creating a safe environment for practicing skills for change agents. It sets fundamentals for you and allow you to perform change. This workshop is for everyone who is involved in improving his or her environment. As the ATD 2015 conference theme states, mastering Agile might be the competitive edge for your organization – and this requires great skills to transform your environment, to change it towards the goal of Agile mastery.In our last years keynote “Insights of Happy Change Agents” we scratched the surface of how to become a “Happy Change Agent”, how to initiate changes with ease and enthusiasm, fun and success. In this workshop we aim to dive deeper.The first part of our workshop is dedicated to the “change dojo” format. Together with your pairing partner you simulate the interaction of a change agent with a team or coachee. We practice different scenarios and we will focus step by step on various aspects like pace, distance, keeping your own space, as well as communicating clearly with your body. This provides a chance to receive instant feedback how the change is perceived by the coachee. One key learning is to appreciate any sign of frustration as a valuable indicator.The second part is intended to storytelling and listening exercises. We all have buried a story of change that somehow failed. If you attend our workshop, please bring your story with you. Key Learnings: - Exercises to bring back to your workplace, to practice with your team - How to be open for feedback and listen - How to sketch your story on a story board - How to use your frustration as indicator - How to reflect in various situations Audience: Tester, Developer, Product Owner, Scrum Master, Agile Manager, Change Agents, Agile Coach

Change Dojo - Agile Testing Days 2015

Dr. Alexander Schwartz

slides of a workshop (in German) facilitated at the ScrumDay 2015 (http://www.scrum-day.de/) in Stuttgart. Lanyrd: http://lanyrd.com/2015/scrum-day/sdpmgb/ Abstract: Coding Dojos sind sehr bekannt und sind nun ein anerkanntes Hilfsmittel um Wissen zu vermitteln und unser Kung-Fu zu verbessern. Warum dieses Format, diese Lernmethode nicht auch für andere Themen verwenden? In diesem Dojo fokussieren wir uns auf User Stories: ihre Akzeptanzkriterien und wie wir grosse Stories in kleinere zerschneiden können. In Gruppenübungen werden wir unser Kung-Fu verbessern. Vielleicht wird Deine Gruppe auf Yoda-Niveau erreichen: alle Mini-Stories haben einen Wert und sind MMFs (minimal markatable features) im Sinne des Lean Startup?

ScrumDay2015: Ein neues Dojo: Anwendergeschichten zerschneiden

Dr. Alexander Schwartz

Insights From Happy Change Agents

Dr. Alexander Schwartz

Ein neues Dojo: Anwendergeschichten zerschneiden

Dr. Alexander Schwartz

A New Dojo: The Art of Story Splitting

Dr. Alexander Schwartz

DevOps in the Enterprise: Our Experiences at HERE/Nokia

Dr. Alexander Schwartz

Wie verändert sich Testen mit Continuous Delivery?

Dr. Alexander Schwartz

How our product, the HERE Places RESTful API, ripened over time and how our understanding of quality changed over time. As every distinguished wine is the result of a long refining and ripening process, every software product is subject to a similar evolution, too. Of course along the journey of a product, the understanding of “Quality” is subject to major changes as well. Lets join the 3-year journey of a software product through its various stages, from planning, seeding to its first wine tasting (that is, the beta offer), to selling the first bottles (that is, the service is used by other internal products), finally to its market readiness (that is, becoming a commercial B2B offer with SLAs). The product under test is the Places RESTful API (places.demo.api.here.com), which delivers data for Places that are shown in various products, for instance for Nokia’s HERE.com maps. We concentrate on three different aspects and how they change over time: * the understanding of what quality means, * the test strategy, and last but not least * how to deal with the intrinsic complexity. We are going to explore the post production deployment part of our process: How we ensure the high availability of this complex service, as well as which test techniques, feedback mechanisms and in particular which visualizations (monitoring 2.0) we leverage for this purpose. Presented a the Agile Testing Days 2013.

Ripening of a RESTful API

Dr. Alexander Schwartz

Presented at the goto;conference in Berlin 2013 (http://gotocon.com/berlin-2013). Most teams introducing Continuous Delivery face problems such as "How do we fit our 4-day QA phase into a daily release rhythm?" The transition to a DevOps strategy and Continuous Delivery usually requires a significant readjustment of the testing approach. Alex shares stories from various companies he worked for, and discusses different ideas on how to retrofit testing for frequent releases. This includes adapting the rhythm of testing, test techniques, scope of testing, and re-thinking the entire quality assurance approach.

Help, we have no more time for testing! (gotoCon Berlin 2013)

Dr. Alexander Schwartz

AWS Ingredients for Deployment Patterns & the PBAPI canary-blue/green-hotstan...

Dr. Alexander Schwartz

Ignite Talk: Help, we have no more time for testing!

Dr. Alexander Schwartz

presented at the conference Agile Testing Days 2012 in Berlin/Potsdam Original version on prezi: http://prezi.com/o39xxactxm6o/how-releasing-faster-changes-testing/ ABSTRACT: In his keynote at the ATD2011 Gojo Adzic covered the “Five key challenges for agile testers tomorrow”. The first one mentioned is the impact of shorter release cycles on testing: “release cycles will get shorter, so short even that there’s no time for testing.” In this talk Alex shares what he learned about this topic during the last four years, on his journey with two companies. In both companies he helped to change the release rhythm dramatically, which had a deep impact on the all facets of the test strategy, of course including cooperation and communication structures. Whereas some lessons learned are obvious, others are unexpected and even counter-intuitive.

How releasing faster changes testing

Dr. Alexander Schwartz

How to Introduce Continuous Delivery

Dr. Alexander Schwartz

How We Introduced Continuous Delivery?

Dr. Alexander Schwartz

Kanban und DevOps bei Nokia

Dr. Alexander Schwartz

Mais de Dr. Alexander Schwartz (20)

Wrestling with Conway's Law: How to support cross-functional teams working on...

#AT16VIE: Does Agile mean we have no time for testing?

Does agile mean having even less time for testing?!

User Stories Schneiden mit Elefanten-Carpaccio (Scrum-Day 2016)

Hilfe, wir haben keine Zeit zum Testen!

Change Dojo - Agile Testing Days 2015

ScrumDay2015: Ein neues Dojo: Anwendergeschichten zerschneiden

Insights From Happy Change Agents

Ein neues Dojo: Anwendergeschichten zerschneiden

A New Dojo: The Art of Story Splitting

DevOps in the Enterprise: Our Experiences at HERE/Nokia

Wie verändert sich Testen mit Continuous Delivery?

Ripening of a RESTful API

Help, we have no more time for testing! (gotoCon Berlin 2013)

AWS Ingredients for Deployment Patterns & the PBAPI canary-blue/green-hotstan...

Ignite Talk: Help, we have no more time for testing!

How releasing faster changes testing

How to Introduce Continuous Delivery

How We Introduced Continuous Delivery?

Kanban und DevOps bei Nokia

Último

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

What is a good lead in your organisation? Which leads are priority? What happens to leads? When sales and marketing give different answers to these questions, or perhaps aren't sure of the answers at all, frustrations build and opportunities are left on the table. Join us for an illuminating session with Cian McLoughlin, HubSpot Principal Customer Success Manager, as we look at that crucial piece of the customer journey in which leads are transferred from marketing to sales.

04-2024-HHUG-Sales-and-Marketing-Alignment.pptx

HampshireHUG

The 7 Things I Know About Cyber Security After 25 Years | April 2024

Rafal Los

Scaling API-first – The story of a global engineering organization

Radu Cotescu

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Scaling API-first – The story of a global engineering organization Ian Reasor, Senior Computer Scientist - Adobe Radu Cotescu, Senior Computer Scientist - Adobe Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

apidays

💉💊+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHABI}}+971581248768 +971581248768 Mtp-Kit (500MG) Prices » Dubai [(+971581248768**)] Abortion Pills For Sale In Dubai, UAE, Mifepristone and Misoprostol Tablets Available In Dubai, UAE CONTACT DR.Maya Whatsapp +971581248768 We Have Abortion Pills / Cytotec Tablets /Mifegest Kit Available in Dubai, Sharjah, Abudhabi, Ajman, Alain, Fujairah, Ras Al Khaimah, Umm Al Quwain, UAE, Buy cytotec in Dubai +971581248768''''Abortion Pills near me DUBAI | ABU DHABI|UAE. Price of Misoprostol, Cytotec” +971581248768' Dr.DEEM ''BUY ABORTION PILLS MIFEGEST KIT, MISOPROTONE, CYTOTEC PILLS IN DUBAI, ABU DHABI,UAE'' Contact me now via What's App…… abortion Pills Cytotec also available Oman Qatar Doha Saudi Arabia Bahrain Above all, Cytotec Abortion Pills are Available In Dubai / UAE, you will be very happy to do abortion in Dubai we are providing cytotec 200mg abortion pill in Dubai, UAE. Medication abortion offers an alternative to Surgical Abortion for women in the early weeks of pregnancy. We only offer abortion pills from 1 week-6 Months. We then advise you to use surgery if its beyond 6 months. Our Abu Dhabi, Ajman, Al Ain, Dubai, Fujairah, Ras Al Khaimah (RAK), Sharjah, Umm Al Quwain (UAQ) United Arab Emirates Abortion Clinic provides the safest and most advanced techniques for providing non-surgical, medical and surgical abortion methods for early through late second trimester, including the Abortion By Pill Procedure (RU 486, Mifeprex, Mifepristone, early options French Abortion Pill), Tamoxifen, Methotrexate and Cytotec (Misoprostol). The Abu Dhabi, United Arab Emirates Abortion Clinic performs Same Day Abortion Procedure using medications that are taken on the first day of the office visit and will cause the abortion to occur generally within 4 to 6 hours (as early as 30 minutes) for patients who are 3 to 12 weeks pregnant. When Mifepristone and Misoprostol are used, 50% of patients complete in 4 to 6 hours; 75% to 80% in 12 hours; and 90% in 24 hours. We use a regimen that allows for completion without the need for surgery 99% of the time. All advanced second trimester and late term pregnancies at our Tampa clinic (17 to 24 weeks or greater) can be completed within 24 hours or less 99% of the time without the need surgery. The procedure is completed with minimal to no complications. Our Women's Health Center located in Abu Dhabi, United Arab Emirates, uses the latest medications for medical abortions (RU-486, Mifeprex, Mifegyne, Mifepristone, early options French abortion pill), Methotrexate and Cytotec (Misoprostol). The safety standards of our Abu Dhabi, United Arab Emirates Abortion Doctors remain unparalleled. They consistently maintain the lowest complication rates throughout the nation. Our Physicians and staff are always available to answer questions and care for women in one of the most difficult times in their lives. The decision to have an abortion at the Abortion Cl

+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...

?#DUbAI#??##{{(☎️+971_581248768%)**%*]'#abortion pills for sale in dubai@

MySQL Webinar, presented on the 25th of April, 2024. Summary: MySQL solutions enable the deployment of diverse Database Architectures tailored to specific needs, including High Availability, Disaster Recovery, and Read Scale-Out. With MySQL Shell's AdminAPI, administrators can seamlessly set up, manage, and monitor these solutions, ensuring efficiency and ease of use in their administration. MySQL Router, on the other hand, provides transparent routing from the application traffic to the backend servers in the architectures, requiring minimal configuration. Completely built in-house and supported by Oracle, these solutions have been adopted by enterprises of all sizes for their business-critical applications. In this presentation, we'll delve into various database architecture solutions to help you choose the right one based on your business requirements. Focusing on technical details and the latest features to maximize the potential of these solutions.

Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...

Miguel Araújo

Enterprise Knowledge’s Urmi Majumder, Principal Data Architecture Consultant, and Fernando Aguilar Islas, Senior Data Science Consultant, presented "Driving Behavioral Change for Information Management through Data-Driven Green Strategy" on March 27, 2024 at Enterprise Data World (EDW) in Orlando, Florida. In this presentation, Urmi and Fernando discussed a case study describing how the information management division in a large supply chain organization drove user behavior change through awareness of the carbon footprint of their duplicated and near-duplicated content, identified via advanced data analytics. Check out their presentation to gain valuable perspectives on utilizing data-driven strategies to influence positive behavioral shifts and support sustainability initiatives within your organization. In this session, participants gained answers to the following questions: - What is a Green Information Management (IM) Strategy, and why should you have one? - How can Artificial Intelligence (AI) and Machine Learning (ML) support your Green IM Strategy through content deduplication? - How can an organization use insights into their data to influence employee behavior for IM? - How can you reap additional benefits from content reduction that go beyond Green IM?

Driving Behavioral Change for Information Management through Data-Driven Gree...

Enterprise Knowledge

Finology Group – Insurtech Innovation Award 2024

The Digital Insurer

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

Created by Mozilla Research in 2012 and now part of Linux Foundation Europe, the Servo project is an experimental rendering engine written in Rust. It combines memory safety and concurrency to create an independent, modular, and embeddable rendering engine that adheres to web standards. Stewardship of Servo moved from Mozilla Research to the Linux Foundation in 2020, where its mission remains unchanged. After some slow years, in 2023 there has been renewed activity on the project, with a roadmap now focused on improving the engine’s CSS 2 conformance, exploring Android support, and making Servo a practical embeddable rendering engine. In this presentation, Rakhi Sharma reviews the status of the project, our recent developments in 2023, our collaboration with Tauri to make Servo an easy-to-use embeddable rendering engine, and our plans for the future to make Servo an alternative web rendering engine for the embedded devices industry. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://ossna2024.sched.com/event/1aBNF/a-year-of-servo-reboot-where-are-we-now-rakhi-sharma-igalia

A Year of the Servo Reboot: Where Are We Now?

Igalia

Effective data discovery is crucial for maintaining compliance and mitigating risks in today's rapidly evolving privacy landscape. However, traditional manual approaches often struggle to keep pace with the growing volume and complexity of data. Join us for an insightful webinar where industry leaders from TrustArc and Privya will share their expertise on leveraging AI-powered solutions to revolutionize data discovery. You'll learn how to: - Effortlessly maintain a comprehensive, up-to-date data inventory - Harness code scanning insights to gain complete visibility into data flows leveraging the advantages of code scanning over DB scanning - Simplify compliance by leveraging Privya's integration with TrustArc - Implement proven strategies to mitigate third-party risks Our panel of experts will discuss real-world case studies and share practical strategies for overcoming common data discovery challenges. They'll also explore the latest trends and innovations in AI-driven data management, and how these technologies can help organizations stay ahead of the curve in an ever-changing privacy landscape.

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

TrustArc

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

sammart93

With more memory available, system performance of three Dell devices increased, which can translate to a better user experience Conclusion When your system has plenty of RAM to meet your needs, you can efficiently access the applications and data you need to finish projects and to-do lists without sacrificing time and focus. Our test results show that with more memory available, three Dell PCs delivered better performance and took less time to complete the Procyon Office Productivity benchmark. These advantages translate to users being able to complete workflows more quickly and multitask more easily. Whether you need the mobility of the Latitude 5440, the creative capabilities of the Precision 3470, or the high performance of the OptiPlex Tower Plus 7010, configuring your system with more RAM can help keep processes running smoothly, enabling you to do more without compromising performance.

Boost PC performance: How more available memory can improve productivity

Principled Technologies

Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...

Neo4j

Developing An App To Navigate The Roads of Brazil

V3cube

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

Tata AIG General Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

What is Agile Testing?

1. What is Agile Testing? Alex Schwartz, HERE Berlin

2. Agile Testing is…

3. Agile Testing is… me colleague

4. Agile Testing is… I found a conference for Agile Testing! me colleague

5. Agile Testing is… I found a conference for Agile Testing! me Why? Agile Testing is nonsense! colleague

6. Agile Testing is… nonsense I found a conference for Agile Testing! me Why? Agile Testing is nonsense! colleague

7. Agile Testing is…

8. Agile Testing is… - Testing in the context of Agile Development

9. Agile Testing is… - Testing in the context of Agile Development - often one of the harder challenges during an Agile Transition

10. What is special about Agile Testing?

11. What is special about Agile Testing? 1. When?

12. What is special about Agile Testing? 1. 2. When? Who?

13. What is special about Agile Testing? 1. 2. When? 3. Who? How? What?

14. When? Late testing approach Design Planning Release Dev Test / Hardening

15. When? Late testing approach Design Planning Release Dev Test / Hardening

16. When? Late testing approach Design Planning Release Dev Test / Hardening

17. When? Late testing approach Design Planning Release Dev Test / Hardening

18. When? Late testing approach Design Planning risk for schedule Release Dev Test / Hardening

19. When? When we have good quality? Late testing approach Design Planning risk for schedule Release Dev Test / Hardening

20. When? When we have good quality? Late testing approach Design Planning Quality Level risk for schedule Release Dev Test / Hardening time

21. When? When we have good quality? Late testing approach Design Planning Quality Level risk for schedule Release Dev Test / Hardening time

22. When? When we have good quality? Late testing approach Design Planning Release Dev Quality Level risk for schedule Test / Hardening Quality/Verification Debt time

23. When? When to test & to fix? Design Planning Release Dev Test / Hardening

24. When? When to test & to fix? Scale Design Planning Release Dev Test / Hardening

25. When? When to test & to fix? Scale Design Planning Earlier • • • • • Release Dev Test / Hardening TDD/ATDD Continuous Integration Requirements discussions Early Feedback …

26. When? When to test & to fix? Scale Design Planning Earlier • • • • • Release Dev Test / Hardening TDD/ATDD Continuous Integration Requirements discussions Early Feedback … Asynchronous activities • • e.g. quarterly security tests …

27. When? When to test & to fix? Scale Design Planning Earlier • • • • • Release Dev Test / Hardening TDD/ATDD Continuous Integration Requirements discussions Early Feedback … Don’t do Are all your tests helpful? Asynchronous activities • • e.g. quarterly security tests …

28. When? When to test & to fix? Scale Design Planning measure, observe, … Release Dev Earlier • • • • • Learn from production Test / Hardening TDD/ATDD Continuous Integration Requirements discussions Early Feedback … Don’t do Are all your tests helpful? Asynchronous activities • • e.g. quarterly security tests …

29. When? When we have good quality? Late vs. early testing approach Design Planning Release Dev Quality Level Test / Hardening early testing late testing time

30. Who? Testing Test QA/Tester Automation Verifying Requirements

31. Who? Testing Test QA/Tester Automation Verifying Requirements

32. Who? Testing Test QA/Tester Automation Verifying Requirements

33. Who? Testing Test QA/Tester Automation Verifying Requirements

34. Who? All of us. Testing Test QA/Tester Automation Verifying Requirements

35. Who? All of us. Testing Test QA/Tester Automation Verifying Requirements QA = consultant for quality

36. What? What is quality? Source: Gojko Adzic correct, functional

37. What? What is quality? performant, etc. Source: Gojko Adzic correct, functional

38. What? What is quality? useful usable performant, etc. Source: Gojko Adzic correct, functional

39. What? What is quality? successful useful usable performant, etc. Source: Gojko Adzic correct, functional

40. Agile Testing is…

41. Agile Testing is… natural