TDD and the Terminator: An Introduction to Test-Driven Development

•

0 gostou•210 visualizações

SpringOne 2021 Session Title: TDD and the Terminator: An Introduction to Test-Driven Development Speaker: Layla Porter, Developer Advocate, .NET communities at VMware

Software

@LaylaCodesIt
MICROSOFTMVP

GITHUBSTAR

MK.NETORGANISER

C#LOVER

DEVELOPERADVOCATE@VMWARE

LAYLAPORTER

@LaylaCodesIt
TDDSUCCESSES
•Acceptance Criteria

•Focus

•Interfaces

•Asynchronous development

•Cleaner code

•Safe refactoring

•Fewer bugs

•Increasing returns

•Living documentation

@LaylaCodesIt
Terminator Requirements
Scan subjects and determine if they
require further investigation
Investigate subjects of interest and
determine if they are the target -
TERMINATE!

@LaylaCodesIt
Scan subjects and determine if
they require further investigation

@LaylaCodesIt
When you write tests after coding you
may be writing them to fit your code
and not your requirements

@LaylaCodesIt
RED/GREENREFACTORPATTERN
• Write a failing test

• Write enough code to get the test to pass

• Refactor!

@LaylaCodesIt
public

bool

InvestigateFurther(ISubject

subject)

{

if

(subject.SubjectName.ToLower()

=
=

"woman")

{

return

true;

}

if

(subject.SubjectName.ToLower()

=
=

"girl")

{

return

true;

}

if

(subject.SubjectName.ToLower()

=
=

"man")

{

return

true;

}

if

(subject.SubjectName.ToLower()

=
=

"boy")

{

return

true;

}

return

false;

}

@LaylaCodesIt
public

bool

InvestigateFurther(ISubject

subject)

{

switch

(subject.SubjectName.ToLower())

{

case

"woman":

case

"girl":

case

"man":

case

"boy":

return

true;

default:

return

false;

}

}

public

$public bool InvestigateFurther(ISubject subject) { switch (subject.SubjectName.ToLower()) { case "woman": case "girl": case "man": case "boy": return true; default: return false; } } [TestCase("woman")] [TestCase("girl")] [TestCase("man")] [TestCase("boy")] public void TerminatorShould_Determine_ToInvestigate Further (string subjectName) { var subject = new Subject {SubjectName = subject Name}; var result = _sut.InvestigateFurther(subject); result.Should().BeTrue(); } [Test]$

$public bool InvestigateFurther(ISubject subject) { switch (subject.SubjectName.ToLower()) { case "woman": case "girl": case "man": case "boy": return true; default: return false; } } [TestCase("woman")] public void TerminatorShould_DetermineNot_ToInvestigateFurther() { var subject = new Subject {SubjectName = "T1000"}; var result = _sut.InvestigateFurther(subject); result.Should().BeFalse(); }$

@LaylaCodesIt
WITHGOODPRACTICES,CODEMANAGEMENTBECOMESINFINITELYEASIER

@LaylaCodesIt
TDDFAILURES
•Underestimating the learning curve

•Confusing TDD with unit testing

•Thinking TDD is enough testing

•Not starting with failing tests

•Not refactoring enough

•Not actually doing TDD!

@LaylaCodesIt
IMPLEMENTATIONWITHINYOURORGANIZATION
•Can be controversial and is a significant culture change

•Initial drop in productivity can be disconcerting

•Productivity will go up and reworks reduced

•Increased understanding of requirements and their acceptance criteria

@LaylaCodesIt
IFYOUTAKEONETHINGAWAYFROMTHISTALK...

$@LaylaCodesIt [Test] public void TerminatorShould_Determine_ToInvestigateFurther (ISubject subject) { var subject = new Subject{SubjectName = "woman"}; var result = _sut.InfestigateFurther(subject); result.Should().BeTrue(); } public bool _sut.InvestigateFurther(ISubject subject) { return true; }$

