|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
B (Visual Studio Team System Glossary)
This glossary defines key terms that are used in the Microsoft Visual Studio 2005 Team System Help.
The set of work items not yet closed, representing work under consideration or still to be completed.
The original approved plan (for a project, a work package, or an activity), plus or minus approved scope changes. Usually used with a modifier (for example, cost baseline, schedule baseline, performance measurement baseline).
- beta version
A pre-released version of a product that is sent to customers and partners for evaluation and feedback.
- black box test
A test that is based on a component's actual behavior without regard to its implementation.
- bottom-up estimating
A principle of good scheduling. It means having those who do the work estimate the effort, rolling up task-level estimates, and recognizing that experience is the best estimating technique.
To allow a collection of files to evolve in two or more divergent paths. Branching is often used when teams need to maintain two or more similar code bases, for example, when a product is released and work needs to begin on the next version. In source control, branching is analogous to a file system copy operation.
- browser mix
Specifies the probability of a virtual user running a given browser profile. For example: 95% use Internet Explorer 6 and 5% use Pocket IE. Valid only for Web test and coded web tests See: load test scenario, Web test, coded Web test.
- browser profile
A collection of HTTP headers to simulate a particular browser, such as Internet Explorer 6 or Netscape 6.
A type of work item that records a potential source of dissatisfaction with the product. The common name of a work item type for tracking code defects.
- bug allotment
A chunk of development time allocated to fix bugs. An allotment is created by leaving slack in the iteration plan.
- bug convergence
The point at which the rate of fixed bugs exceeds the rate of found bugs. Bug convergence is a visible indication that the team is making progress against the active bug count. It is a sign that the project end is within reach.
A named set of deliverables (software components) produced, usually by compiling, from a discrete set of source versions.
- build acceptance test
See build verification test (BVT)
- build cycle
A part of the internal release cycle. It is the process of adding features, creating test cases for each, stabilizing each feature before building new features, and then releasing for evaluation.
- build error
A message that notifies you of an issue that breaks the build.
- build health
The quality of the as-built software.
- build type
Used to manage the conditions under which a single solution or a set of solutions will be built.
- build verification test (BVT)
Also known as a smoke test. A group of tests used to determine the health of a build at a high level. Typically, these tests exercise the core functionality to help team members determine whether further testing is worthwhile. They are run after the daily build to verify that compilation of source code has been built successfully and is ready for further testing.