|
|
|
Use this tool to learn about websites, specifically the one you just entered.
If you find some aspect of it inappropriate it is not our fault.
If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Submit your site to major search engines within 48 hours.
Find out if your site has been cataloged by top search engines for only $8.99.
Below you will see site info taken directly from the URL you entered in real time. This is also known as our URL Breakdown tool and can be used independently of our site info tool.
Scott White's Distillery: NUnit Best Practices
This is just a sample of the content found on this website. Please visit the website to read the entire page.
"skip to main
skip to sidebar
Scott White's Distillery
Technology refined, distilled and dispensed.
Thursday, May 08, 2008
NUnit Best Practices
Programming is not just an art, not just a science, but a discipline. Part of what we all know we should be doing includes solid unit testing. Below is my list of best practices, feel free to comment and add others I enjoy feedback. Create a separate assembly for your test fixtures i.e. don't be lazy and put your test fixtures in the same assembly as the application code) Create a bin folder per solution and place nunit.framework.dll in there Each project should copy their binaries to the solution bin folder. Your Post-Build event should look like this: copy $(TargetFileName) "../../../bin/" Categorize your test fixtures such as DAO, ETL and BusinessRules. This will let you test pieces of your application more easily: [Category("ETL")] Once you have the basic interface of a class written, it is time to write your unit test for it. Even though it will fail it will at least serve as a place holder to go back to as well as serving as a test for when things are working Make sure each test is atomic. Therefore if you are inserting data into a table and you know say CustomerName must be unique, then the second time you run your test it will fail because of uniqueness. For this reason have your persistence tests be all inclusive, include an insert, update and delete. Put your delete code into a finally so that it is always executed regardless of if the other test"
....
read entire page
|
Links to Pages on Other Domain Names
|
|
