Agile Thoughts

Agile Thoughts

By Lancer KindBusinessTechnologyEducationSelf-ImprovementManagement
Download on the App Store

Agile Thoughts episodes

  • 019 A QA Professional Questions Micro Tests and TDD

    Note: this IT radio drama starts with episode 14, Why Devs don’t TDD. Start listening there. 
    Connect
    Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet.
    ​019 A QA Professional Questions Micro Tests and TDD
    Jose: I heard from the other team members plenty about your TDD. Now I’m all about quality but come on! These tests are just testing the code. And I’m already testing the features. So what good is that?
     
    Vanilla: Well, what you do is a lot of manual work. Instead these are automated, and —
     
    Jose: And they are written by developers? How does it make sense for you to write your own tests for code you wrote? Won’t your tests just pass because you want them to?
     
    Vanilla: It’s like this, Unit tests–
     
    Jose: Unit tests? More like Fantasy Unicorn tests. Do you really think you guys will actually make any? And that they will be any good?
     
    Vanilla: Now come on, Unit tests are fast and test the developer’s intent.
     
    Jose: I don’t need any stinking unit tests to tell me developers intent. Every developer’s intent is to do as little testing as possible so they can write features and fix them later. And everyone comes to me complaining that I didn’t catch them all when, after all, my testing schedule is cut in half!
     
    Vanilla: Now see here Jose, in the last 4 days I’ve written twenty unit tests, and you know what, they test every line of code I wrote.
     
    Jose: Every line of code YOU wrote. I bet they are all happy path. Come on! Be honest!
    Vanilla: Now see here Jose–
     
    Jose: The cat’s already out of the bag Pop. I heard the PO talking about how these unit tests don’t even test features. Now how does that make any sense?
     
    Vanilla: They don’t *directly* test the features. Directly, I say! However, they test the code that makes the features work.
     
    Jose: Listen to yourself talk man. You’re raving.
    Vanilla: Come on!
    Jose: Micro or not, developers write tests? Those two things just don’t go together. A skunk don’t change its stripes.
    Vanilla: Now you just hold on there! Do you think that
    0 min
  • 018 TDD gets no Love from the PO

    Note: this IT radio drama starts with episode 14, Why Devs don’t TDD. Start listening there.  Connect Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet. ​018 […]

    The post 018 TDD gets no Love from the PO first appeared on Agile Thoughts.

    0 min
  • 018 TDD gets no Love from the PO

    Note: this IT radio drama starts with episode 14, Why Devs don’t TDD. Start listening there. 
    Connect
    Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet.
    ​018 TDD gets no Love from the PO

    Note: this IT radio show starts with episode 14, Why Devs don’t TDD.  It’s suggested you start there first.  

    Narrator: Vanilla Pop talks to the PO about the team doing TDD.
     
    Horst: How are you Vanilla Pop? Or should I refer to you as simply, rising star of the company? Ja? What is on your mind?
     
    VPop: Sprint planing is tomorrow. I’ve been piloting the practice of TDD for the team and—
     
    Horst: TDD is something about testing, Ja?
     
    VPop: That’s right. Micro testing. So I think I’m ready to teach the whole team how to do this. But it will slow us down a little before it speeds us up.
     
    (Internal voice: slow us down a little? doesn’t he know if this will work?)
     
    Horst: excuse me but Isn’t Jose already Testing the app? Why do you test what Jose is already testing?
     
    VPop: Well it’s different. What Jose does is macro testing. And some of it is manual. You see these automated micro tests only test if the code works, not the feature.
     
    (Internal voice: test code not feature? What is this?)
     
    Horst: excuse me but don’t the tests Jose write, don’t they test the code too? Ja?
     
    VPop: Well yeah, but these tests each test a small piece better and respond nearly instantly when there is a bug.
     
    Horst: Because Jose works too slowly?
     
    VPop: Well no, his tests are slower which means we need to spend time later fixing bugs. And macro tests don’t help us locate the bugs. Only know there exists bugs.
     
    Horst: But if you’re spending time now to write tests for code we are already testing, that sounds like we are over testing. I’d rather you write more functionality and let Jose handle QA.
     
    VPop: It’s not like that. If all the devs do this, we could have zero bugs.
     
    (Internal voice: zero did he say zero bugs? He’s gone mad!)
    0 min
  • 017 The Architect Disses TDD

    Note: this IT radio drama starts with episode 14, Why Devs don’t TDD. Start listening there.  Connect Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet. ​017 […]

    The post 017 The Architect Disses TDD first appeared on Agile Thoughts.

    0 min
  • 017 The Architect Disses TDD
    Note: this IT radio drama starts with episode 14, Why Devs don’t TDD. Start listening there. 
    Connect
    Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet.
    ​017 The Architect Disses TDD

    Note: this IT radio show starts with episode 14, Why Devs don’t TDD.  It’s suggested you start there first.  

    Narrator: Vanilla Pop has had some personal breakthroughs with using TDD and has checked in his code. The problem is, not everyone he needs to work with understand what he’s trying to do.
     
    (A knock. Architect says “enter”. Door closes)
    Architect: I called you to my office to discuss your project.
     
    VPop: Yeah?. Is something wrong?
     
    Architect: I was reviewing the code you checked in and I have some concerns. Do you have a project number for these code changes?
     
    VPop: Yeah. of course I do. It’s written in the checkin comments.
     
    Architect: But… you made code changes here and here, and here and here.
    Oh! And what have we here? Some new files: AggregationTest, LoggerTest, and RaterTest. Nice! You’re adding test automation. I like that, but come on. The functionality for project 555439 is really only in Rater. Did you read this comment block? Wow. Such a beautiful comment block! It expresses in natural language what the code does.
     
    Pop: Sure enough. But—
     
    Architect: You only needed to change one file, but you changed three and added three tests. Mind you, I’m not complaining about the tests. But changing this other code…
    Pop: yeah well—
    Architect:More changes mean more bugs after all. I mean why change Logger.
     
    Pop: When Rater executes, it uses Logger, and logger opens network connections and you know what? That slows down my microtests by about a million percent.
    Architect: seriously?
     
    Pop: I’m not kidding. Normally the logger talks to a service. So it waits f
    0 min
  • 016 Driving under the Influence of FUD

    Note: this IT radio drama starts with episode 14, Why DEvs don’t TDD. Start listening there.  CONNECT Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet. 016 […]

    The post 016 Driving under the Influence of FUD first appeared on Agile Thoughts.

    0 min
  • 016 Driving under the Influence of FUD

    Note: this IT radio drama starts with episode 14, Why DEvs don’t TDD. Start listening there. 
    CONNECT
    Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet.
    016 Driving under the Influence of FUD

    Note: this IT radio show starts with episode 14, Why Devs don’t TDD.  It’s suggested you start there first.  

    Narrator:
    Last Episode, Code Dog tried to discourage Vanilla Pop from trying out TDD. Now let’s see how that affects Vanilla Pop’s ability to experiment with TDD.
     
    (Office sounds, keys clattering, VPop continues doing TDD, while plagued by voices of uncertainty (use echoey voices like in a Hitchcock film.)
     
    VPop:
    How do I do test drive this again? This is kinda hard.
    This test library. I think that’s how the assert is written. Or maybe it’s wrong. How do I know the test is correct?
     
    Voice:
    This test first so so backwards.
     
    VPop:
    Ok. Write the product code now. Huh. I’ve spent so much time writing one test. I really want to spend the rest of the day writing product code. But that’s not TDD right? But what is TDD? What is a correct test? What is life? I feel so uncomfortable! What is happening?
     
    Voice:
    why not write more product code? I mean who writes their test first anyways?
     
    VPop:
    OK, OK. Focus. (Strained) Need to focus. Must focus. Write only a stub for the product code… then run …. the … test. Not going to make it.
    VPop: Uhhn! Click … run … on … test … runner. Did it! Red bar.
     
    Voice:
    Really? How is this a good use of your time? You’re paid too much to write tests.
     
    VPop:
    Huh. OK, write a bit of product code. (tap, tap) Done. A hardcoded solution that will make the test pass.
     
    Voice:
    why not keep writing product code? You don’t need to run the test again. You KNOW it’s going to pass.
     
    VPop:
    Must … run … test. (click) Huh? I got a red bar!??
     
    Voice:
    See? You didn’
    0 min
  • 015 The TDD FUD Spreader

    Note: this IT radio drama starts with episode 14, Why DEvs don’t TDD. Start listening there.  CONNECT Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet. 015 […]

    The post 015 The TDD FUD Spreader first appeared on Agile Thoughts.

    0 min
  • 015 The TDD FUD Spreader

    Note: this IT radio drama starts with episode 14, Why DEvs don’t TDD. Start listening there. 
    CONNECT
    Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet.
    015 The TDD FUD Spreader

    Note: this IT radio show starts with episode 14, Why Devs don’t TDD.  It’s suggested you start there first.  

    (A Code-Dog is typing away, the Agile Thoughts podcast playing in the background. Vanilla Pop enters the room.)
     
    Code-Dog: Well good morning to you Pop. You got in early. It’s only 10am.
    VPop: yeah yeah. I’ve been listening to this podcast and wanted to try some of the ideas out.
    Code-Dog: Whoa! Whatcha cooking up? A test class?
    VPop: yeah! I’m building some micro tests as I build the code and–
    Code-Dog: You what? Did you say write tests *as* you build the code? You mean after you build the code, and only if you’ve got some time left before the Sprint ends.
    VPop: No, I mean I’m writing the test before that. It’s called TDD and–
    Code-Dog: Dude I’ve hear of Test Driven Development and that’s some messed up shit!
    VPop: Well I got this book called TDD by Example, and I’m giving it a go.
    Code-Dog: You remember Instant Nugget? Over in accounting? His boss told the whole team they had to start doing it. And none of them knew how…. so they wrote the tests later and I guess they didn’t make enough because they still haven’t deployed their app.
    VPop: Yeah. That project is a steaming pile of bugs. So yeah. I’m giving it a try in case our manager makes us do it.
    Code-Dog: Nuh uh, there is no way. All the other managers in the company are too scared after that.
    VPop: what did they expect when no one on the team knew how?
    Code-Dog: So that’s how it is huh? YOU’re learning now so they can make us do it later. Man I don’t know… Maybe better you don’t so we can keep things cushy the way they are…
    VPop: You know that last Sprint, I spent most of it tracking down a problem in production? It must have been a code merge that changed that fouled up a Handler class.
    Code-Dog: yeah, that sucked. But hey, everyone understands that you nee
    0 min
  • 014 Why Devs don’t TDD

    CONNECT Visit Agile Thoughts and register to receive free development, analysis, or leadership and management materials and learn to excel at developing software. I’ll also send information on my low cost email courses you can take via the internet. 014 Why Devs Don’t TDD Honestly, doing TDD isn’t that hard, although if you listen to […]

    The post 014 Why Devs don’t TDD first appeared on Agile Thoughts.

    0 min

About Agile Thoughts

From the publisher's feed

In the time it takes to receive a Starbucks coffee, Lancer Kind covers how to consistently release software with zero defects, and how to guide teams and organizations through changes necessary to do Continuous Delivery. The Mandarin edition is at (中文版):