AmosFiveSix.com

I'm just starting to look into Unit Testing and here are some introductory things I found.

Stack Overflow: What is unit testing?
http://stackoverflow.com/questions/1383/what-is-unit-testing

Stack Overflow: What are good Unit Testing examples in C#?
http://stackoverflow.com/questions/2101/what-are-good-unit-testing-examples-in-c

Stack Overflow: .NET Unit Testing packages?
http://stackoverflow.com/questions/1760/net-unit-testing-packages

TestDriven.net: The Zero Friction Unit Testing Add-In for Microsoft Visual Studio ($)
http://testdriven.net/

NUnit Quick Start
http://www.nunit.org/index.php?p=quickStart&r=2.4.8

NUnit Best Practices - Scott White's Tech Blog
http://scottwhite.blogspot.com/2008/05/nunit-best-practices.html

.NET Projects: Unit Testing with NUnit
http://grantpalin.com/2008/06/08/net-projects-unit-testing-with-nunit/

It's been a long and winding road to objects and classes in JavaScript for me. Below are some of the articles that helped me on the journey.

• Inheritance Revisited on Mozilla Developer Network (revision from 6/26/2011)
• What's the best way to define a class in javascript on Stackoverflow
• Object Oriented Programming in JavaScript
• How to Write Maintainable OO JavaScript Code
• Functional vs. Object-Oriented JavaScript Development
• Prototypes and Inheritance in JavaScript
• Constructors considered mildly confusing
• Objects, event handlers and "this" in javascript
• JavaScript Namespacing
• JavaScript, 5 ways to call a function
• Closures are not complicated
• Introduction to the JavaScript Module Design Pattern

SharePoint document libraries provide a number of advanced document management features. Here is an overview I put together for SharePoint 2007.

One thing to keep in mind is that some features, such as Check Out, Version History, Draft Versions and Content Approval, are turned on or off for the entire document library. For example, it is not possible to have only certain files or folders within the library use version history while others do not. You need to create separate document libraries if you need different features used with different documents. For example, you may want one library for your more important documents that requires check out, content approval and version history, while you have a second library for "every day" documents that do not require any of these features.