Overview


Language(s): English, Japanese
Audiences(s): Developers
Technology: Microsoft Visual Studio 2012
Type: Proctored Exam

Exam Topics Covered

The following patterns & practices guide book includes topic areas covered on this exam.

Testing for Continuous Delivery with Visual Studio 2012

Audience Profile

Candidates for this exam are software testers. They manage the process of running tests, creating and monitoring bugs, and managing and mitigating issues that a software organization has in controlling test coverage for project requirements.

The qualified candidate has:

  • a strong understanding of the software testing role.
  • a strong understanding of modern testing practices.
  • the ability to implement testing practices by using Microsoft technologies. 

Credit Toward Certification

Exam 70-497: Software Testing with Visual Studio 2012: counts as credit toward the following certification(s):

Note This preparation guide is subject to change at any time without prior notice and at the sole discretion of Microsoft. Microsoft exams might include adaptive testing technology and simulation items. Microsoft does not identify the format in which exams are presented. Please use this preparation guide to prepare for the exam, regardless of its format.

Skills Measured


Create and Configure Test Plans (31%)
  • Create test plan properties.

    This objective may include but is not limited to: selecting test settings; selecting configurations; defining name, description, area, path, and iteration; selecting test environments; assigning Build to Test Plan (when to assign a build to a plan; compare assigned build to another build)
  • Configure test settings.

    This objective may include but is not limited to: creating multiple test settings; selecting data and diagnostics; setting up roles
  • Define configurations

    This objective may include but is not limited to: managing configuration variables; setting default configurations; adding new configurations; setting configuration state; deleting configurations
  • Create Test Suites.

    This objective may include but is not limited to: creating query-based Test Suites; creating requirement-based Test Suites; creating static Test Suites; copying Test Suites; creating a Test Suite hierarchy; assigning Test Suite states
  • Configure Test Suites.

    This objective may include but is not limited to: assigning Testers; selecting configurations; ordering Test Cases within a Test Suite; setting defaults
Manage Test Cases (34%)
  • Create Test Cases.

    This objective may include but is not limited to: designing Test Cases that have clear and measurable steps; assigning Test Case properties (title, areas and iterations, state, priority, assign to, and automation status); adding attachments and links; adding the Test Case description and history; adding Tested requirements; managing Test Case workflow (state)
  • Create Test Steps.

    This objective may include but is not limited to: adding and removing parameters to and from actions or expected results; adding and removing data; creating repeatable Test actions for using Fast Forward for Manual Testing; creating expected results; adding Test Step attachments
  • Define parameters.

    This objective may include but is not limited to: managing Test Case iterations; creating a parameter variable; renaming parameters; deleting parameters
  • Manage Shared Steps.

    This objective may include but is not limited to: creating Shared Steps; designing Shared Steps that can be reused effectively across different Test Cases; moving Shared Steps; creating Action Recording for Shared Steps
  • Manage requirements.

    This objective may include but is not limited to: reviewing requirements; verifying requirements; verifying all requirements are accounted for; validating Test Coverage
Manage Test Execution (35%)
  • Run Tests.

    This objective may include but is not limited to: running tests with options; creating Fast Forward for Manual Testing recordings; selecting Fast Forward Playback options (all steps, multiple steps); setting Test Run states; validating expected results (add comments, snapshots)
  • Perform Exploratory Testing.

    This objective may include but is not limited to: perform ad hoc Exploratory Testing; exploring by Work Item; generating Test Case from Test; generating bugs from Exploratory Testing; adding screenshots, video, or audio recording
  • Manage bugs.

    This objective may include but is not limited to: tracking bug metrics (bug trends, status); verifying bugs (create Test from bugs); analyzing bug reports; managing bug workflow
  • Use Lab Center.

    This objective may include but is not limited to: creating new environments; creating copies of environments; running Tests on remote environments; executing Test Case in a Lab Center Environment
  • Analyze Recommended Tests.

    This objective may include but is not limited to: selecting the build in use; comparing the current build to a previous build; viewing Recommended Tests; analyzing related Work Items
  • Perform analysis.

    This objective may include but is not limited to: analyzing reports (Requirements-User Stories); analyzing by Test Suite; analyzing by configuration; identifying areas where quality is low; identifying Test Plan status
  • Manage Work Items.

    This objective may include but is not limited to: validating requirements; Work Item relationships (e.g., what it means when a test case is associated with a requirement); creating Work Item queries; performing bulk updates in Microsoft Excel

Preparation Materials


Learning Plans and Classroom Training
Books
Practice Tests

Community


Related Forum Posts

If one of the posts in the following threads helps you answering your question, please vote them as helpful so other community members will find helpful information faster.

Other languages

This article is also available in other languages