Project acceptance

[Will Anderson]

Good morning everyone,

There are a couple stories queued up in the Pivotal Tracker project for capybara-accessible (http://bit.ly/1855tf9). How should we go about their acceptance?

As a product person, I would want to verify that tests are appropriately passing/failing/running on a controlled environment where we understand what is expected to pass or fail with each capybara-accessible improvement. We don't have that, at the moment, so we've been relying on running the gem updates on our local projects.

Does that local acceptance feel good enough for the group or should we invest in a simple site on which to run acceptance testing?

Regards,

Will

[Cameron Cundiff]

We've seen more than one regression when testing locally only, so that needs improvement.

It may make sense to investigate how other gem maintainers integration test the actual installation process.

--
You received this message because you are subscribed to the Google Groups "capybara-accessible" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capybara-access...@googlegroups.com.
To post to this group, send email to capybara-...@googlegroups.com.
Visit this group at http://groups.google.com/group/capybara-accessible.
For more options, visit https://groups.google.com/groups/opt_out.

[Will Anderson]

In addition to the technical side of acceptance, who should do the acceptance for the stories that are being completed?

--
Mobile: 917-330-9016

[Cameron Cundiff]

We may want to do internal pull requests with mini code reviews to get merge signoff. That would be a good time to do acceptance on technical stories.