You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, first, thanks a lot for Spinach, it is a wonderful tool to work with.
This issue is a feature request.
I would love to have the ability to add the keyword "Expected" in the .feature definition under any steps. Our auditors requires us to be extremely explicit about what our automated tests do and it can be a pain to maintain the documentation of what test does what including the expected results. One way I managed to get around that is to use the hooks architecture to generate the file they expect. This allowed me to have the scripts kinda self-generate the documentation. The only part I am lacking at this point is the "expected results" for each step.
The way I see this could be used is in the "feature" files, kinda in that fashion (here's a pseudo version):
@web_test
Feature: Web_test
In order to test the web application
As a user
I want it to access the web application and execute a series of action
Scenario: User access the Web Application
Given I have test properties defined
Expect Values used are valid
And I have logged in to a zone
Expect to log in successfully
When I click the About box information
Expect Information box to be displayed
Then Validate the Application version displayed
Expect the Application version to match the expected value
I understand that adding the "expected" keyword wouldn't bring much functionality to Spinach itself, but this would help a lot in my work.
I would understand if this is declined, if that is the case, is there a way to achieve something similar in the current situation?
Thanks!
The text was updated successfully, but these errors were encountered:
Hello, first, thanks a lot for Spinach, it is a wonderful tool to work with.
This issue is a feature request.
I would love to have the ability to add the keyword "Expected" in the .feature definition under any steps. Our auditors requires us to be extremely explicit about what our automated tests do and it can be a pain to maintain the documentation of what test does what including the expected results. One way I managed to get around that is to use the hooks architecture to generate the file they expect. This allowed me to have the scripts kinda self-generate the documentation. The only part I am lacking at this point is the "expected results" for each step.
The way I see this could be used is in the "feature" files, kinda in that fashion (here's a pseudo version):
I understand that adding the "expected" keyword wouldn't bring much functionality to Spinach itself, but this would help a lot in my work.
I would understand if this is declined, if that is the case, is there a way to achieve something similar in the current situation?
Thanks!
The text was updated successfully, but these errors were encountered: