{"id":38646,"date":"2016-11-23T22:57:33","date_gmt":"2016-11-24T04:57:33","guid":{"rendered":"http:\/\/nichoblogs.wordpress.com\/?p=342"},"modified":"2016-11-23T22:57:33","modified_gmt":"2016-11-24T04:57:33","slug":"time-to-quality-test","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/time-to-quality-test\/","title":{"rendered":"Time To Quality Test"},"content":{"rendered":"

Humans are not perfect<\/em><\/h3>\n

Humans are not perfect, and since we are the ones doing the programming, a lot of times programs have what\u00b4s known as bugs, or errors(Fun Fact: they are called bugs because way back in times of the ENIAC, what caused problems were literal bugs who crawled to the machine).<\/p>\n

Sometimes bugs can be as disastrous as cracking your program the second you run it and ruin everything you\u00b4ve worked so hard for!!! and other times they\u00b4re not as bad, but either way the best thing to do is spray Raid over them and kill them(please don\u00b4t spread Raid ver your computer, that thing is really toxic).<\/p>\n

\"Resultado<\/p>\n

Software testing is just what it sounds like, to run your own program and see how it works, so you can correct any mistakes you may have made. This is usually made in order to debug your program, or to give it maintenance(which a lot of times \u00b4maintenance\u00b4 means a new bug was discovered). While it may seem easy, it often gives not-experienced programmers(like me) a really really hard time.<\/p>\n

<\/p>\n

This is a huge topic and has a lot of coverage in it, so we\u00b4ll start from the beginning.<\/p>\n

Why do we do it?<\/em><\/h3>\n

Well, first of all, a crash in your program carries a risk of damaging your hardware. Also the people funding or contracting you don\u00b4t want to pay for later debugging, because that is quite expensive. A study from the NIST in 2002 found that this is the cost of debugging at later phases of the development.<\/p>\n\n\n\n\n\n\n\n
Cost to fix a defect<\/th>\nTime detected<\/th>\n<\/tr>\n
Requirements<\/th>\nArchitecture<\/th>\nConstruction<\/th>\nSystem test<\/th>\nPost-release<\/th>\n<\/tr>\n
Time introduced<\/th>\nRequirements<\/th>\n1\u00d7<\/td>\n3\u00d7<\/td>\n5\u201310\u00d7<\/td>\n10\u00d7<\/td>\n10\u2013100\u00d7<\/td>\n<\/tr>\n
Architecture<\/th>\n\u2013<\/td>\n1\u00d7<\/td>\n10\u00d7<\/td>\n15\u00d7<\/td>\n25\u2013100\u00d7<\/td>\n<\/tr>\n
Construction<\/th>\n\u2013<\/td>\n\u2013<\/td>\n1\u00d7<\/td>\n10\u00d7<\/td>\n10\u201325\u00d7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Table taken from NIST Study, 2002<\/h6>\n

As

\"\"<\/div>\n
\"\"<\/div> can see, if they skip just one phase at debugging, it could end up costing 3 or even 10 times more than it would had you noticed them in their respective phase, of course this takes a lot of experience, which is also why it is one of the hardest parts of software development. Also, from a consumer standpoint a lot of times you want to pay for something of good quality, so if a program is not correctly debugged, it may end up decreasing sales.<\/p>\n

All right, I get it…how do I stop it?<\/em><\/h3>\n

There are a number of different ways you can test it.<\/p>\n