Make use of our custom paths
Reported by baphled (at boodah) | July 13th, 2010 @ 09:51 AM | in 0.8.2
At present a lot of our steps are using custom definitions for steps which could be covered with our custom paths, to resolve this we should go over through all of our steps and refactor them to make use of our path based step definitions.
Comments and changes to this ticket
-
baphled@boodah.net July 13th, 2010 @ 10:32 AM
- State changed from “new” to “open”
- Milestone order changed from “28” to “0”
All steps that use the step command, should be refactored to use our paths.
-
baphled@boodah.net July 13th, 2010 @ 10:34 AM
We'll refactor all of our steps which use the word visit to now use the goto step definition
-
baphled@boodah.net July 16th, 2010 @ 06:32 PM
Refactored all plain steps to use the path_to, will need to do the same for our enhanced features and finally remove all instances of visit that are no longer needed. Ideally we will remove all now but it may be a case of waiting until we have cleaned up the other parts of our steps first.
-
baphled@boodah.net July 16th, 2010 @ 08:59 PM
All scenarios should be using the path_to based steps.
Next step is to remove all other steps that use the visit command.
-
baphled@boodah.net July 16th, 2010 @ 11:37 PM
- Milestone order changed from “10” to “0”
All visit based steps are now removed.
-
baphled@boodah.net July 16th, 2010 @ 11:37 PM
- State changed from “open” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bridging the gap between clients and developers
baphled@boodah.net