Starting with a quote ( quote (verb ). "Master Code used by humans who use their right side of the brain more than their left side )
In the spacecraft business no design can survive the review process, without first answering the question—how are we going to test this thing?
—Glen B. Alleman, Director Strategic Consulting for Lewis & Fowler
I was driven into Testing by a split second decision after years of working on compiler optimizations for languages that a few souls on this planet knew. There have been loads of changes to the way I look at development now , than I used to think of when I was a developer. There were quite a few times I knew of kludges that were used in code without guaranteeing safe execution. I knew that they existed but we had to take calls, business decisions and make your boss happy system all across.
The reason for such and such decisions were always the number of decisions a human has to take when there were x number of tests in the system under 'n' number of circumstances and to get a overall green , a shade of red here and there was in consequential. But who would take the load of cleaning the redder sections till 'red grows and makes the red and green combo muddy'.
All in all, a system of soft and hard decisions created the testing environment challenging. Acceptance TDD is the newly used model today in most places where Agile systems needs to be built and even before the testing translates to a real life running monster clipping the fancy wings of the 'enter' happy developer, the devs are on to something new. I have noticed a pattern that the modern software development world is now facing. Development was fast in the 80s and then the 90s gen thought that 80s were slow. Same with the 2010+ gen where things and platforms are changing, developers are moving form platform to platform ( some going back to the roots for performance if the project is there to stay ).
ATDD <-- sounds near to ADD right [ It was ADD that got me started on blogging in the first place ]. With ATDD , we write stories ( in other words PMs define the role of the product , and by the time the product is adhoc tested we are onto the new projects.In this fast pace, we have make a TDD story that is solid enough but flexible on its head to reverse direction at times to manual testing. A smart manual tester will capture bugs that automation can only learn from machine learning process that needs time. I will keep updating the blog with latest tehcnologies that I put my hands on and update here.
Image may be NSFW.Clik here to view.
