[sf-perl] Managing Perl Projects
frimicc at gmail.com
Mon Mar 25 15:45:10 PDT 2013
For automated interface (Web GUI) testing, Polyvore is using a combination of tools:
If you're doing something that doesn't have a Web GUI, I'm not sure where you would turn.
For our test environment we have a single script that sets up everything for the tests: creates a local instance of MySQL, populates initial data, initializes Selenium, and returns the important connecting information (port numbers, for example) so that the actual tests can use them. This script runs before the tests run every time (automatically in Jenkins) so that each test run has a blank slate.
For testing non-blank-slates, developers don't run the setup script every time, so we get old testing cruft in our systems. That way the automated tests don't break because of it -- our test runs do and we can fix things before committing them.
It's a pretty cool setup, I must say.
-- Mike Friedman
On Mar 25, 2013, at 2:32 PM, jpbida <jpbida at ambrosevaast.com> wrote:
> What are your favorite set-ups for managing multiple developers contributing to a single perl code base? What is a good resource for doing this right? I'm really interested in projects using Dancer/Catalyst Frameworks.
> 1) Revision Systems
> 2) Code Review Tools and Release Management
> 3) Automated Testing
> Interface testing?? is there something out there that can simulate clicks?
> 4) Requirements Management
> trac, How to write a requirement?
> 5) Managing Test, UAT, & production environments
> or anything else that you would include in a good large project set-up.
> SanFrancisco-pm mailing list
> SanFrancisco-pm at pm.org
More information about the SanFrancisco-pm