SECJ1013-02 TEKNIK PENGATURCARAAN I (PROGRAMMING TECHNIQUE I)

Programming Technique is a tough course. I never thought on taking this course and it is still feel like dream. Even though I have basic in C which I study at  college it is still hard for me to understand the programming language. However, I have to take it as challenges or motivation for me to study hard for this course. Thanks to Dr. Lizawati who teaching and guiding us throughout this semester. I hope one day my programming skills will improved.  

Way back when I first started out learning to program, I did not check my code at all. I'm certain nearly no one does at first. In the commencing it takes so an awful lot intellectual effort just to type out ten lines of code that the compiler is willing to be given that writing extra code to take a look at that code honestly isn't in the cards. I spent a lot of time coding new features into my packages and breaking the entirety else in the process. I would poke and prod at my programs, manually checking out for bugs and fixing the ones that I stumbled across, but it used to be a tedious process. At some point, probably via a aggregate of analyzing about quality practices and getting fed up with guide testing, I located the golden hammer of unit testing. I may want to write more code to test my essential code automatically. I could write packages to routinely generate huge input units to check my code to 100% coverage, or so I thought. It turns out that getting to true 100% test insurance is extra challenging than it first seems. Hitting each and every line of code with automatic checks is sincerely possible, (or at least must be if there may be no dead code) however it truly is only 100% control route coverage. To get a hundred percent program state coverage—testing every enter combination and each program state transition—would efficaciously take an eternity, if no longer in take a look at improvement time, at least in take a look at run time.

Puan Lizawati Binti Mi Yusuf