network profile
| bio | website | madcoderspeak.blogspot.com |
|---|---|---|
| location | Mumbai, India | |
| age | 32 | |
| visits | member for | 2 years, 2 months |
| seen | May 6 at 15:10 | |
| stats | profile views | 35 |
Developer - I like to build things and see them work. Gimme a good book or a game and I can keep myself out of trouble. Got hooked on TDD-XP-Agile around 2005.. trying to get to the promised land since. Work with C Based languages. Play with Ruby.
|
May 6 |
revised |
Best Development Methodology for One Person? expanded - not a 'link only' answer anymore |
|
Mar 24 |
awarded | Yearling |
|
Feb 26 |
awarded | Caucus |
|
Jun 6 |
revised |
Has test driven development (TDD) actually benefited a real world project? typo : breaks => brakes.. |
|
Jun 6 |
suggested | suggested edit on Has test driven development (TDD) actually benefited a real world project? |
|
Mar 24 |
awarded | Yearling |
|
Dec 23 |
comment |
Does not testing internals entail diligent refactoring and/or rely on developer talent? @MakeMinePanacea - Ok. I think I see your dilemma : my tests are "specs" ; they are not implementation dependent. e.g. If I want a method that sorts, I write a test that feeds in input data sets and verifies output sets. My test would not be different if I satisfied the spec by implementing BubbleSort or MergeSort. Corner-cases can be tested by passing in different input-sets that would cause the internal code to be executed. If you can post such an example, maybe I can reword it OR I end up learning something new. HTH |
|
Dec 16 |
answered | Does not testing internals entail diligent refactoring and/or rely on developer talent? |
|
Sep 29 |
comment |
Offensive programming / coding Funny term - I can think of a few lines I've read in the comments section. Not sure if it relates to defensive programming. |
|
Jul 5 |
comment |
i am “scared” to learn a new language Another way to look at it would be .. what if I'm better at it than C# ? No easy way to answer it apart from just giving it a good try. You don't stand to lose in any case. |
|
Jul 4 |
comment |
Automated Testing: Explaining its Business Value @orangepips - My objection was related to the QA/Dev Exceptions/Happy divide. Unit tests exist to ensure that you're building it right. QA/Acceptance tests exist to ensure that you're building the right system. So all scenarios that are relevant to the business (e.g. the credit card has expired) should be tested by QA before they brand it ready to ship. I recommend automation of acceptance tests - Automate the tedious, routine stuff 80%+. Top that off with some imaginative non-scripted manual testing. |
|
Jul 1 |
answered | Automated Testing: Explaining its Business Value |
|
Jul 1 |
comment |
Automated Testing: Explaining its Business Value @orangepips - I disagree. "QA level"/Acceptance tests should test everything that matters to the user.. i.e. happy paths and alternate scenarios. Unit tests frequently use mocks, stubs and fakes... which means there is a possibility that the happy path unit test passes but when all the components are brought together, the happy path end-to-end test may fail. It is too much of a chance to be left to fate. |
|
Jun 25 |
comment |
TDD vs. Productivity @lurscher - it depends. Usually it is 50% Reflection followed by one of 1. Comment the current failing test and go for some (p)refactoring to be able to write the next test. 2. Go hit the whiteboard. Draw the main classes and see if there is a misalignment of responsibilities or new types that need to surface. 3. Ask for help on the TDD mailing list. 4. Take a break.. and return with a fresh mind. |
|
Jun 24 |
awarded | Good Answer |
|
Jun 24 |
comment |
TDD vs. Productivity @asgeo - can't edit that comment.. the link has picked up a trailing bracket.This should work - goo.gl/dWp3k |
|
Jun 23 |
awarded | Nice Answer |
|
Jun 22 |
comment |
TDD vs. Productivity @Nairoi - Not sure what test runner you are using. I just learned a name for what I wanted to convey. Abstract fixture pattern[goo.gl/dWp3k]. This still requires you to write as many Fixtures as there are concrete SUT types. If you want to be even more concise, look at your runner's docs. e.g. NUnit supports Parameterized and Generic test fixtures (now that I searched for it) goo.gl/c1eEQ Seems like the very thing you need. |
|
Jun 22 |
awarded | Commentator |
|
Jun 22 |
comment |
Do you write unit tests for all the time in TDD? @mcaa - Whatever Steve said + you might set a precedent that it's okay to not write tests. The threshold of what is "interesting enough to test" might keep rising over time... The test above is not much of an effort.. it's hardly 5 lines and in return you get 95%+ peace of mind |