@LaylaCodesIt
Twitter:@LaylaCodesIt

GitHub:Layla-P

Email:laylap@vmware.com
Repo:http://bit.ly/tdd-terminator

Deck:http://bit.ly/tdd-deck

Twitch:twitch.tv/LaylaCodesIt

Yaks:https://bit.ly/shaving-a-yak

Mais conteúdo relacionado

Mais procurados

DevSecCon Tel Aviv 2018 - Value driven threat modeling by Avi Douglen

DevSecCon

ATAGTR2017 Security Test Driven Development (STDD)

Agile Testing Alliance

Improve existing code with confidence, supported by unit tests

Dattatray Kale

Ast in CI/CD by Ofer Maor

DevSecCon

DevSecOps - The big picture

DevSecOpsSg

DevSecCon London 2017: when good containers go bad by Tim Mackey

DevSecCon

ATAGTR2017 Test the REST

Agile Testing Alliance

DevSecCon London 2017: Shift happens ... by Colin Domoney

DevSecCon

DevOps and Continuous Delivery has changed how technology operates and how business is run, but security continues to struggle to catch-up with the velocity of change in this new world : it’s almost a cat-and-mouse game when it comes to spot security holes into code before delivering to production, and traditional manual security assessment just continue to be untenable as a way of working with modern agile teams. The concept of DevSecOps can be the ultimate answer, but unfortunately most articles and vendor pitches about this subject are incredibly superficial, and it’s all about dumping existing/traditional security tools on developers, which adds more complexity and frustration without solving the real problem. “Modern problems require modern solutions” : this talk explains the evolution of security tooling over the last years, and how they must change (or has changed) to match the macro trends and keep up with the shifting threat. As an example, this talk demonstrates how modern “lightweight” code analysis techniques, when combined with secure-by-default frameworks/patterns, can be used to easily detect potential holes within a code base, and provide accurate/fast feedbacks to developers.

Sec4dev 2021 - Catch Me If You can : Continuous Delivery vs. Security Assurance

Abdessamad TEMMAR

DevSecCon London 2017: Threat modeling in a CI environment by Steven Wierckx

DevSecCon

DevSecCon London 2017: How far left do you want to go with security? by Javie...

DevSecCon

How can you squeeze Security into DevOps? Security is often an understaffed function, so how can you leverage what you have in DevOps to improve your security posture? Often the culture clash between Security and Development is even more prominent than between Development and Operations. Understanding the differences in how these functions work, and leveraging their similarities, will reveal processes already in place that can be used to improve security. This fine tuning of tools and processes can give you DevSecOps on a shoestring."

DevSecOps for Developers: How To Start

Patricia Aas

In graph we trust: Microservices, GraphQL and security challenges - Mohammed A. Imran Microservices, RESTful and API-first architectures are rage these days and rightfully so, they solve some of the challenges of modern application development. Microservices enable organisations in shipping code to production faster and is accomplished by dividing big monolithic applications into smaller but specialised applications. Though they provide great benefits, they are difficult to debug and secure in complex environments (different API versions, multiple API calls and frontend/backend gaps etc.,). GraphQL provides a powerful way to solve some of these challenges but with great power, comes great responsibility. GraphQL reduces the attack surface drastically(thanks to LangSec) but there are still many things which can go wrong. This talk will cover the risks associated with GraphQL, challenges and solutions, which help in implementing Secure GraphQL based APIs. We will start off with introduction to GraphQL and its benefits. We then discuss the difficulty in securing these applications and why traditional security scanners don’t work with them. At last, we will cover solutions which help in securing these API by shifting left in DevOps pipeline. We will cover the following as part of this presentation: GraphQL use cases and how unicorns use them Benefits and security challenges with GraphQL Authentication and Authorisation Resource exhaustion Backend complexities with microservices Need for tweaking conventional DevSecOps tools for security assurance Security solutions which works with GraphQL

In graph we trust: Microservices, GraphQL and security challenges

Mohammed A. Imran

#ATAGTR2018 Presentation " Security Testing for RESTful APIs" By Anuradha Raman

Agile Testing Alliance

NYIT DSC/ Spring 2021 - Introduction to DevOps (CI/CD)

Hui (Henry) Chen

Building software today involves more assembly than actual coding. Much of our code is in fact pulled in open source packages, and the applications heavily rely on surrounding third party binaries. These third parties make us more productive - but they also introduce an enormous risk. Each third party component is a potential source of vulnerabilities or malicious code, each third party service a potential door into our system. This talk contains more information about this risk, create a framework for digesting and tackling it, and lists a myriad of tools that can help.

Stranger Danger: Securing Third Party Components (Tech2020)

Guy Podjarny

How To Think Like A Programmer

Kassandra Keeton

Integrating DevOps and Security

Stijn Muylle

DevOps is a cultural shift for more and more organisations, bringing speed and innovation benefits that surpass other SDLC methods. But some of the principles of DevOps aren’t quite aligned with how companies of all sizes will need to incorporate and embed security into this shift. DevSecOps provides a path forward for the transformation and helps companies to shift security to the left so that everyone can take responsibility for it. While automating security testing is an obvious answer to secure applications in the code pipeline, that does not provide 100% coverage until security risks are fully mitigated. Fabian will talk about his journey in making DevSecOps a reality in an organisation. This talk will focus some of the lessons learnt - which includes implementing open source tools to help security team do their jobs better, hacking the culture, whitelisting services, reporting security defects. and also doing Red Team activities.

The Rise of DevSecOps - Fabian Lim - DevSecOpsSg

DevSecOpsSg

In this Practical DevSecOps's DevSecOps Live online meetup, you’ll learn DevSecOps Challenges and Opportunities. Join Mohan Yelnadu, head of application security at Prudential Insurance on his DevSecOps Journey. He will cover DevSecOps challenges he has faced and how he converted them into opportunities. He will cover the following as part of the session. DevSecOps Challenges. DevSecOps Opportunities. Converting Challenges into Opportunities. Quick wins and lessons learned. … and more useful takeaways!

[DevSecOps Live] DevSecOps: Challenges and Opportunities

Mohammed A. Imran

Mais procurados (20)

DevSecCon Tel Aviv 2018 - Value driven threat modeling by Avi Douglen

ATAGTR2017 Security Test Driven Development (STDD)

Improve existing code with confidence, supported by unit tests

Ast in CI/CD by Ofer Maor

DevSecOps - The big picture

DevSecCon London 2017: when good containers go bad by Tim Mackey

ATAGTR2017 Test the REST

DevSecCon London 2017: Shift happens ... by Colin Domoney

Sec4dev 2021 - Catch Me If You can : Continuous Delivery vs. Security Assurance

DevSecCon London 2017: Threat modeling in a CI environment by Steven Wierckx

DevSecCon London 2017: How far left do you want to go with security? by Javie...

DevSecOps for Developers: How To Start

In graph we trust: Microservices, GraphQL and security challenges

#ATAGTR2018 Presentation " Security Testing for RESTful APIs" By Anuradha Raman

NYIT DSC/ Spring 2021 - Introduction to DevOps (CI/CD)

Stranger Danger: Securing Third Party Components (Tech2020)

How To Think Like A Programmer

Integrating DevOps and Security

The Rise of DevSecOps - Fabian Lim - DevSecOpsSg

[DevSecOps Live] DevSecOps: Challenges and Opportunities

Semelhante a TDD and the Terminator: An Introduction to Test-Driven Development

CodeOne Java Debugging Tips

Martin (高馬丁) Skarsaune

As developers we always look for ways to do things faster, better, and automate as much as possible. We write code in top-notch IDEs that have static code analysis, automatic refactoring and so on, we run unit tests, we use CI servers, and issue trackers, we adopt agile practices to get feedback and deliver as fast as possible. As far as code review practice goes, there’s still a lot to be improved, and in this talk I’m going to tell you how you can perform efficient, transparent and useful code reviews.

