SpecFlow structure added and initial accessibility test created #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR adds SpecFlow to the
Web.Tests
project along with an initial accessibility test on the homepage.Major changes
Axe Core
,Fluent Assertions
,Selenium WebDriver Chrome
, andSpecFlow
packages added toWeb.Test
.Features
directory with respectiveAccessbilityTests.feature
file containing accessibility scenario and test steps.Steps
directory with respectiveAccessibilitySteps.cs
step definition file containing code for test steps.Hooks
directory with respectiveSpecFlowHooks.cs
for setting up and tearing down the web app and the WebDriver.build.yml
updated torun-on: windows-latest
to be able to run Selenium.ToDo
Next round of work to possibly include the following:
.exe
inSpecFlowHooks.cs
- is there a better way to run the app?Headless
et al.AccessibilityOptions.cs
as per SD test project.