This glossary defines key terms that are used in the Visual Studio Application Lifecycle Management (ALM) Help.
A computer, either physical or virtual, capable of processing information to produce a desired result.
A test performed by a human, usually captured in text or a Word document that lists the steps.
manual test template
A template used by the system to give the user a consistent experience when authoring a manual test.
master project plan
A deliverable of the planning phase for a development project. It consolidates feature team and role plans. The master project plan includes a budget plan, capacity plan, communications plan, deployment plan, development plan, pilot plan, purchasing and facilities plan, security plan, test plan, and training plan.
master project schedule
A schedule that identifies all the project's activities and milestones, consolidating all team and role schedules. The master project schedule is a deliverable of the planning phase.
Degree of process improvement across a predefined set of process areas in which all goals within the set are attained.
The process of combining the changes in two distinct branches. A merge operation takes changes that have occurred in the source branch and integrates them into the target branch. Merging integrates all types of changes in the source branch including name changes, file edits, file additions, and file deletions.
A point on the project schedule at which the project team assesses progress and quality, and reviews deviations in scope and specifications. A project may have many interim milestones for internal use only, which signal a transition within a phase and help divide large projects into workable pieces. External milestones or major milestones typically occur at the end of major phases of work and are associated with the completion of major deliverables. External milestones are the points where the team and customer review work to date and agree to proceed with the project, appear as a task with a duration of zero work units, and are exposed on customer reports.
A line of code that was not executed by a test. See also: hit
Classes used as proxies for gaining greater code coverage in unit testing.
A database that is installed with Microsoft SQL Server and that provides the template for new user databases. SQL Server creates a database by copying in the contents of the model database and then expanding the new database to the size requested.
A folder under the work items node of every Team Foundation project that contains queries defined by, and seen only by, the current user.