16

Nobody Unit Tests.

So it's already 1:15am late night and I am all tucked up in bed watching Roy Oshrove talk on unit testing and ways to write correct unit test. My friend walk in and finds me in bed watching this. He seems surprised as what are you doing ??
I replied it is an interesting talk on unit testing.

He says are you mad? Who the hell does unit testing ?
People out there are spitting on unit test code base. And they don't write unit tests.

Nobody unit tests.!!

I stay calm. I know there is no point of arguing. I said I'll sleep in some time.

And he works as developer, a job that I applied an never got because of connections.

I am optimistic someday I'll find a job that I deserve. The developer world is in danger. !!!

Comments
  • 3
    I think the main misunderstanding about unit tests (and TDD for that matter) is HOW to write unit tests.
    It you start with something like
    testConstructor(), then you are most likely on a wrong path.
    Also, if your unit tests need to start a database server first, then there is definiciones something wrong.

    Unit tests should be:
    - fast
    - specific
    - failable (!)

    And test code should be a first class citizen, too!

    If seen the benefits in practice, so I think I know what I'm talking about ;)
  • 0
    @kgbemployee i second that not because its time consuming and not planned but because the effing client keeps changing every minute detail of the requirements that was originally discussed
  • 0
    @kgbemployee completely agree, but but ..a software services company makes money by building software so if you get an account manager who's only goal in life is to meet his/her sales target (which almost every account manager i have known), then all those contracts, sign offs, frozen requirements goes out the window and you do what the customer asked you to do the last time you met him/her :)..
  • 0
    @kgbemployee lets hope so :)
Add Comment