Build Validation Tests (AKA BVTs)

Topics: Developer Forum, Project Management Forum
Coordinator
Nov 7, 2007 at 12:59 AM
Edited Nov 7, 2007 at 5:51 AM
We need to have a minimum set of tests that should be run before each checkin. A way to achieve this without a lot of investment in test tools is to document a set of manual steps. I decided to take a crack at this for my recent patch and I thought I'd start a discussion on what should become the "normal" BVTs:

Build BVT
Perform a full build from the root using nmake. (Normally I'd require that this build with no warnings, but the code is far off of this right now). I've filed SLK Build has warnings

Fresh BVT
Perform a Fresh Install.
Upload a document to the document library.
Assign document to self.
Begin assignment.
Resume assignment.
Complete assignment.
Check status on the My Assignments web part.

Upgrade BVT
Perform an install of the previous release.
Upload a document to the document library.
Assign document to self.
Upgrade to the new build.
Check the assignment to make sure it still looks good.
Begin/Resume/Complete assignment.
Check status.
Create a new assignment to self.
Begin/Resume/Complete assignment.
Check status.