Xp days ukraine 2012

•Download as ODP, PDF•

0 likes•1,349 views

The document discusses reversing the traditional tests pyramid when dealing with legacy code. It notes that with legacy code, there may be no true units to unit test. Instead, it advocates starting with end-to-end tests to build confidence to refactor the code into units and add integration and unit tests. However, it warns that end-to-end tests are long to maintain. The goal is to slowly reverse the tests pyramid by refactoring code into units and adding tests at each level to manage technical debt over time. Paying down technical debt is important to maintain the ability to change software.

Technology

Reversed Tests Pyramid

Wiktor Żołnowski

@streser
http://www.agileszkolenia.pl
http://codesprinters.com

Agile Coach Troublemaker
Who am I?
Passionate

Tests pyramid

End to End Tests

Functional/Integration Tests

Unit Tests

It would be perfect to work with perfect
software every day...

Sometimes Technical Debt could be
considered as something good...

Unfortunately temptation of easy
making money is huge...

People lives in illusion of continuous,
fast and low cost development...

Success in Software Development is something which is not
continuous...

Success is state that you can achieve but also lose very fast
if you can't respond to changes fast enough...

So, is it possible to deal with legacy code?

Reversed Tests Pyramid

End-to-End Tests

Functional/Integration Tests

Unit Tests

You can't do unit testing when there are
no units in your software...

You can't do integration tests when
there is nothing to integrate...

You need to refactor your code so it
would be testable...

Now refactor...

High level tests gives you courage to refactor your code...
●

Now you can refactor and introduce
some units into your software...

But.. There are few reasons why you shouldn't
reverse tests pyramid

End-To-End tests are too long...

End-to-end tests are difficult to maintain...
If we need end-to-end tests we are probably doing something
wrong with our architecture...

So it's all about reversing back our
tests pyramid.

Step by step we are introducing new
architecture...

Remember that creating reversed tests
pyramid and reversing it back will take
some time...

But you need to do this if you want to
pay your technical debt back!

Few final thoughts...

Keep your technical debt as low as possible and try to
pay it back every time you can. For example use your
slack time for that!

“Leave the world better then you found it”

Beware of refactoring just for refactoring!
Few final thoughts...

Few final thoughts...
● Beware of refactoring just for refactoring!
● Resist temptation to re-write from scratch – history is against you,
such projects usually fail.
● Remember to always remove your (duplicated) tests!
● Software quality in many cases could be understood as ability to
introduce changes into software!
● Keep your technical debt as low as possible and try to pay it back
every time you can. For example use your slack time for that!

Resist temptation to re-write from scratch – history is
against you, such projects usually fail.

False positive or false negative safety
net is even worst than lack of safety
net...

● Software quality in many cases could be understood as
ability to introduce changes into software!

Wiktor Żołnowski
www.codesprinters.com

Questions?

@streser
http://www.agileszkolenia.pl
http://codesprinters.com

The document discusses reversing the traditional tests pyramid for legacy code. It proposes starting with end-to-end tests to give courage for refactoring code into testable units. This establishes a reversed tests pyramid to gradually introduce a new architecture. The goal is to keep technical debt low by refactoring and removing duplicated tests to improve software quality and the ability to change the system. Beware of refactoring just for its own sake and resist rewriting from scratch.

Testing tdd jasmine

Philipp Fehre

The document introduces test-driven development (TDD) and provides examples of using it with Ruby and JavaScript. It explains that testing is not the same as TDD, and that test-first is a form of TDD where the tests are written before the code. Examples are given for building a FizzBuzz program and converting numbers to Roman numerals using TDD in a test-first approach with Ruby and JavaScript libraries. The document encourages thinking about the desired outcomes before implementing solutions in a straightforward way and making the solutions simpler.

Reversed Tests Pyramid - Agile Prague 2014

Wiktor Żołnowski

The document discusses dealing with legacy code by implementing a "reversed tests pyramid" approach. It recommends starting with end-to-end tests to allow refactoring the codebase into a more testable structure before introducing unit and integration tests. While end-to-end tests are difficult to maintain, this process helps pay down technical debt over time by improving code quality and making the software easier to change. The key is to reverse the tests pyramid gradually through refactoring supported by tests at each level.

Unit testing JS = SQLSat 324

Justin Obney

