Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. The Insider News
  4. Unit Tests Don't Find Bugs: the Death of QA

Unit Tests Don't Find Bugs: the Death of QA

Scheduled Pinned Locked Moved The Insider News
comtestingbeta-testinghelp
5 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    Terrence Dorsey
    wrote on last edited by
    #1

    DZone[^]:

    TDD's goal is to prevent programmers from introducing new bugs into working code. However, when you're writing code from scratch, your tests won't help you find all the bugs in your code. That's because you can't possibly write tests for all the ways your software will be used (or abused). When I first started doing TDD, I had really good tests, but I was too tired to do much exploratory QA. However, my boss wasn't, and I was very embarrassed to find that my software had lots of bugs. Simply put, he used my software in ways that I hadn't intended.

    Worked on my machine (as long as I didn't actually click anything).

    E F 2 Replies Last reply
    0
    • T Terrence Dorsey

      DZone[^]:

      TDD's goal is to prevent programmers from introducing new bugs into working code. However, when you're writing code from scratch, your tests won't help you find all the bugs in your code. That's because you can't possibly write tests for all the ways your software will be used (or abused). When I first started doing TDD, I had really good tests, but I was too tired to do much exploratory QA. However, my boss wasn't, and I was very embarrassed to find that my software had lots of bugs. Simply put, he used my software in ways that I hadn't intended.

      Worked on my machine (as long as I didn't actually click anything).

      E Offline
      E Offline
      ed welch
      wrote on last edited by
      #2

      They are releasing products with only unit testing? That sounds suicidal

      1 Reply Last reply
      0
      • T Terrence Dorsey

        DZone[^]:

        TDD's goal is to prevent programmers from introducing new bugs into working code. However, when you're writing code from scratch, your tests won't help you find all the bugs in your code. That's because you can't possibly write tests for all the ways your software will be used (or abused). When I first started doing TDD, I had really good tests, but I was too tired to do much exploratory QA. However, my boss wasn't, and I was very embarrassed to find that my software had lots of bugs. Simply put, he used my software in ways that I hadn't intended.

        Worked on my machine (as long as I didn't actually click anything).

        F Offline
        F Offline
        FourCrate
        wrote on last edited by
        #3

        This makes my heart sink. Will we ever find a fool-proof way to find bugs? Not to mention the amount of time it takes to create unit tests.

        L 1 Reply Last reply
        0
        • F FourCrate

          This makes my heart sink. Will we ever find a fool-proof way to find bugs? Not to mention the amount of time it takes to create unit tests.

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          FourCrate wrote:

          Will we ever find a fool-proof way to find bugs

          From a logical perspective; no, not ever. It's also not helpful to aim at something like that, it's more appropriate to expect mistakes.

          Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]

          F 1 Reply Last reply
          0
          • L Lost User

            FourCrate wrote:

            Will we ever find a fool-proof way to find bugs

            From a logical perspective; no, not ever. It's also not helpful to aim at something like that, it's more appropriate to expect mistakes.

            Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]

            F Offline
            F Offline
            FourCrate
            wrote on last edited by
            #5

            You're right.

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups