Aquality WinAppDriver Template Project

Template for aquality-winappdriver-dotnet library.

Project structure

• Aquality.WinAppDriver.Template - project related part with PageObjects, models and utilities
  • Configuration/: classes that used to fetch project config from Resources/Environment folder
  • Forms/: Page Objects
  • Models/: classes that represent data models of the application under the test
  • Utilities/: util classes
  • Resources/: resource files such as configurations and test data
• Aquality.WinAppDriver.Template.SpecFlow - SpecFlow implementation of the tests
  • Features/: Gherkin feature files with test scenarios
  • Hooks/: SpecFlow hooks
  • StepDefinitions/: step definition classes
  • Transformations/: SpecFlow data transformations

Configuration

settings.json file contains settings of Aquality WinAppDriver library. Additional information you can find here.

allureConfig.json is a part of Allure Report configuration. See details here.

NOTE: Do not store application executable under source control as here. This is done only for demo purpose. For example, you can implement task in your CI system that will download and install necessary version of your application under the test. The delivery of application builds/updates may vary.

Tests execution

Scenarios from feature files can be executed with IDE or with .NET Core CLI dotnet test where you can specify all necessary arguments.

Reporting

Allure Framework is used as a reporting tool. Report data will be placed in {Environment.CurrentDirectory}/allure-results/ folder (you can change it in allureConfig.json file).

Run allure CLI command allure serve "{path_to_allure_results_directory}" to build and open report in web browser. To generate report in CI use corresponding plugin for your system.

License

Library's source code is made available under the Apache 2.0 license.