The document is an agenda for a presentation on JavaScript testing. The summary includes: 1) The presentation covers JavaScript testing fundamentals including the importance of testing, different testing frameworks, unit vs integration testing, and tools to assist with testing. 2) Testing JavaScript applications is important because JavaScript is widely used but many developers do not fully understand it. Writing tests encourages writing code in a testable way and prevents bugs. 3) The presentation concludes by thanking the audience and providing contact details for the presenter.

Performance testing for web-scale

Izzet Mustafaiev

If you heard about web-scale or have a requirement to survive under web-scale or you just would like to prepare your application to handle an X effect this topic is for you. During a presentation you will understand aspects and caveats of performance testing, nuances of performance testing of Java based web applications. As a practical part you will get a brief overview of existing tools and will get a guide of using Gatling as a tool to make a load for your application. Gatling is an open source tool for performance loading written in Scala and provides comprehensive DSL for load scenario specification.

Test driven development_and_puppet-cfgmgmtcamp_eu-20140402

Johan De Wit

Day1 - TDD (Lecture SS 2015)

wolframkriesing

This document provides an overview of a presentation on test-driven development (TDD) and JavaScript. It discusses concepts like refactoring, unit testing, pair programming, and practicing TDD in small exercises called code katas. The presentation covers JavaScript topics like variable scoping and introduces the basic steps of TDD: writing a failing test first, then just enough code to make it pass before refactoring. It emphasizes that TDD helps produce a simple design and provides quick feedback.

Unit testing traning

Diego Pacheco

The document discusses the importance of unit testing at different levels. It emphasizes that tests allow for safe refactoring, are a safety requirement, and help speed up development. Developer tests are important for faster development and validation. Mocked contract tests help ensure code changes don't break consumers. Stress and chaos tests are also important to test how systems handle load, failures, and edge cases. The document encourages testing beyond happy paths by considering invalid data, exceptions, and other scenarios. It concludes by noting the importance of coverage goals to help developers learn to write stable code.

This document discusses various tools and techniques for maintaining code quality, including EditorConfig for consistent code styling across editors, JSHint/JSLint/ESLint for flagging suspicious JavaScript usage, JSCS for enforcing a JavaScript code style, jsbeautifier/JsFormat for formatting code, (S)CSScomb for formatting CSS/SCSS code, Scss Lint for checking SCSS code quality, and automating these processes with Grunt/Gulp tasks and Git hooks. It also mentions the Plato tool for visualizing and analyzing code complexity. The overall message is that these linters, formatters, and automation help enforce code quality and style guidelines on a team project.

JavaScript Unit Testing

Mihail Gaberov

This document discusses JS unit testing and provides guidance on how to implement it. It explains that unit tests isolate and test discrete functions to ensure they work as intended. This helps refactor code to be modular, scalable, and easier to understand. While unit tests add initial time, they speed up development in the long run. Common JS testing libraries include Mocha, Jasmine, and assertion libraries like Chai to validate results. The document also provides example unit test code and links to additional resources on JS testing.

Why do you say BDD if it is Cucumber?

Enrique Sánchez-Bayuela

This document discusses the difference between Behavior-Driven Development (BDD) and Cucumber, a tool used for BDD. While Cucumber can be used for BDD, it does not guarantee that BDD is being properly practiced. BDD is a mindset and process that focuses on defining features and scenarios from the perspective of stakeholders to reduce miscommunication between teams. Gherkin language and Cucumber tool can be used to define narratives in a simple format understood by all teams. The document provides guidelines for writing effective scenarios using this approach to achieve emergent design through examples and collaboration between teams.

OpenWFEru (Ruote) @ BPMinna, June 2008

John Mettraux

The document discusses Ruote, an open source workflow engine written in Ruby. It notes that Ruote is a commercial open source project licensed under BSD, and can be used to manage long running asynchronous processes, start and stop processes, modify running processes, and handle errors by fixing and restarting processes. Ruote aims to provide clear and concise process definitions that are easy to write and maintain, making it appealing to those who follow agile software development principles.

Don’t let your code to be illiterate along with your colleagues

Izzet Mustafaiev

Do you remember you saw in the code method with name “getCatalogVerion()” or variable name “reimbusmentEntrys” or comment “necesarry”? If you’re an Eclipse user I’d say you’re lucky, IntelliJ guys are not. Why? Because they see those silly mistakes after Eclipse guys checked code in. If you’re an IntelliJent person and do not want to make a “holly war” come to my talk – I’m going to share a good practices to keep your code “clean” from grammar perspective as well.

JavaScript frontend testing from failure to good to great

Philipp Fehre

