Week 2: Testing Units
Hello readers, I started this week to a very unpleasant surprise. My second monitor in my battle station was missing, and even though its loss wouldn't affect any of my work, i had grown attached to it. Luckily, I was given another within 10 minutes, and the crisis was averted. This last week was spent doing mostly the same thing: creating more unit tests for one class of software that I was given. 
I finally feel comfortable creating these in the code, and I think that I have learned a lot! The hardest part about creating these unit tests isn't actually the tests themselves, it's figuring out what the methods I'm testing are supposed to do... or, what I'm actually supposed to be testing for. With that figured out though, I was pleased to hear that I will not only be able to test software within the next few weeks, but I can move my tests to hardware! This means I get to plug stuff in and play with a circuit board! Pictures, as always, will follow. I hope to see you next week, Chris Varanese
So what exactly are you testing for? This all looks like jibberish to me.
ReplyDeleteI'm just testing various parts of another class to be sure that it does everything it is supposed so. So, I have to test for a lot of things, such as if it is returning the right numbers, if it's setting the right values, or if it is calling the right functions.
DeleteThe monitor went to a better place.
ReplyDeleteThat looks like a lot of work. Props.
and I definitely would love to see pictures of the hardware.
Yeah, I kind of also want to know what you're testing for.
OH NO NOT THE MONITOR! But on a serious note, it's good to hear that you are getting the hang of using DAVE. Have fun with testing on hardware, I hope it goes well!
ReplyDeleteI'm quite sorry about your monitor. I am sure it is dearly missed. I can't wait to hear how your next tests go!
ReplyDelete