Skip to main content

Posts

Showing posts with the label Testing

When do we begin Colonoscopy on Code?

At what age should we be inspecting all this code full of colons?  Sometime in 1970's the software world had a lot of colons evolving - 1973 for the popular C Language and its family... That tells us that in 2023 at age 50 the C Language should begin Colonoscopy procedures, yearly.  It's not a pleasant thought but it is the recommendation. Now some of the more modern (non-legacy) code may not need this extreme level of screening... but how would one know - unless one probes around in all those semicolons. Now, many Proctologist have worked to make this procedure less stressful, what have we done in the software community to improve patient outcomes, and satisfaction with our inspection and visualizations? Jokes from the Hole (A Proctologist's Perspective) Shall we work on that?

Coal in your bug tracking stocking this Christmas?

What is your plan for being a better developer next year?  What's the technique that will repay your efforts many fold?  Testing - automated test to be specific.  There are all types of automated testing.  The agile mind set thinks of testing first, not in a reactive manner, but as a preventative and design effort. "For three years, The Container Store has been using application performance management (APM) technology from AppDynamics to locate bugs in the website, target them immediately and fix them. Sometimes there's a slowdown in a particular region. Other times it's from a certain database and often from a single line of code. Just this year, the Container Store upped its contract with AppDynamics, buying more software so the company can test new features before deploying them and minimize the number of live fixes necessary. "We said we want to be more proactive instead of reactive," said A.J. Azzarello, a quality assurance engineer at The Con...

The 21st century definition of TEST

What is the difference between a test and an experiment? I propose that in the 21st century and the realm of software development that these definitions must morph to our needs.  There is little difference in the general definition. Yet many people in quality control or quality assurance departments appear to dislike the word experiment.   Defining actions a person takes to perform a 'test-case' as an experiment appears to rankle feathers.   I find this interesting. Test - (verb) take measures to check the quality, performance, or reliability of (something), esp. before putting it into widespread use or practice. Experiment - (verb) perform a scientific procedure, esp. in a laboratory, to determine something. I would like to define that within the modern software world that the word test have a more specific meaning.  I propose: Test - (verb) a highly repeatable measure to check the quality, performance or reliability of (something), esp. before (somethi...