So I have mentioned Unit Test quite a few times but what are unit test? According to a quick google search "unit testing is a software testing method by which individual units of source code, sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures, are tested to determine whether they are fit for use." Wow that is quite wordy so lets break it down.
I am just now learning how to write unit test for my company. A lot of developers do not use unit test or TDD. Also it is fairly new to the Apple world as Xcode just added testing in Xcode 6 which was released September of last year. So back to our original question. What is Unit test? Well it is testing the basics of a code of you want to test an add function how will you do it. Well you input values then run them through the add function and compare the answer to the correct answer. That is what a unit test does it implements the function and then test if it has the correct output. This is for basic test so that your qa can focus or bigger bugs when usability testing.
Next week I will go over how to write a unit test in the second part of this blog post. Also last week Test Reactor went over Zombies and Zombies in the Code. Talking about what zombies are in pop-culture as well as what QA will need to know about Zombies in the code. This week we will be going over story boarding and what QA needs to know as story-boarding is part of the agile environment. So check it out at TestReactor.com. You can also find us on iTunes and most podcast apps.
QA Hipster is a Quality Assurance Technical Lead for an software company, mostly working with Macs. I have been in the field since September 2013, and have a bachelor's degree in Management Information Services. I started my studies at Iowa State in Software Engineering. I have been working on moving my company forward with the latest QA techniques.