Activity (RSS)

All visit based steps are now removed.

All scenarios should be using the path_to based steps.

Next step is to remove all other steps that use the visit command.

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 n...

Removed all visit based steps, as they are no longer used.

Once we have cleaned up all our visit based steps we'll go over our other steps to make them more flexible, removing all duplicate and unused steps

Done the same for the project, steps and stories features.

Added a new form based helper to help us fill in our form with duplicate data, this primarily will be...

The basic validations are being covered by form_validations.feature. It would be nice if we moved the error messages to our locale file but it is not essential ...

Although our selenium scenario are working individually we still need to get the working consistently when ran as a collective.

The following scenarios need to ...

Issue seems to be resolved with the latest version of cucumber and rspec, not quite sure how this was fixed but modified the enhanced settings to use db_cleaner

Refactored the features feature file and its associated steps, in turn creating form helper which helps us to fill in our form, will need to do the same for the...

Added wrappers for filling in our basic forms, This has already been done in a separate branch but was essential to getting our scenarios passing in this one. W...

Now created acceptance tests for the following features:
ordering button
info and summary headers
flash messages
hover sidebar

Will need to work on pagination a...

Refactored path and tested all related scenarios.

We'll refactor all of our steps which use the word visit to now use the goto step definition

All steps that use the step command, should be refactored to use our paths.

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...

Centralised too_short based error messages to our locale file, will need to do the same with the other error messages and cover these with specs.

Implemented change

This is not essential so will move it to another milestone.

We have neglected to document any of the application up until now. This will need to be worked on to help us get an understanding of what functionality.

Will hold this back for another milestone, possibly 0.8.2 if we have enough time.

The functionality could definately do with some improvement but it is not esse...

Moved as not essential to this milestone

In some cases are feature file content changes but we have no way of tracking these changes. To solve this we will add revisions to our features.

Ideally we wan...