-
Notifications
You must be signed in to change notification settings - Fork 753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: enable table aliases to be used in SpecFlow.Assist CompareToInstance and CompareToSet methods #1384
Comments
Hi Andreas, |
@Sambafrosch This is not on our backlog at the moment and in the near future. |
Co-authored-by: Emil Tzvetkov <[email protected]>
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
SpecFlow Version:
Used Test Runner
Version number: 3.11.0
Visual Studio Version
Are the latest Visual Studio updates installed?
.NET Framework:
Test Execution Method:
<SpecFlow> Section in app.config
Repro Project
https://github.com/basdijkstra/specflowassist-examples
Feature Description
In #969, the ability to use TableAliases has been added for SpecFlow.Assist methods CreateInstance and CreateSet. However, these aliases are not yet available for the 'return path', i.e., CompareToInstance and CompareToSet. This prevents a user from using the same alias for a property in both directions, which could potentially lead to confusion.
Example (also featured in the repro project):
I have an object Album with an integer property LengthInMinutes:
I want to be able to use both LengthInMinutes as well as the alias AlbumLength in my feature files. I can use the alias AlbumLength perfectly fine when creating an instance of an object from a table using
but when I want to compare this instance to a table specified in a feature file using
the alias AlbumLength is not recognized and I have to use LengthInMinutes instead, causing inconsistency in my feature specification.
The text was updated successfully, but these errors were encountered: