Preventing Bugs with Unit Testing

Short Description
If you’re employed by a large organization, you may have the luxury of working with a wellstaffed and trained quality assurance (QA) department who will test your code. If you’re in a small shop, you might well do most of your own testing. Either way, you should have some feel for the major types of testing that most software is subjected to, and you should appreciate that part of your job as a developer is to perform your own testing.

Website: www.codertodeveloper.com | Filesize: 2189kb
No of Page(s): 26

Content
…
Every developer knows that software requires testing, but that simple word “testing” encompasses quite a few activities. Here are half a dozen types of testing that you might consider for any given application:
Unit testing. Testing very small pieces of code is called unit testing. These are the units that make up an entire application. These tests focus on very small sections of the code to ensure that those small sections are doing what they are supposed to do.
Integration testing. When different developers are working on different parts of the code, it doesn’t always fit together as it should. The goal of integration testing is to ensure that your code doesn’t break someone else’s code, and vice versa. Integration testing might consist of simply running all the various unit tests to make sure the various bits of code continue to perform as designed.
System testing. When you have a separate QA group, they often focus on system testing: exercising the entire application to see if they can make it fail.
System testing often consists of a mix of automated tests and ad hoc “banging on” the application to see if it can be made to fail. System testing can uncover interactions between components and bugs that the developers never even considered.
…

Get the file Download here