TDC2016POA | Trilha DevOps - DevOps Anti-Patterns

tdc-globalcode

Fernando Ike provides a document discussing DevOps anti-patterns, what DevOps is and is not, and best practices. The document includes sections on DevOps training topics, common misconceptions about DevOps roles, and advice for developers, operations, and managers implementing DevOps processes and culture. Anti-patterns discussed include using buzzwords to sell products/services, treating DevOps as only tools or processes, and prioritizing experience over problem-solving skills in hiring.

Best coding practices

Sergey Aganezov

Continuous Delivery - kolejny krok na drodze do Agile - Quality Excites 2014

Wiktor Żołnowski

Frameworki agilowe w obszarze testow - Monika Braun

Women in Technology Poland

A little bird told me... about a good page in your user guide

Sarah Maddox

Abe 2012

Wiktor Żołnowski

The document discusses the role of testers in Agile teams. It argues that while methodologies like Scrum and XP do not explicitly mention testers, they can still be valuable members of cross-functional teams. Testers bring a different perspective than programmers as they behave more like users. Their domain knowledge and ability to ask questions can help improve quality. Ultimately, the document says that while testers are not mentioned in Agile, they are still important team members, and that everyone on the team engages in a form of testing.

Stickies on the wall will not help you if you are building crappy software

Wiktor Żołnowski

This document discusses how agile practices like stickies on a wall will not help if an organization has underlying issues like building poor quality software, lack of trust among employees, or basic communication problems. It emphasizes that good organizations choose practices that fit their needs and that true agility is about dividing large products into independent subproducts that can be developed and managed separately. Scaling agile is about decomposition, not just scaling individual methods. Having an agile mindset and understanding what agile means is more important than any single practice.

Bdd and Agile Requirements Boiling Frogs 2016

Wiktor Żołnowski

Agile, Scrum, Lean Startup, Testy A/B, Zwinny Marketing, Lean Canvas, Agile Coaching, Test Driven Development, User Stories, BDD, SBE, ATDD, TDD po wrzucania do jednego kotła i odpowiednim zamieszaniu otrzymujemy…(?) Przepis na sukces… Lub wiele mitów i nieporozumień! Sukces lub totalną porażkę naszego produktu… Współczesne metody wytwarzania oprogramowania, nowoczesne technologie i narzędzia, masowy klient/odbiorca oraz dobrze wykwalifikowani, wszechstronni developerzy dają nam możliwości, o których nie mogliśmy marzyć jeszcze kilka lat temu. Niemniej jednak nadal popełniamy wiele błedów i nasze projekt raczej stosunkowo niezbyt często kończą sie spektakularnym sukcesem. Być może jednym z powodów tej niedoskonałości w procesach wytwarzania oprogramowania jest niekoniecznie dobre zrozumienie wspomnianych wyżej metod i narzędzi. A jeśli o zrozumienie chodzi to myślę, że najelpiej zacząć od początku naszego procesu czyli od wymagań. I właśnie o tym jest ta prezentacja… Jeśli wydaje Ci się, że wiesz już wszystko na temat BDD i wymagań w Agile to… Pewnie jesteś w błędzie… Nie, nie twierdzę, że na tym wykładzie dowiesz się wszystkiego w tym temacie… Być może jednak dowiesz się o rzeczach, które nie są oczywiste i które realnie pomoga Ci w pracy. Jeśli uważasz, że User Stories, BDD, ATDD i SBE nie mają sensu to… Zgadzam sie z Tobą i z chęcią powiem Ci dlaczego w Twoim kontekście im tego sensu brakuje (wspomożemy się w tym celu Cynefin Framework). Mowa będzie o mitach związanych z User Stories, Specification By Example, Behavior Driven Development, różnicy pomiędzy wymaganiami a specyfikacją, Cynefin Framework oraz Continuous Delivery.

Bogna Majchrzak, Magda Traciłowska - Tester jako strażnik jakości oprogramowaniaGeek Girls Carrots Poznan

Monika Braun - Agile Test Team

kraqa

selenium grid & docker

Łukasz Rosłonek

This document discusses testing web applications in a distributed environment using Selenium Grid and Docker. It describes the challenges of testing on virtual machines and how containerization with Docker addresses those challenges by running tests within Docker containers managed by Docker Compose. Examples are provided of pulling pre-built Selenium images from Docker Hub and running a Selenium Grid configuration with a hub and node containers defined in a docker-compose.yml file. Links are also included for additional Selenium Grid and Docker resources.

