🖋️
QualityMate
  • QualityMate
  • Getting Started
    • Introduction
    • Why QualityMate
    • Architecture
    • Supported Web Browsers
    • Glossary
  • Components
    • UI Player
      • Basic Concepts
      • UiPlayer
      • MSTest Integration
      • Samples
        • QualityMate Sample Desktop
        • QualityMate Sample Web
        • QualityMate MSTest Integration Sample Desktop
        • QualityMate MSTest Integration Sample Web
        • QualityMate Integration with Test Frameworks
        • Web Authentication Sample
      • QualityMate Project Template
    • UI Recorder
      • Basic Concepts
      • Setting Up the Recorder
      • Validating an Element
      • Generating QualityMate Solution
  • Tools
    • File Comparators
    • Image Processor
    • Project Merger
    • Test Case Generator
      • Filters
      • Rename Recorded Controls
  • Basic Concepts
    • Page Object
      • Work Guide
    • Controls
      • Control Types
        • Generic Types
        • Desktop types
        • Web Types
        • WebMap types
          • Kendo PowerBuilder
          • Kendo WinForms
          • Kendo Silverlight
      • Interactions
        • SendKeys
        • Validate
    • Selectors
      • Selectors in Code
      • Default Selector
      • Shared Selector
      • Selectors Category
        • CSS Selector
        • XPath Selector
        • Image Selector
        • Frame Selector
      • Identifying Selector
        • Identify for Windows Desktop
        • Identify for Web
  • How to Guides
    • Setting Up the Configuration
      • Parameters
      • Context
      • Loading External Data
    • Awaiting for the Application
      • Busy Loaders
      • Retries
    • Defining Controls
      • Extending Controls
      • Control Slice
      • Control Collection
    • Logging on Tests
      • QualityMate Reports
      • Logging
  • Help
    • Best Practices
      • Environment
      • Tests
      • Page Objects
      • Validations
      • Interactions
      • Image Comparisons
    • Known Issues
    • Continuous Integration
      • Agents Session
    • Upgrading QualityMate
      • From version 7 to version 8
      • Previous Versions
      • How to switch from TestFeature to UiTest
    • VS Test
      • Command Line
      • Generate Reports
  • API
    • Control Interfaces
      • IButton
      • ICheckBox
      • IComboBox
      • IControl
      • IControlSlice
      • IDateTimePicker
      • IElement
      • IGrid
      • IGroupBox
      • ILabel
      • IListBox
      • IMenu
      • INumericUpDown
      • IPageObject
      • IProgressBar
      • IRadioButton
      • IRadioButtonGroup
      • ISplitButton
      • IStatusStrip
      • ITab
      • ITextBox
      • IToggleButton
      • IToolBar
      • ITreeView
    • Behavior
      • ICheckableControl
      • IList
      • ITextControl
    • Enums
      • ClickType
      • KeyModifiers
      • MouseButton
  • Changelog
    • Changelog
      • Version 8
      • Version 7
      • Version 6
      • Version 5
      • Version 4
      • Version 3
Powered by GitBook
On this page
  • When to use it?
  • Execute
  • Configuration from Runsettings file
  • Report files are attached when the test fails.
  • How to use UiTest?

Was this helpful?

  1. Components
  2. UI Player

MSTest Integration

PreviousUiPlayerNextSamples

Last updated 3 years ago

Was this helpful?

UiTest is a class linked with MSTest and makes it easy to use the UiPlayer with MsTest. It is convenient when creating test cases using MSTest as the Test Framework.

When to use it?

When you want to take advantage of MsTest's reporting.

This integration incorporates some other MsTest features that make test cases development easier.

Execute

The way to tell QualityMate to perform the wanted steps is through the Execute method. It receives an containing the steps. Additionally, a can be passed to it.

This method is like inside , but is integrated with some MSTest features. Resulting in the following advantages:

Configuration from Runsettings file

You have two options for passing configuration to QualityMate, using a runsettings file or a provided to the Execute method.

This is what a basic runsettings looks like:

<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
    <TestRunParameters>
        <Parameter name="Technology" value="Desktop" />
    </TestRunParameters>
</RunSettings>

This is how it is passed to the Execute method:

UiPlayerConfiguration configuration = new UiPlayerConfiguration()
{
    Technology = Technology.Web
};

this.Execute(this.ExecuteSteps, configuration);

Note the following considerations:

  • If no configuration is provided, an exception is thrown indicating that the required parameters are needed. You can check the required parameters in this article.

Report files are attached when the test fails.

When the test fails the Log file and the screenshot of the last performed step are attached to the MsTest report. Those can be found at the end of the VisualStudio report as follow:

The attachments can be found at: {OutputPath}\{yyyy-MM-dd_HH-mm-ss}\{TestName}\

How to use UiTest?

If you're working on Visual Studio, information on how to load the runsettings can be found .

If you provide both configurations, they are merged into one. Whenever they have overlapping parameters, will take precedence over runsettings

You can use the UiPlayer with the NuGet Mobilize.QualityMate.UiTesting.MsTest. For more information on how to use the UiPlayer, follow this .

here
link
Action
UIPlayer
UIPlayerConfiguration
Execute
UIPlayerConfiguration
UiPlayerConfiguration