Share via

R (Visual Studio Team System Glossary)

  • Article

This glossary defines key terms that are used in the Visual Studio Team System Help.

  • RAISERROR statement
    A Transact-SQL (T-SQL) statement that displays an error message and sets the @@ERROR automatic variable without changing the flow of the procedure. You can use RAISERROR statements to return test results from database unit tests.

  • rank
    To give a unique cardinal position to each entry, as in stack rank. See prioritize.

  • regression
    The reappearance of a previously fixed problem.

  • regression test
    A test that is run after the daily build to verify that compilation of source code has been built successfully.

  • related link
    A Team Foundation link between two work items.

  • release
    A build promoted for use or deployment. A release can be internal and used for further testing or external and released or deployed.

  • release candidate
    A version of a build that has been tested and is ready for release.

  • report
    Information produced from the metrics warehouse of Visual Studio Team Foundation.

  • request
    HTTP requests that make up a Web test and are displayed in the Web Test Editor as a tree structure.

  • request tree
    The tree of nodes that contains HTTP requests (URLs) in the Web Test Editor.

  • requirement
    (1) A condition or capability needed by a user to solve a problem or achieve an objective. (2) A condition or capability that must be met or possessed by a product or product component to satisfy a contract, standard, specification, or other formally imposed documents. (3) A documented representation of a condition or capability as in (1) or (2). [IEEE 610.12-1990]

  • required fields
    Fields with rules. In practice, the designer of a work item type will identify a field that must be filled in with a range of values.

  • requirements analysis
    The determination of the functional and performance characteristics of the solution based on analyses of customer needs, expectations, and constraints.

  • responsibility matrix
    A document that explicitly calls out the individual team members who are tasked with executing, reviewing, and approving work packages within a project.

  • Results List
    The table or grid in the UI that displays the list of results from a work item query.

  • Results view
    The Visual Studio document window that contains both the results list and the work item form. Results view helps you quickly define and run your own queries.

  • rig
    A group of computers used to generate simulated load for testing. This group consists of a controller and agents, which are collectively called a rig.

  • risk
    A type of work item, recording a possible event with an undesirable outcome. Risks must be identified, assigned, and if the impact is probably and really undesirable, mitigated.

  • risk analysis
    The evaluation, classification, and prioritization of risks. Risk analysis includes quantitative assessments, which measure the probability and consequences of risks and qualitative assessments, which prioritize risks' effects on project objectives.

  • risk management
    A proactive, formalized process for decision-making and taking action to continuously assess what can go wrong, assess and quantify the identified risks, determine what risks are important to address, implement strategies to deal with those risks, and monitor the status of risks and mitigation activities.

  • risk mitigation
    Reducing the probability and/or impact of a risk to an acceptable level. Risk mitigation is not risk avoidance. Action may be taken to reduce the probability or impact of a risk, transfer the risk to another party, or avoid the risk entirely. A given risk may have several, one, or no mitigation actions attached to it.

  • risk statement
    A condition-consequence statement that helps to clearly articulate risk by expressing a causal relationship between a real, existing project state of affairs or attribute, and a potential, unrealized other project state of affairs or attribute.

  • risk trigger
    Indications that a risk has occurred or is about to occur. They sometimes are called risk symptoms or warning signs. Triggers may be discovered in the risk identification process and watched in the risk monitoring and control process.

  • risk-driven scheduling
    A principle of good scheduling that prioritizes tasks based on the level of risk involved and prioritizes features based on their importance to key stakeholders.

  • role
    1) A group of activities normally (but not always) performed by one person and often implemented with a security group. Often, one person may play multiple roles. 2) In Domain Specific-Language Tools, a representation of one side (the source or the target) of a relationship. Role properties include its multiplicity and its role player

  • rollout plan
    The plan for delivering an external release. This plan includes all of the elements that must be put in place for acceptance in the marketplace, operations, or to a customer.

  • rough order of magnitude estimate
    An estimate done without detailed costing, or based on initial or incomplete data. Typical categories are 1 - 3 days, 3 - 10 days, or greater than 10 days. A rough order of magnitude estimate establishes an approximate cost for a scenario or quality of service requirement.

  • run configuration
    Settings that are stored in a run configuration file and that impact the runtime environment of a test run.

  • run query
    A command to run a work item query.

  • run settings
    A set of properties that influence the way a load test runs, for example, test duration and description could be specified in the run settings.