Monika Braun - "Tester i frameworki agilowe - rola testera w różnych metodyka...

kraqa

Artur Górski - How many defects are left

kraqa

The document discusses four methods for predicting the number of defects remaining in software: 1. Tracking defects found during development, system testing, and deployment. 2. Modeling the number of defects based on factors like complexity, injection rate, and size. 3. Using reliability growth models like the Weibull distribution to plot defects over time/testing effort. 4. Dividing the software into cells to track defects found in each cell.

Scrum and Kanban are not enough - Agile Slovenia 2013

Wiktor Żołnowski

Scrum and Kanban are not enough to make an organization agile. Good organizations choose practices that fit their needs, like valuing individuals, working software, customer collaboration and adaptability. While common project methods focus on fixed plans, agile emphasizes adapting to changes. Scaling agile means dividing work into independent sub-products developed by autonomous teams with communication. Stickers on a wall won't help without addressing cultural and technical foundations for agility.

Let's tests! Prezentacja Moniki Braun w trakcie warsztatów "Let's go to IT"

mamopracuj

BDD and Agile Requirements (v 2.1)

Wiktor Żołnowski

What's hot

Why and how to keep your code quality

Krešimir Antolić

JavaScript Unit Testing

Mihail Gaberov

Why do you say BDD if it is Cucumber?

Enrique Sánchez-Bayuela

OpenWFEru (Ruote) @ BPMinna, June 2008

John Mettraux

Don’t let your code to be illiterate along with your colleagues

Izzet Mustafaiev

JavaScript frontend testing from failure to good to great

Philipp Fehre

TDC2016POA | Trilha DevOps - DevOps Anti-Patterns

tdc-globalcode

Best coding practices

Sergey Aganezov

What's hot (8)

Why and how to keep your code quality

JavaScript Unit Testing

Why do you say BDD if it is Cucumber?

OpenWFEru (Ruote) @ BPMinna, June 2008

Don’t let your code to be illiterate along with your colleagues

JavaScript frontend testing from failure to good to great

TDC2016POA | Trilha DevOps - DevOps Anti-Patterns

Best coding practices

Viewers also liked

Continuous Delivery - kolejny krok na drodze do Agile - Quality Excites 2014

Wiktor Żołnowski

Frameworki agilowe w obszarze testow - Monika Braun

Women in Technology Poland

A little bird told me... about a good page in your user guide

Sarah Maddox

Abe 2012

Wiktor Żołnowski

Stickies on the wall will not help you if you are building crappy software

Wiktor Żołnowski

Bdd and Agile Requirements Boiling Frogs 2016

Wiktor Żołnowski

Bogna Majchrzak, Magda Traciłowska - Tester jako strażnik jakości oprogramowaniaGeek Girls Carrots Poznan

Monika Braun - Agile Test Team

kraqa

selenium grid & docker

Łukasz Rosłonek

Monika Braun - "Tester i frameworki agilowe - rola testera w różnych metodyka...

kraqa

Artur Górski - How many defects are left

kraqa

Scrum and Kanban are not enough - Agile Slovenia 2013

Wiktor Żołnowski

Let's tests! Prezentacja Moniki Braun w trakcie warsztatów "Let's go to IT"

mamopracuj

BDD and Agile Requirements (v 2.1)

Wiktor Żołnowski

Agileee 2012

Wiktor Żołnowski

The document discusses reversing the "tests pyramid" approach to address technical debt in legacy code. It notes that unit testing is difficult for code without separation of concerns, but refactoring without tests is risky. It proposes starting with high-level tests to gain confidence for refactoring into units and writing unit tests incrementally. However, end-to-end tests are long to maintain, and if needed, the architecture may be flawed. Reversing the tests pyramid and refactoring code in this way takes time but pays back technical debt and allows for sustainable changes. Beware of refactoring just for its own sake - focus on removing duplication and improving changeability.

KraQA #22, Filip Cynarski - Selenium Grid w chmurze Amazon Web Services

kraqa

Eleven step of software testing process

Himanshu

The 11-step software testing process follows a "V" model where the first five steps involve verifying interim deliverables and the last six steps involve validating the executable software. The 11 steps are: 1) assess development plan and status, 2) develop test plan, 3) test requirements, 4) test design, 5) test during programming, 6) execute and record results, 7) acceptance test, 8) report results, 9) test installation, 10) test software changes, and 11) evaluate test effectiveness. The process aims to validate and verify that the software meets requirements, works as expected, can be implemented consistently, and satisfies stakeholder needs.

