Development without Testers: Myth or Real Option? (ConfeT&QA conference)

•

8 recomendaciones•1,680 vistas

Presentation from online conference ConfeT&QA (March 2012) about true role of testers and ways to fix development process to avoid their participation in usual stages of the quality control chain.

Tecnología

DEVELOPMENT WITHOUT TESTERS:
MYTH OR REAL OPTION?
Mikalai Alimenkou
http://xpinjection.com
14.03.2012

Background
• Java Technical Lead/Scrum Master at Zoral
Labs
• 7+ years in software development
• 5+ years of working by Agile
methodologies
• Expert in Agile engineering practices
• Founder and coach at XP Injection
(http://xpinjection.com)
• Organizer of Selenium Camp, JEEConf and
XP Days Ukraine conferences

Before start doing something you need to understand it properly

I. WRONG VISION OF TESTING
ACTIVITY

Why so many testers?

Too many bugs “Brave” automation team

Endless regression testing Very quick development

What is the “ideal”
dev/tester ratio?
Dev Tester ?

Devs Tester ?
Devs Tester ?

X Devs Y Testers ?

Where may problems
happen? Can’t implement
what they want

Can’t explain
requirements

Customer
Existing functionality is Dev Team

broken when new is ready

People can’t read minds and any communication channels lose data

II. BROKEN REQUIREMENTS
CHANNEL

Discuss everything in details
before start implementing

Make customers accept
results of development
responsibly

Even very good developer can make stupid mistake

III. DEVELOPERS MAKE MISTAKES

Team design session
before implementation

Pair programming for the
most complex parts

Strong definition of DONE
Can I start testing
this new feature?

Yes, it is done!

But I can’t even build
the product…

Ops, I forgot to
commit some files...

TDD at all levels
ATDD TDD
Customer’s Tests Programmers’ Tests

Acceptance Fixtures Production Unit Integration
Tests Code Tests Tests

Existing functionality must never be broken

IV. IMPLEMENTED ONCE, WORKING
FOREVER

Build safety net from
completely automated tests

This role is always needed, but can be played by different people

V. TESTER IS A ROLE, NOT A PERSON

Magic happens when
everybody know
that there are
no testers

Shared
responsibility
for quality
is built

Give development process what it really needs

VI. HOW TO SURVIVE? PLAY RIGHT
ROLE!

Help developers to do
slicing development

@xpinjection
http://xpinjection.com
mikalai.alimenkou@xpinjection.com

Más contenido relacionado

La actualidad más candente

Swiss Testing Day - Testautomation, 10 (sometimes painful) lessons learned

Michael Palotas

Test Driven Development

Orbit One - We create coherence

Pair Programming (2014)

Peter Kofler

Ethics... It could be the most important and underrated topic in software industry. It is directly related with professionalism, craftsmanship and professional discipline. From time to time we have to jump into the discussions, however we never discuss it deeper. I have found himself in a huge blast of discussions when he tweeted about a **HUGE** security issue at the most popular operating system. Then I had deep thoughts about ethics and the behaviours of ethical developers. In this session I talk about the followings: * I refer to real-life stories of many good practices for professional ethics that are critical in the software development world. * I mention technical and non-technical aspects of being an ethical developer. * I deep dive into the arguments against the ethical controversies and the debate over the sharing of a major error in MacOS via Twitter.

Irresponsible Disclosure: Short Handbook of an Ethical Developer

Lemi Orhan Ergin

Developer disciplines

Chris Howe-Jones

As developers, we often complain about the efficiency problems we face while working. We work hard but produce so little that our whole development life turns into a hamster wheel at some point. One of the biggest reason of such a common problem is working in waste. Waste is in everywhere, in our source code, in the office, in our processes and even in management. In this session, I will talk about the wastes and how we can remove to make our development life leaner.

Let the Elephants Leave the Room: Tips for Making Development Life Leaner by ...

Bosnia Agile

In this report we take a look at the top 10 reasons Java is the choice for so many development teams, all around the world, and why you should consider it for your next project. One of the main qualities Java possesses since the early design days is its simplicity. In that spirit we laid out in plain simple terms why Java outperforms other languages when it comes to popularity, performance, its amazing ecosystem and community. For the less technical, this report explains the value Java brings to your projects. For fellow developers, we included some other projects in the Java ecosystem that you might want to look at. Check them out, have a play with them. It will make you a better developer. Continue to the full report on RebelLabs: http:0t.ee/java-rocks

Top Reasons Why Java Rocks (report preview) - http:0t.ee/java-rocks

ZeroTurnaround

DevOps & Technical Agility: From Theory to Practice

Lemi Orhan Ergin

Test driven development

Sharafat Ibn Mollah Mosharraf

Scrum Events and Artifacts in Action

Lemi Orhan Ergin

Justin Ison

CodeFest

Andy Rachleff, Wealthfront Presentation at Lean Startup SXSW

500 Startups

Recipe of a rockstar developer

Topu Newaj

Frank's Learning Summary - Evolution of agile testing

Frank Lee

There's still a lot of discussion on whether testers should be able to code or not. While coding and understanding of code is a useful skill, this presentation sets out to remind us of the stuff that does not involve code but is definitely relevant in developing software. The presentation takes on a case view of things I do as a single "testing specialist" with a product development team of developers. We look at examples of things of value contributed as realised activities towards a common goal. While presented from a testers perspective, there will be a lot of aspects anyone interested in software development may find relevant and useful.

I Don't Code, Am I No Longer Useful

Maaret Pyhäjärvi

Testing: the more you do it, the more you'll like it

Jeffrey McGuire

Test driven development

Nascenia IT

Continuous delivery its not about the technology, its about the people. @pipe...

Tomas Riha

Reliable tests with selenium web driver

PawelPabich

Tdd 4 everyone full version

Lior Israel

La actualidad más candente (20)

Swiss Testing Day - Testautomation, 10 (sometimes painful) lessons learned

Test Driven Development

Pair Programming (2014)

Irresponsible Disclosure: Short Handbook of an Ethical Developer

Developer disciplines

Let the Elephants Leave the Room: Tips for Making Development Life Leaner by ...

Top Reasons Why Java Rocks (report preview) - http:0t.ee/java-rocks

DevOps & Technical Agility: From Theory to Practice

Test driven development

Scrum Events and Artifacts in Action

Justin Ison

Andy Rachleff, Wealthfront Presentation at Lean Startup SXSW

Recipe of a rockstar developer

Frank's Learning Summary - Evolution of agile testing

I Don't Code, Am I No Longer Useful

Testing: the more you do it, the more you'll like it

Test driven development

Continuous delivery its not about the technology, its about the people. @pipe...

Reliable tests with selenium web driver

Tdd 4 everyone full version

Destacado

World Wide Web Caching

ersanbilik

Caching technology comparison

Rohit Kelapure

Тестировщики часто говорят о противостоянии и конфликтах с разработчиками. Но ведь есть команды, где все живут в мире и согласии. Видимо что-то тут не так? Я хочу поговорить о том, как тестировщиков видят сами разработчики. В докладе будет проведена забавная классификация. Кроме известного всем тестировщика-обезьянки будут представлены тестировщик-муха, тестировщик-нацист, тестировщик-панда и многие другие герои. Высможете лишний раз задуматься над тем, как вас видят со стороны и, возможно, изменить ситуацию к лучшему. Доклад будет также полезен менеджерам проектов и лидерам команд. Вы сможете быстрее распознавать те или иные шаблоны поведения тестировщикови принимать меры по повышению уровня командной работы. Приходите, будет интересно!

Бытовая классификация тестировщиков с точки зрения разработчика

Mikalai Alimenkou

When you work in a small collocated team many engineering practices and approaches are relatively easy to use and adapt. In large project with many teams working on the same product this task is not so simple. I want to share experience report in implementing Code Review practice in big product development team (more than 150 people, 10+ feature teams). In this talk we will review what approaches works in such setup and what don’t work, what tools and additional practices are needed to support Code Review and make it more effective, what difficulties and blockers will you probably see in the real life cases, what useful metrics could be produced by this practice.

Code review at large scale

Mikalai Alimenkou

Caching In Java- Best Practises and Pitfalls

HARIHARAN ANANTHARAMAN

Caching for J2ee Enterprise Applications

Debajani Mohanty

Scalable Application Development on AWS

Mikalai Alimenkou

Micro Service Architecture 탐방기

jbugkorea

Destacado (8)

World Wide Web Caching

Caching technology comparison

Бытовая классификация тестировщиков с точки зрения разработчика

Code review at large scale

Caching In Java- Best Practises and Pitfalls

Caching for J2ee Enterprise Applications

Scalable Application Development on AWS

Micro Service Architecture 탐방기

Similar a Development without Testers: Myth or Real Option? (ConfeT&QA conference)

10 Lessons learned in test automation

Romania Testing

Agile Testing by Example

Mikalai Alimenkou

30 days or less: New Features to Production

Karthik Gaekwad

TDD in Agile

Atish Narlawar

Test-driven development is generally regarded as a good move: it should result in simple decoupled design, your tests tend to cover behaviour not methods, and far fewer bugs. However, just getting unit tests in on a real, commercial project is hard - switching to TDD is even harder. Often you can start a project with good intentions and coverage, then the deadline looms and the tests go out then the hacks come in. So, instead of beating ourselves up about not being perfect let's look at an interative approach to adopting TDD principles. We'll look at tactics for selling TDD to your client, boss and colleagues. This talk will also cover methods for making TDD easier for you by showing you what tools you can use to integrate it into your development environment. In the project itself, we'll examine how we can make small but permanent steps towards full TDD, without losing that progress when deadlines hit. We'll also cover a few methods for learning on your own time and how the whole process can actually be made quite enjoyable.

TDD and Getting Paid

Rowan Merewood

“A comprehensive suite of JUnit tests is one of the most import aspects of a software project because it reduces bugs, facilitates adding new developers, and enables refactoring and performance tuning with confidence. Test-driven development (TDD) is the best way to build a suite of tests. And the Dependent Object Framework is the best way to test against database objects.” This presentation covers the benefits of TDD along with practical advice on how to implement TDD in complex projects.

xUnit and TDD: Why and How in Enterprise Software, August 2012

Justin Gordon

Improving developer tester collaboration with microsoft visual studio 2010

Mohamed Samy

Unit Testing

Gian Maria Ricci

Unit Testing, TDD and the Walking Skeleton

Seb Rose

Test Driven Development

pmanvi

TDD in functional testing with WebDriver

Mikalai Alimenkou

Cas2010 is-there-space-for-testers-in-agile-projects

Agile Spain

Test driven development v1.0

Ganesh Kondal

Test-Driven Development In Action

Jon Kruger

Agile Software Development Process Practice in Thai Culture

Wee Witthawaskul

Usable Software Design

Alexandru Bolboaca

This presentation on Continuous Delivery is from the November 2013 Automated Testing San Francisco meetup that took place at Constant Contact. The author/presenter is Matt Wilson, CTO of Lab Zero. Matt has advised clients at various industries including consumer brands, non-profits, start-ups, and financial services on Agile development, web application development, and other technology leadership challenges. This overview on Continuous Delivery highlights some of the best practices that Lab Zero has distilled, based on their many client engagements. --- About Matt Wilson: Matt is an enthused agile developer, architect, and consultant. He enjoys building elegant web services in Ruby. He believes that high-fives are underrated and measures the success of his day by how many he's seen. Prior to joining Lab Zero, Matt's work history includes: Co-founder/Architect at Earfl.com, Architect at Kodak Gallery, Developer at Westwave Communications, Engineer at Motorola, and Developer at Coldwell Banker. About Lab Zero: Lab Zero Innovations, Inc. provides web application development and technology leadership consulting. Our client relationships include staff augmentation, pure software development, project management, system integration, advisor/leadership roles. Contact us about your next project.

Don't hate, automate. lessons learned from implementing continuous delivery

Solano Labs

Software presentation

JennaPrengle

Continuous Delivery for Agile Teams

Mike Bowler

Agile Testing 20021015

Raghu Karnati

Similar a Development without Testers: Myth or Real Option? (ConfeT&QA conference) (20)

10 Lessons learned in test automation

Agile Testing by Example

30 days or less: New Features to Production

TDD in Agile

TDD and Getting Paid

xUnit and TDD: Why and How in Enterprise Software, August 2012

Improving developer tester collaboration with microsoft visual studio 2010

Unit Testing

Unit Testing, TDD and the Walking Skeleton

Test Driven Development

TDD in functional testing with WebDriver

Cas2010 is-there-space-for-testers-in-agile-projects

Test driven development v1.0

Test-Driven Development In Action

Agile Software Development Process Practice in Thai Culture

Usable Software Design

Don't hate, automate. lessons learned from implementing continuous delivery

Software presentation

Continuous Delivery for Agile Teams

Agile Testing 20021015

Más de Mikalai Alimenkou

Люди в мире Agile используют Story Points - для Agile коучей и тренеров это самый простой способ объяснить, как следует проводить оценку и планирование в «новом мире». Но тогда эта простая концепция нарушает реальные практические кейсы. В настоящее время команды состоят из очень специализированных людей, работающих над бэкендом, фронтэндом, тестировании, инфраструктуре и прочим. Для них почти невозможно иметь общий уровень сложности. Это только одна из проблем, которые мы собираемся осветить в этом докладе. Чтобы оставаться конструктивным, а не просто старомодным парнем из XP, Николай поделится своим опытом с более точной и прагматичной техникой оценки/планирования - планированием на основе возможностей.

Rise and fall of Story Points. Capacity based planning from the trenches.

Mikalai Alimenkou

We have spent many years testing our applications and systems manually and with test automation tools. During this time many bug root causes have been classified and could be detected automatically with special static analysis tools. Most of them could be applied at the early stages of development even before code is integrated into the main development branch. In this talk, I will go through available solutions and demonstrate what kinds of issues may be detected automatically reducing the time and effort of traditional testing.

Static analysis tools as the best friend of QA

Mikalai Alimenkou

In this talk, we will go through the design process of modern CI/CD for the microservices-based system with Kubernetes support. We will discuss how to verify consistency between microservices, apply different levels of quality gates and promote artifacts between environments. Thanks to Kubernetes we will review different approaches of environment resources optimization for development needs during CI/CD cycles.

Modern CI/CD in the microservices world with Kubernetes

Mikalai Alimenkou

Most of people nowadays think microservices architecture is a great way to build any system. They visit conference talks, read books and review tutorials, where ‘hello world’ applications are built just in several minutes using microservices approach. But the reality is not so wonderful and one of the biggest pain is hidden inside distributed business transactions. In monolith application this topic is almost completely covered with DB level transactions. In distributed world you have to face many issues trying to implement reliable and consistent business logic. In this talk we will review different types of problems related to distributed business transactions, popular SAGA pattern, frameworks and techniques to simplify your life without compromising quality of the system.

Saga about distributed business transactions in microservices world

Mikalai Alimenkou

Effectiveness tips from Kubernetes trenches by Captain Obvious

Mikalai Alimenkou

For a long time DB related testing in Java world has been a real pain and most developers tried to reduce number of such tests as much as possible. With good in-memory database implementations like H2, schema migration solutions like Liquibase or Flyway, containerization with libraries like TestContainers, database management is now much simpler. But test data management is still a pain. Some developers use SQL dumps, others insert data via JPA/JDBC or rely on prepared data sets. Good old DBUnit may be a good option, but it is not so developer friendly and not adopted well for modern annotations driven development style. Database Rider closes the gap between modern Java development environment and DBUnit, bringing DBUnit closer to your JUnit tests, so database testing will feel like a breeze. In addition to flexible data sets management this library provides other useful features: programmatic data sets definition, leak hunting, data sets export, constraints management, etc. As contributor and loyal user for many years, I would like to share my experience with Database Rider and demonstrate how to make database testing a fun again!

Ride the database in JUnit tests with Database Rider

Mikalai Alimenkou

I think almost everybody experienced cases when things are moving very slowly in IT companies or teams. You have many people, talented engineers, Agile process and development speed is still below expectations. We try to focus on performance and efficiency last 10 years, improving our practices and tools. But we are still there in terms of speed when they are applied to real life cases. How is it possible? In this talk we will review the concept of waste circles and understand what are the main sources of time waste in development process. This concept would help you to check your processess, focus on right things and achieve much better results in your organization or team.

Wastful waste or why everything is so slow in development

Mikalai Alimenkou

Nowadays traditional layered monolithic architecture in Java world is not so popular as 5-10 years ago. I remember how we wrote tons of code for each layer repeating almost the same parts for every application. Add unit and integration testing to understand how much time and efforts has been spent on repeatable work. All cool ideas around DDD (domain driven design) and Hexagonal Architecture was just a nice theory because reality hasn’t allow us to implement it easily. Even Dependency Injection with Spring framework was completely focused on traditional layered approach, not even talking about JavaEE platform. Today we have Spring Boot ecosystem covering most of our needs for integration with almost all possible technologies and microservices architectural trend, enabling completely new approach to build Java applications around domain model. It is so natural to build Java domain-oriented services and connect them with external world using ports and adapters, that Hexagonal Architecture is almost enabled by default. You just need to switch your way of thinking…

Hexagonal architecture with Spring Boot

Mikalai Alimenkou

Wastful waste or why everything is so slow in development

Mikalai Alimenkou

DevOps become a buzzword in a last few years. Several companies, development and product teams have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques. Do you think is achievable for you team or it’s still a bunch of drama? There is no common approach for measuring achievements and understanding how much DevOps’ich the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.

DevOps checklist or how to understand where is your team in DevOps landscape ...

Mikalai Alimenkou

DevOps is a hot topic during last several years. Some companies, teams and products have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques. At the same time there is no common approach for measuring achievements and understanding “how DevOps” the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.

DevOps checklist or how to understand where is your team in DevOps landscape

Mikalai Alimenkou

Почти год мы в Whirl Software разрабатываем систему Медкарта в масштабе целой страны. За это время мы столкнулись с множеством интересных сложностей и проблем, часть из которых успешно победили, а для некоторых хорошего решения до сих пор не найдено. В этом докладе мы поделимся накопленным практическим опытом и некоторыми техническими решениями, которые могут быть полезны в рамках разработки электронных медицинских систем.

Практические трудности в разработке Медкарты для целой страны

Mikalai Alimenkou

Hexagonal architecture with Spring Boot [EPAM Java online conference]

Mikalai Alimenkou

Almost any application or software system manages data. It is hard to imagine test automation that is not affected by this fact. There are many differenct approaches how to prepare system under test, providing predefined test data: use application UI, invoke API methods, run business logic directly, access DB from test scenarios, etc. In this talk we will review most of existing approaches, starting from the easiest and the most popular ones and finishing with really tricky ways to manage your test data for large distributed systems. There is no ideal solution for every case or silver bullet, but I hope your toolset will become wider after visiting this talk.

Bro, manage test data like a pro! [QA Fest 2018]

Mikalai Alimenkou

Вот уже более 10 лет Agile движение шагает по Украине и стучится практически в каждую компанию. Но приносят ли новые процессы, принципы и практики реальную практическую пользу? Получается ли изменить к лучшему команды, проекты, компании? Я в роли консультанта за эти 10 лет поработал с более чем 100 компаниями, поэтому повидал много хорошего и плохого. В данном докладе хочется пробежаться по основным проблемам, сложностям и анти-паттернам в переходе отечественных компаний на "Agile рельсы". Мы рассмотрим какие практики не очень хорошо приживаются, от чего страдает большинство команд, какие основные препятствия встречают на своем пути и как умудряются их обходить. Я надеюсь, доклад поможет зародиться множеству интересных дискуссий.

Agile antipatterns: review after 10 years of practice

Mikalai Alimenkou

Hexagonal architecture with Spring Boot

Mikalai Alimenkou

Bro, manage test data like a pro!

Mikalai Alimenkou

Бытовая классификация тестировщиков с точки зрения разработчика

Mikalai Alimenkou

Usually it is hard to analyze personal effectiveness and detect wastes in development process because developer’s work decomposition is not transparent and available for analysis. As a good sample of ineffective process imagine developer, who spends 1 day on task implementation and then reimplements it several times according to code review notes during next 2 days. Or another developer, who is waiting for code review during 2 days, switching context to other tasks, finally gets notes and switches back to initial task, trying to refresh all details in his head. And so on and so forth… Code review tool usage helps to aggregate lots of useful information about any code change at any stage (static analysis, code review, rework, acceptance, integration into main branch). In this talk I’m going to demontrate how this information could be used for detailed analysis of development effectiveness and wastes detection. Based on mentioned analysis you could implement many improvements for your development process and then measure their success.

Code Review tool for personal effectiveness and waste analysis

Mikalai Alimenkou

During last several years DevOps became strong buzzword used almost in every project, team and company. But almost everywhere it is used in very funny and strange context. For example, existing ops guys are renamed to DevOps just to sell them to the client for more money. Or DevOps is used as new job title for some magically powerful person who is able to operate cloud environment and modern infrastructure related tools, leading team of old school ops and participating in management meetings. In this talk I’m going to review all different anti-patterns and bad practices in DevOps landscape using stories from my personal experience as Delivery Manager and independent consultant.

Funny stories and anti-patterns from DevOps landscape

Mikalai Alimenkou

Más de Mikalai Alimenkou (20)

Rise and fall of Story Points. Capacity based planning from the trenches.

Static analysis tools as the best friend of QA

Modern CI/CD in the microservices world with Kubernetes

Saga about distributed business transactions in microservices world

Effectiveness tips from Kubernetes trenches by Captain Obvious

Ride the database in JUnit tests with Database Rider

Wastful waste or why everything is so slow in development

Hexagonal architecture with Spring Boot

Wastful waste or why everything is so slow in development

DevOps checklist or how to understand where is your team in DevOps landscape ...

DevOps checklist or how to understand where is your team in DevOps landscape

Практические трудности в разработке Медкарты для целой страны

Hexagonal architecture with Spring Boot [EPAM Java online conference]

Bro, manage test data like a pro! [QA Fest 2018]

Agile antipatterns: review after 10 years of practice

Hexagonal architecture with Spring Boot

Bro, manage test data like a pro!

Бытовая классификация тестировщиков с точки зрения разработчика

Code Review tool for personal effectiveness and waste analysis

Funny stories and anti-patterns from DevOps landscape

Último

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

Manulife - Insurer Innovation Award 2024

The Digital Insurer

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

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

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

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

This presentation explores the impact of HTML injection attacks on web applications, detailing how attackers exploit vulnerabilities to inject malicious code into web pages. Learn about the potential consequences of such attacks and discover effective mitigation strategies to protect your web applications from HTML injection vulnerabilities. for more information visit https://bostoninstituteofanalytics.org/category/cyber-security-ethical-hacking/

HTML Injection Attacks: Impact and Mitigation Strategies

Boston Institute of Analytics

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

Partners Life - Insurer Innovation Award 2024

The Digital Insurer

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Edi Saputra

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

Neo4j

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

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

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

Discord is a free app offering voice, video, and text chat functionalities, primarily catering to the gaming community. It serves as a hub for users to create and join servers tailored to their interests. Discord’s ecosystem comprises servers, each functioning as a distinct online community with its own channels dedicated to specific topics or activities. Users can engage in text-based discussions, voice calls, or video chats within these channels. Understanding Discord Servers Discord servers are virtual spaces where users congregate to interact, share content, and build communities. Servers may revolve around gaming, hobbies, interests, or fandoms, providing a platform for like-minded individuals to connect. Communication Features Discord offers a range of communication tools, including text channels for messaging, voice channels for real-time audio conversations, and video channels for face-to-face interactions. These features facilitate seamless communication and collaboration. What Does NSFW Mean? The acronym NSFW stands for “Not Safe For Work,” indicating content that may be inappropriate for professional or public settings. NSFW Content NSFW content encompasses material that is sexually explicit, violent, or otherwise graphic in nature. It often includes nudity, profanity, or depictions of sensitive topics.

Understanding Discord NSFW Servers A Guide for Responsible Users.pdf

UK Journal

GenAI Risks & Security Meetup 01052024.pdf

lior mazor

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Real Time Object Detection Using Open CV

Khem

Development without Testers: Myth or Real Option? (ConfeT&QA conference)

1. DEVELOPMENT WITHOUT TESTERS: MYTH OR REAL OPTION? Mikalai Alimenkou http://xpinjection.com 14.03.2012

2. Background • Java Technical Lead/Scrum Master at Zoral Labs • 7+ years in software development • 5+ years of working by Agile methodologies • Expert in Agile engineering practices • Founder and coach at XP Injection (http://xpinjection.com) • Organizer of Selenium Camp, JEEConf and XP Days Ukraine conferences

3. Before start doing something you need to understand it properly I. WRONG VISION OF TESTING ACTIVITY

4. Why so many testers? Too many bugs “Brave” automation team Endless regression testing Very quick development

5. What is the “ideal” dev/tester ratio? Dev Tester ? Devs Tester ? Devs Tester ? X Devs Y Testers ?

6. Where may problems happen? Can’t implement what they want Can’t explain requirements Customer Existing functionality is Dev Team broken when new is ready

7. Developer is the root of evil!

8. Instead of control lets fix it!

9. People can’t read minds and any communication channels lose data II. BROKEN REQUIREMENTS CHANNEL

10. Divide work in small pieces

11. Discuss everything in details before start implementing

12. Use prototypes and mockups

13. Make customers accept results of development responsibly

14. Even very good developer can make stupid mistake III. DEVELOPERS MAKE MISTAKES

15. Team design session before implementation

16. 100% Code Review

17. Pair programming for the most complex parts

18. Detailed static code analysis

19. Stable releasable trunk

20. Strong definition of DONE Can I start testing this new feature? Yes, it is done! But I can’t even build the product… Ops, I forgot to commit some files...

21. TDD at all levels ATDD TDD Customer’s Tests Programmers’ Tests Acceptance Fixtures Production Unit Integration Tests Code Tests Tests

22. Existing functionality must never be broken IV. IMPLEMENTED ONCE, WORKING FOREVER

23. Build safety net from completely automated tests

24. Global Continuous Integration

25. This role is always needed, but can be played by different people V. TESTER IS A ROLE, NOT A PERSON

26. Magic happens when everybody know that there are no testers

27. Team members can play different roles

28. Shared responsibility for quality is built

29. Give development process what it really needs VI. HOW TO SURVIVE? PLAY RIGHT ROLE!

30. Help developers to do slicing development

31. Perform much exploratory testing

32. Help customer to express his minds

33.

34. @xpinjection http://xpinjection.com mikalai.alimenkou@xpinjection.com

Development without Testers: Myth or Real Option? (ConfeT&QA conference)

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (8)

Similar a Development without Testers: Myth or Real Option? (ConfeT&QA conference)

Similar a Development without Testers: Myth or Real Option? (ConfeT&QA conference) (20)

Más de Mikalai Alimenkou

Más de Mikalai Alimenkou (20)

Último

Último (20)

Development without Testers: Myth or Real Option? (ConfeT&QA conference)