Oz is a behavioral web-ui testing framework developed to reduce test maintenance by using a predictive model rather than a scriptive model when writing tests.
Idea here is to create an "unsafe" version of the proceed to method, proceed_to!. This method allows the router to attempt a recalculation of available routes from a given page in the event that it's not on the first route that the router picked to try. (Think like a GPS where you miss a turn.)
This allows us to write data driven tests that don't need to specify that they went through a given page.
Scenario: Additional information shows if the user doesn't provide enough information
Given I have a REGISTERING_USER_THAT_PROVIDED_TOO_LITTLE_INFO
When I proceed to the Registration Confirmation Page by any means
Then I should have visited the Additional Information Page along my route
And I can see that all the content on the page is correct
Before merging, this should receive a functional example and I plan to add some unit tests as well around the various affected pieces.
I've just posted it in its current state for review
Castone22
commented
5 years ago
closes #41
Idea here is to create an "unsafe" version of the proceed to method, proceed_to!. This method allows the router to attempt a recalculation of available routes from a given page in the event that it's not on the first route that the router picked to try. (Think like a GPS where you miss a turn.)
This allows us to write data driven tests that don't need to specify that they went through a given page.
Before merging, this should receive a functional example and I plan to add some unit tests as well around the various affected pieces.
I've just posted it in its current state for review