How to get the most out of code reviews

JavaDayUA

ScalaClean at ScalaSphere 2019

Rory Graves

In pre-production, there’s lots of tools that help optimizing your code: debuggers, CI/CD, load tests, etc. There’s even tools that automatically deploy them into production. Plus, engineers usually have a whole sprint as a time frame. Once you’re in production, things are a bit different and all that convenience is just not there for operators. They need to be able to pinpoint trouble spots within minutes. They have to identify the handful of bad requests out of thousands that allows for reproduction of the problem. And then, they are finally required to hand all that information over to the developers as convenient and as soon as possible. And nothing of that is automated. Performance monitoring, call-tracing and visualization are the concepts any developer should know about to be able to provide as much insight as possible into running systems. This session introduces open-source tools that allow devs and ops to work together much closer. To name just a few: * statsd / collectd * Zipkin * Spring-Cloud Sleuth * and some more For the sake of completeness and to also cover the Enterprise user-space, the main commercial vendors in that space will also be mentioned real quick. After that session, you’ll see new ideas popping up inside your head and already have all the knowledge you need to directly jump into planning and implementation.

Pushing the hassle from production to developers. Easily

Martin Gutenbrunner

Odessa .NET User Group - 10.11.2011 - Applied Code Generation

Dmytro Mindra

Slides from a talk I gave at BSides Knoxville 2019. Abstract: My team loves working on legacy code projects. It's all that we do. That's why a friend of mine reached out to us for some help. His startup was building out a universal API across a very fragmented industry with little to no interoperability or standards. Up until now, integrating with the systems in that industry had been pretty easy, because the companies that built them were willing to help. But now he'd found one that wasn't willing to help. There was no obvious API for getting data out of the legacy application so that it could be exposed via his company's API. A big client for his company was riding on his ability to be able to pull this off. He remembered how much I loved a challenge and how much my team loved legacy code, so he figured we were his best shot. The goal was to be able to read from the application's database. In this talk, I'll cover: * the different approaches that we took * the one we really wanted to try because we thought it would be fun * the approaches that we needed to try before we could attempt the fun one * the excitement that we felt while working on it * the grind toward completion once the big technical hurdle was crossed * the sense of achievement when we got a read-only solution built * the hope that we'd get the green light to start working on a read-write solution * the disappointment when the plug got pulled and we weren't authorized to proceed any further It was a fun journey, and I'd love to be able to share it.

Building a Bridge to a Legacy Application: How Hard Can That Be?

M. Scott Ford

We all know how painful is to be paged at 3 am because the site is not responding. Netflix has made popular the Circuit Breaker pattern, but that is just one of the stability patterns of Michael Nygard's "Release it!" book. On this presentation, you will learn each of the stability patterns found in the "Release it!" book and we will look at practical examples of how they were applied while building a Java based system that integrates and mash up information from more than twenty different sources, some of them quite unreliable. See http://danlebrero.com/2017/08/03/stability-patterns-a-case-study-devoxx-pl-2017-video/ for proper slides

Stability patterns devoxx_pl_2017

Daniel Lebrero

If you are thinking of trying out a NoSQL document database, there are many good options available to Microsoft-oriented developers. In this session, we’ll compare some of the more popular databases, including: CosmosDb, Couchbase, MongoDb, CouchDb, and RavenDb. We’ll look at the strengths and weaknesses of each system. Querying, scaling, usability, speed, deployment, support and flexibility will all be covered. This session will include a discussion about when NoSQL is right for your project and give you an idea of which technology to pursue for your use case.

5 Popular Choices for NoSQL on a Microsoft Platform - Tulsa - July 2018

Matthew Groves

You will learn why naming is really difficult if done right, why coding and style guidelines are crucial, code structuring, exception handling and why other elements of coding often define the tipping point between success and failure of projects. Following the principles of software craftsmanship will allow you to end up with better maintainability and extensibility of your software and the success of the project in the end. All 3 Clean Code presentations provide great value by themselves, but taken together are designed to offer a holistic approach to successful software creation. Why writing Clean Code makes us more efficient Over the lifetime of a product, maintaining the product is actually one - if not the most - expensive area(s) of the overall product costs. Writing clean code can significantly lower these costs. However, writing clean code also makes you more efficient during the initial development time and results in more stable code. You will be presented design patterns and best practices which will make you write better and more easily maintainable code, seeing code in a holistic way. You will learn how to apply them by using an existing implementation as the starting point of the presentation. Finally, patterns & practices benefits are explained. This presentation is based on C# and Visual Studio 2013. However, the demonstrated patterns and practice can be applied to every other programming language too. Note: Moving forwards this presentation will be updated with the latest version of the slides for the last event I did the presentation instead of creating new separate slide decks here on SlideShare. Presentation dates and locations: 2015-06-27 SoCal Code Camp - San Diego, CA 2014-11-14 SoCal Code Camp - Los Angeles, CA 2014-10-18 Desert Code Camp - Chandler, AZ

Clean Code III - Software Craftsmanship

Theo Jungeblut

Imagine that you’re part of a (car) race team. You’re the one behind the screens to control the race and make some tough decisions (like changing the teams strategy). But you don’t have the insights (or metrics) about your car, opponents or even the weather. Sounds painful right? But why are we making this mistake when building our software? Why don’t we implement metrics by default? SLFf4J logging is one side of the story, but we also need to know our application health. That’s where Micrometer comes in! It’s a library which you can use to define your own custom metrics, like: - timers (to check the performance of your microservices) - counters (to check how many times a certain event is occurring) - gauges (to check the current value of a variable) - and many more These metrics are exposed by REST endpoints (JSON) together with Spring Boot actuator, which can be saved into a database like Prometheus or Graphite. And to visualize the data you can use a tool like Graphana. Pretty interesting right? In the demo I will show you how to create such applications using Micrometer, Spring Boot and Cloud Foundry as our platform. Ready to win this race with me? Jump in!

Controlling your race with Micrometer, Spring Boot and Cloud Foundry @Geekle

Ko Turk

The SEO Guide to Migrate International Websites #SMProfs

Aleyda Solís

Migration from IBM DOORS 9 to DOORS Next Generation

Matt Mendell

Real life unit testing tools and practices

Gil Zilberfeld

An Introduction to MongoDB Compass

MongoDB

So, you've made the ferpect Single Page Application. It has all the bells and whistles, and uses all the flashing new frameworks. But how do you know it works, and how do you know that it will continue to work in this world of continuous delivery? This session will try to explain how to do end-to-edn testing of the system, how to test the application server code, and how to test the code the executes on the client.

Testing your Single Page Application

Wekoslav Stefanovski

Many developers would love to work on brand-new, cutting-edge, greenfield projects, never dealing with the mess of unintelligible code someone else left behind. But most of us spend most of our time maintaining existing code, and it is often spaghetti code with no unit tests, no documentation, and, if we are lucky, a comment that says, “Not sure how this works, but it does so don’t touch it.” We need to make changes, but we can’t even figure out what the code is supposed to do. You know your changes will pile on and make it worse. You can’t change the code safely without adding tests, but you can’t add tests without making changes. So how do you tackle this chicken-and-egg problem? You do it slowly and methodically, building a safety net along the way. Join Gene as he talks about helping to maintain and improve code on an infamous software project- it was so bad it made the national news. He’ll explain his approach to breaking the code into manageable, maintainable chunks. He’ll talk about adding unit tests that actually test the code using mutation testing- one of his favorite subjects. If you have inherited a pile of code and want to clean it up into something you aren’t afraid to touch, this talk is for you. You’ll hear about some tools and approaches to help you turn legacy code into code you don’t hate.

