Survey Results
|
|
 |
|
Those sound like a description of me … once upon a time.
Best record: 36 hours from description of requirements to completion of project (no sleep). Deadline was 48 hours – you would think I would have received a bonus for that one, especially since I had not been hired to write software and I was sick. All I received was a lecture from my doctor for doing something so stupid. The company managed to get a contract worth something in the neighborhood of 100k per month, and the general manager received a bonus (Go figure).
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
|
|
|
|
|
|
Just to make it clear, I don't think that the intention of the question is whether we unit test our code using a formal framework such as nUnit. A lot of times I find it simpler to use Debug.WriteLine / Console.WriteLine / Trace.WriteLine or to simply view the output on the screen to unit test my code that I know won't change much (or at all). Other times I may opt to use a formal unit test using nUnit where it makes sense. With this clarification, I believe that most people unit test their code and the stats here may not be correct due to people confusing unit testing with writing / executing formal tests.
Muhammad Haroon
Thoughtful discussions about software design, development, and management, using Microsoft and related tools and technologies.
|
|
|
|
|
/signed 
We don't suffer from insanity, we enjoy every minute of it!
|
|
|
|
|
C# Genius wrote: Re: Unit Testing Not Equal To
I wrote that I never unit test. As I never use any formal unit test suite, however I do have a built in log system (in all my applications) that records every error, warning, outputs values... I also do have some test routines for some of my lower level code that will yell if they are get the wrong result for that case but this is only for a small fraction of the code and does not appear to be at as low a level as unit tests.
John
|
|
|
|
|
Most of the problems come from house-of-cards apps built long ago by others.
Anything new gets tested.
He was a snowflake, like other "unique" snowflakes, falling down, getting stepped on, and pushed aside to disappear.
|
|
|
|
|
Never mind the official title, who could (or would) build an app without testing the methods as they go along?
I suppose one could dump out 60,000 - 70,000 lines and then expect it all to work, but it would seem to be natural to test the all of its several parts, if for no other reason, then to fein sanity.
Balboos
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
|
|
|
|
|
depends what you class as testing?
i know people who test every function, spend ages on each function ensuring that its 100% functional and covers all possible errors and handles them.
others will just hack the code out hit (f5'run') fix syntax bugs and compiler bugs then says its alright. sure it works but isnt going to be stable.
myself i try to do the first one but when in a team its very hard, even if your the boss and you make sure that your dev's know they should do proper coding and testing someone will miss something just due to rushing or hacking code out.
thats why we have QA testing team who i make sure i dont get emails from lol
|
|
|
|
|
I could not agree more! I always ran my own tests constantly while building applications even before I knew what the names of the different testing types where. The best person to test the individual pieces of code is the developer of that code. Of course as a matter of pride, I do my best to avoid any errors in my code and am more than happy to let someone else try to break it. If there is something wrong, then I want to know no matter who finds the problem.
Those who try to hide problems are fools and only hurt themselves in the long run.
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
|
|
|
|
|
My younger brother spends much of his free time working on his house (go figure?). Anyway, there's an old adage he quotes which can be applied to doing testing as one goes along:
Measure Once - Cut Twice.
- or -
Measure Twice - Cut Once.
The irreversability of the cutting in the physical world may, perhaps, be related to the brown stains on ones reputation when their buggy application falls apart because ego precluded testing one's own code.
Another somewhat wise saying (am I going to get a reputation for this?):
"If you can't find the time to do it right the first time . . . how are you going to find the time to do it again?"
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
|
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Rant 
Admin
Submit an article or tip
Post your Blog