Interoperability Testing

kraqa

Bdd and Agile Requirements

Wiktor Żołnowski

People are awesome - ALE 2014

Wiktor Żołnowski

Viewers also liked (20)

Continuous Delivery - kolejny krok na drodze do Agile - Quality Excites 2014

Frameworki agilowe w obszarze testow - Monika Braun

A little bird told me... about a good page in your user guide

Abe 2012

Stickies on the wall will not help you if you are building crappy software

Bdd and Agile Requirements Boiling Frogs 2016

Bogna Majchrzak, Magda Traciłowska - Tester jako strażnik jakości oprogramowania

Monika Braun - Agile Test Team

selenium grid & docker

Monika Braun - "Tester i frameworki agilowe - rola testera w różnych metodyka...

Artur Górski - How many defects are left

Scrum and Kanban are not enough - Agile Slovenia 2013

Let's tests! Prezentacja Moniki Braun w trakcie warsztatów "Let's go to IT"

BDD and Agile Requirements (v 2.1)

Agileee 2012

KraQA #22, Filip Cynarski - Selenium Grid w chmurze Amazon Web Services

Eleven step of software testing process

Interoperability Testing

Bdd and Agile Requirements

People are awesome - ALE 2014

Similar to Xp days ukraine 2012

Reversed Test Pyramid - Testing and dealing with Legacy Code

SQALab

The document discusses reversing the tests pyramid for legacy code by starting with end-to-end tests before introducing unit and integration tests through refactoring. It warns that end-to-end tests are long and costly to maintain, so the goal is to refactor code to introduce unit tests from the outside-in. Maintaining a low technical debt by refactoring during slack times can help pay it back over time. The key is to introduce changes gradually through a reversed tests pyramid rather than rewriting everything from scratch.

PHP Mega Meetup, Sep, 2020, Anti patterns in php

Ahmed Abdou

PHP is one of the easiest programming languages to use ever and powers more than half of the internet. With this ease of use, certain common patterns emerge that become harmful. This is especially true when your product or service is not expected to die soon. Some anti-patterns are coding, others are related to operating your service, especially with new docker stacks. We will go over some of the most common pitfalls with a focus on enterprise development.

Agile

Komal2525

This document provides an overview of agile methodology and several agile frameworks. It begins with a brief history of the traditional waterfall model and its limitations. It then introduces the agile manifesto and some core agile principles. Several agile frameworks are described at a high level, including scrum, kanban, extreme programming, and others. Key practices of scrum and extreme programming like iterations, user stories, stand-up meetings, and test-driven development are defined. The document aims to give the reader a broad understanding of agile concepts and some of the most commonly used agile frameworks and practices.

Investing in a good software factory and automating the build process

Nicolas Mas

Services, tools & practices for a software house

Paris Apostolopoulos

Dear compiler please don't be my nanny v2

Dino Dini

Software Development Essential Skills

John Choi

The document discusses essential skills that programmers need versus accidental skills. Essential skills are hard to acquire but long-lasting, including things like managing complexity, writing readable code, and limiting bugs. These skills separate good programmers from bad. Accidental skills like knowledge of a specific programming language are easier to obtain but have shorter usefulness. The document advocates spending time on design, planning, unit testing, discussing solutions with others, and considering alternative solutions rather than just focusing on writing code. Developing essential skills through these practices can help programmers continuously learn and improve over the course of their careers.

Agile Methodologies And Extreme Programming - Svetlin Nakov

Svetlin Nakov

1. Agile development and Extreme Programming (XP) are methodologies that focus on iterative development, collaboration, and adaptability. 2. XP consists of 12 key practices including simple design, test-driven development, pair programming, and small releases. It aims to improve quality, reduce risks, and adapt to changing requirements. 3. While XP works well for some projects and teams, its practices may not be suitable or flexible enough for all situations. Developers should understand the principles behind XP and tailor practices as needed for their specific projects.

TDD - Seriously, try it - Codemotion (May '24)

Nacho Cougil

Ever wondered about the wonders of Test-Driven Development (TDD)? Curious devs, this session is for you! Get ready to dive into TDD and explore its benefits. We'll see the "secrets" behind TDD, its roots, and the rules surrounding it. But that's not all! We'll also uncover the ups and downs of TDD, plus we'll share some tips and tricks... including a live coding session in Java. Get ready to level up your development skills with TDD – more insights, more advantages, and more confidence in your coding adventures! PS: Building tests before production code can sound more fun than it sounds 😉. --- Presentation shared at Codemotion Madrid '24 Feedback form: https://bit.ly/tdd-seriously-try-it-feedback

The Art Of Performance Tuning - with presenter notes!

Jonathan Ross

A somewhat more verbose version of https://www.slideshare.net/JonathanRoss74/the-art-of-performance-tuning. Presented at JavaOne 2017 [CON4027], this presentation takes a practical, hands-on look at Java performance tuning. It discusses methodology (spoiler: it’s the scientific method) and how to apply it to Java SE systems (on any budget). Exploring concrete examples with tools such as the Oracle Java Mission Control feature of Oracle Java SE Advanced, VisualVM, YourKit, and JMH, the presentation focuses on ways of measuring performance, how to interpret data, ways of eliminating bottlenecks, and even how to avoid future performance regressions.

TDD - Seriously, try it! (updated '22)

Nacho Cougil

Have you heard of TDD? Are you interested or familiar with this practice but have never been able to understand it? Join this session to see the benefits of Test-Driven Development (TDD), understand how it works and its benefits. In a more detailed approach, we will see this way of developing software, where our code is always built guided by tests. We will go over some history about TDD, which is the main process we must follow when we work with this mechanic and the rules that surround it. We will also list the main advantages and disadvantages that most developers who practice TDD find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD and see how to do it step by step with an example of a "live" coding session with Java. At the end of the session, I hope that you will have a wider understanding of what TDD is, what advantages it brings, why it is interesting to master it and also that you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code === Presentation (revisited & updated) shared at JDD 2022: https://jdd.org.pl/lecture_2022/#id=78434

Effective cplusplus

Mark Veltzer

This document discusses micro optimizations in C++ and their effectiveness. It begins by defining micro optimizations and noting that the real bottlenecks are often not within one's own code. It then discusses reasons both for and against micro optimizations, noting they can improve performance if used judiciously but also complicate code. The document covers measuring efficiency and complications that arise in C, C++ and higher-level languages. It emphasizes the importance of understanding what languages do behind the scenes and focusing optimizations on the "fast path" code used most frequently.

Agile Development: Key to smart software development

Jerlyn Manohar

The document discusses key aspects of adopting an agile development workflow including having daily stand up meetings to discuss progress, taking an iterative development approach with working software delivered each sprint, and conducting retrospectives at the end of each sprint to improve. Adopting agile practices helps ensure working software is delivered frequently for stakeholder feedback, allows skills and the product to evolve together, and prevents waste through continuous testing.

TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)

ssusercaf6c1

Have you heard of TDD? Are you interested or familiar with this practice but have never been able to understand it? ‌ Join this session to see the benefits of Test-Driven Development (TDD), understand how it works and its benefits. In a more detailed approach, we will see this way of developing software, where our code is always built guided by tests. ‌ We will go over some history about TDD, which is the main process we must follow when we work with this mechanic and the rules that surround it. We will also list the main advantages and disadvantages that most developers who practice TDD find and whether the arguments in favour add up to more than those that subtract. Finally, we will review some good habits and practices when applying TDD and see how to do it step by step with an example of a "live" coding session with Java. At the end of the session, I hope that you will have a wider understanding of what TDD is, what advantages it brings, why it is interesting to master it and also that you will take with you some tricks and good practices to be able to apply them in your day-to-day life when writing code --- Presentation shared at Trójmiasto Java User Group Public group 17th of May '23

TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)

Nacho Cougil

Spaghetti gate

Jon Bachelor

You've officially leveled-up in the world of software development with Visual Studio, and you now find yourself working on projects that are infinitely larger and far more complex than anything you've worked on before. Time to beef up your debugging skills not only to debug, but sometimes just to learn the flow of a given process! Plain old break-points have always gotten you by, but now you quickly run into trickier situations that come close to making your head explode. Come and learn some new debugging tricks & tips to bring your debugging skills to new heights.

CPP01 - Introduction to C++

Michael Heron

TDD and Simple Design Workshop - Session 1 - March 2019

Paulo Clavijo

The document discusses test-driven development (TDD) and simple design. It introduces TDD and some of its core practices, including test-driven development, simple design, refactoring, and pair programming. It provides an agenda for a workshop that will cover these topics over three sessions, including extreme programming (XP), the four elements of simple design, test doubles, outside-in TDD, and SOLID principles. The workshop aims to communicate best practices for using technical practices to succeed with agile development.

Usable Software Design

Alexandru Bolboaca

Functional Prototyping For Mobile Apps

Movel

This document discusses functional prototyping for mobile apps. It begins by defining various types of prototypes like paper drawings, wireframes, and mockups. It then outlines several popular prototyping tools like POP, Balsamiq, Flinto, and Marvel. The document emphasizes that prototyping can save significant money on app development projects by clarifying requirements and creating a unified vision. It also argues for cross-functional teams that include disciplines like security, testing, and operations from the beginning rather than as an afterthought. Finally, it provides some resources for prototyping with Sketch and Framer.

Similar to Xp days ukraine 2012 (20)

Reversed Test Pyramid - Testing and dealing with Legacy Code

PHP Mega Meetup, Sep, 2020, Anti patterns in php

Agile

Investing in a good software factory and automating the build process

Services, tools & practices for a software house

Dear compiler please don't be my nanny v2

Software Development Essential Skills

Agile Methodologies And Extreme Programming - Svetlin Nakov

TDD - Seriously, try it - Codemotion (May '24)

The Art Of Performance Tuning - with presenter notes!

TDD - Seriously, try it! (updated '22)

Effective cplusplus

Agile Development: Key to smart software development

TDD - Seriously, try it! - Trójmiasto Java User Group (17th May '23)

TDD - Seriously, try it! - Trjjmiasto JUG (17th May '23)

Spaghetti gate

CPP01 - Introduction to C++

TDD and Simple Design Workshop - Session 1 - March 2019

Usable Software Design

Functional Prototyping For Mobile Apps

Recently uploaded

Essentials of Automations: Exploring Attributes & Automation Parameters

Safe Software

Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they? Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality. You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.

Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...

Pitangent Analytics & Technology Solutions Pvt. Ltd

Monitoring and Managing Anomaly Detection on OpenShift.pdf

Tosin Akinosho

Monitoring and Managing Anomaly Detection on OpenShift Overview Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices. Key Topics Covered 1. Introduction to Anomaly Detection - Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems. 2. Understanding Edge (IoT) - Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source. 3. What is ArgoCD? - Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices. 4. Deployment Using ArgoCD for Edge Devices - Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD. 5. Introduction to Apache Kafka and S3 - Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions. 6. Viewing Kafka Messages in the Data Lake - Learn how to view and analyze Kafka messages stored in a data lake for better insights. 7. What is Prometheus? - Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices. 8. Monitoring Application Metrics with Prometheus - Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system. 9. What is Camel K? - Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes. 10. Configuring Camel K Integrations for Data Pipelines - Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow. 11. What is a Jupyter Notebook? - Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text. 12. Jupyter Notebooks with Code Examples - Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.

9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...

saastr

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Jason Yip

The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.

Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe

Precisely

Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market. Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.

5th LF Energy Power Grid Model Meet-up Slides

DanBrown980551

5th Power Grid Model Meet-up It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology. Power Grid Model The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services. Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability. Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization. What to expect For the upcoming meetup we are organizing, we have an exciting lineup of activities planned: -Insightful presentations covering two practical applications of the Power Grid Model. -An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024. -An interactive brainstorming session to discuss and propose new feature requests. -An opportunity to connect with fellow Power Grid Model enthusiasts and users.

Dandelion Hashtable: beyond billion requests per second on a commodity server

Antonios Katsarakis

This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).

Leveraging the Graph for Clinical Trials and Standards

Neo4j

Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency

ScyllaDB

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

akankshawande

Driving Business Innovation: Latest Generative AI Advancements & Success Story

Safe Software

Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency. During the hour, we’ll take you through: Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board. Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes. Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI. We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI. This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!

zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...

Alex Pruden

Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security. Paper Link: https://eprint.iacr.org/2024/257

Astute Business Solutions | Oracle Cloud Partner |

AstuteBusiness

"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk

Fwdays

At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience

Programming Foundation Models with DSPy - Meetup Slides

Zilliz

Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors

DianaGray10

Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more. The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications. We’ll discuss and demo the benefits of UiPath Apps and connectors including: Creating a compelling user experience for any software, without the limitations of APIs. Accelerating the app creation process, saving time and effort Enjoying high-performance CRUD (create, read, update, delete) operations, for seamless data management. Speakers: Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP Charlie Greenberg, host

The Microsoft 365 Migration Tutorial For Beginner.pptx

operationspcvita

Choosing The Best AWS Service For Your Website + API.pptx

Brandon Minnick, MBA

Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API? Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose? Which one is cheapest? Which one is fastest? Which one will scale to meet our needs? Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!

Mutation Testing for Task-Oriented Chatbots

Pablo Gómez Abajo

Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots. To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.

Recently uploaded (20)

Essentials of Automations: Exploring Attributes & Automation Parameters

Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...

Monitoring and Managing Anomaly Detection on OpenShift.pdf

9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...

[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...

Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe

5th LF Energy Power Grid Model Meet-up Slides

Dandelion Hashtable: beyond billion requests per second on a commodity server

Leveraging the Graph for Clinical Trials and Standards

Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

Driving Business Innovation: Latest Generative AI Advancements & Success Story

zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...

Astute Business Solutions | Oracle Cloud Partner |

"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk

Programming Foundation Models with DSPy - Meetup Slides

Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors

The Microsoft 365 Migration Tutorial For Beginner.pptx

Choosing The Best AWS Service For Your Website + API.pptx

Mutation Testing for Task-Oriented Chatbots

Xp days ukraine 2012

1. Reversed Tests Pyramid Wiktor Żołnowski @streser http://www.agileszkolenia.pl http://codesprinters.com

2. Agile Coach Troublemaker Who am I? Passionate

3. Can you imagine perfect software?

5. Tests pyramid End to End Tests Functional/Integration Tests Unit Tests

6. It would be perfect to work with perfect software every day...

7. But!

8. Reality...

9. Is...

10. Different!

11. Legacy Code

12. How did we get to this point?

13. It's all because of the money...

14. Technical Debt

15. Sometimes Technical Debt could be considered as something good...

16. Unfortunately temptation of easy making money is huge...

17. People lives in illusion of continuous, fast and low cost development...

18. Forgetting about the Quality...

19. Success in Software Development is something which is not continuous...

20. Success is state that you can achieve but also lose very fast if you can't respond to changes fast enough...

21. So, is it possible to deal with legacy code?

22. Reversed Tests Pyramid End-to-End Tests Functional/Integration Tests Unit Tests

23. - What?!

24. You can't do unit testing when there are no units in your software...

25. You can't do integration tests when there is nothing to integrate...

26. You need to refactor your code so it would be testable...

27. How to refactor without tests?!

28. Now refactor... High level tests gives you courage to refactor your code... ●

29. Now you can refactor and introduce some units into your software...

30. But.. There are few reasons why you shouldn't reverse tests pyramid End-To-End tests are too long...

31. End-to-end tests are difficult to maintain... If we need end-to-end tests we are probably doing something wrong with our architecture...

32. So it's all about reversing back our tests pyramid.

33. Step by step we are introducing new architecture...

34. Remember that creating reversed tests pyramid and reversing it back will take some time...

35. But you need to do this if you want to pay your technical debt back!

36. Few final thoughts... Keep your technical debt as low as possible and try to pay it back every time you can. For example use your slack time for that!

37. Remember - WHY we are doing this?

38. “Leave the world better then you found it”

39. Beware of refactoring just for refactoring! Few final thoughts...

40. Few final thoughts... ● Beware of refactoring just for refactoring! ● Resist temptation to re-write from scratch – history is against you, such projects usually fail. ● Remember to always remove your (duplicated) tests! ● Software quality in many cases could be understood as ability to introduce changes into software! ● Keep your technical debt as low as possible and try to pay it back every time you can. For example use your slack time for that! Resist temptation to re-write from scratch – history is against you, such projects usually fail.

41. Few final thoughts... ● Beware of refactoring just for refactoring! ● Resist temptation to re-write from scratch – history is against you, such projects usually fail. ● Remember to always remove your (duplicated) tests! ● Remember to in many cases could your (duplicated) tests! Software quality always remove be understood as ability to introduce changes into software! ● Keep your technical debt as low as possible and try to pay it back every time you can. For example use your slack time for that!

42. False positive or false negative safety net is even worst than lack of safety net...

43. ● Software quality in many cases could be understood as ability to introduce changes into software!

44. Wiktor Żołnowski www.codesprinters.com Questions? @streser http://www.agileszkolenia.pl http://codesprinters.com

Xp days ukraine 2012

Recommended

Recommended

More Related Content

What's hot

What's hot (8)

Viewers also liked

Viewers also liked (20)

Similar to Xp days ukraine 2012

Similar to Xp days ukraine 2012 (20)

Recently uploaded

Recently uploaded (20)

Xp days ukraine 2012