How I Learned to Stop Worrying and Love Legacy Code

Gene Gotimer

No one sets out to create crufty code, but too often the pressure to "push it out the door and we'll fix it later" gets the best of us all. Before you know it, it's three projects later, the sun is still shining and you're still getting a paycheck. So where is the incentive to go back and clean under the rug? Poor core quality isn't just a developer problem, either. It bleeds into team moral, deters decision agility, and ultimately prevents team members from getting into flow. Quality code isn't something that requires a complete rewrite either (which is likely impossible), but can be accomplished with style guides, code reviews and a devotion to team investment time. The pressure to ship will always be there, but starting (or maintaining) projects with an agreed upon foundation alleviates developers and designers from making potentially hundreds of decisions each day. This leaves room for the decisions that actually matter. Learn how to transform your team, regardless of your position, into a lean, mean standards machine. Develop a multi-tier style guide, workflow and practices that focus on knowledge and consensus building. Eliminate the mundane decisions and allow the team to focus on its craft.

What is quality code? From cruft to craft

Nick DeNardis

TDD CrashCourse Part2: TDD

David Rodenas

I laugh at people that tell me that Java is slow, heavyweight and cumbersome. Maybe it was true when we had EJB2. I will prove to you that we can develop Enterprise Applications with just a few lines of code that can run in a Raspberry PI. If it runs in a PI, I think we can safely say it would run anywhere! To be able to do it, I'm going to use a new platform called Microprofile. Microprofile optimizes Enterprise Java for a Microservices Architecture and delivers application portability across multiple runtimes. You can use a subset of the Java EE specifications to develop Microprofile applications, with JAX-RS, CDI and JSON-P. Join me for this live coding session and help me spread the word that Java is actually great for the Enterprise.

Lightweight Enterprise Java With Microprofile

Roberto Cortez

I've seen projects with shiny, new code render into unmaintainable big balls of mud within 2-3 years. Multiple times. But regardless of whether it's the code base as a whole that's rotten, or whether it's just the UI and User Experience that needs a major overhaul: the question on rewrite vs refactoring will come up sooner or later. Based on years of experience, and a plethora of bad decisions cumulating into epic failures, I'll share my experience on how to have a code base that stays maintainable - even after years. After this talk, you'll have more insight into whether you should refactor or rewrite, and how to do it right from now on.

Old code doesn't stink - Detroit

Martin Gutenbrunner

Semelhante a TDD and the Terminator: An Introduction to Test-Driven Development (20)

CodeOne Java Debugging Tips

How to get the most out of code reviews

ScalaClean at ScalaSphere 2019

Pushing the hassle from production to developers. Easily

Odessa .NET User Group - 10.11.2011 - Applied Code Generation

Building a Bridge to a Legacy Application: How Hard Can That Be?

Stability patterns devoxx_pl_2017

5 Popular Choices for NoSQL on a Microsoft Platform - Tulsa - July 2018

Clean Code III - Software Craftsmanship

Controlling your race with Micrometer, Spring Boot and Cloud Foundry @Geekle

The SEO Guide to Migrate International Websites #SMProfs

Migration from IBM DOORS 9 to DOORS Next Generation

Real life unit testing tools and practices

An Introduction to MongoDB Compass

Testing your Single Page Application

How I Learned to Stop Worrying and Love Legacy Code

What is quality code? From cruft to craft

TDD CrashCourse Part2: TDD

Lightweight Enterprise Java With Microprofile

Old code doesn't stink - Detroit

Mais de VMware Tanzu

What AI Means For Your Product Strategy And What To Do About It

TDD and the Terminator: An Introduction to Test-Driven Development

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a TDD and the Terminator: An Introduction to Test-Driven Development

Semelhante a TDD and the Terminator: An Introduction to Test-Driven Development (20)

Mais de VMware Tanzu

Mais de VMware Tanzu (20)

Último

Último (20)

TDD and the Terminator: An Introduction to Test-Driven Development