[p2pu-dev] Suggestion for developemnt process

Nadeem Shabir ns at talis.com
Wed May 11 11:06:52 UTC 2011

Zuzel what level of automated testing do we have at the moment?
I'm a little out of sync with our current development process ... but ...

Should the development process not be tied into / supported by a continuous
integration process? I.e. every check in into trunk is checked out by a CI
server that builds, deploys, and runs any automated tests.  Should we be
aiming to have a suite of unit tests, and a suite of acceptance or more
functional tests written in something like Selenium that verifies that the
application is working consistently across different browsers.  I've been
using tools like SauceLabs to run a Selenium based test suite against
multiple browser and os versions - and the net result is all developer
checkins are tested automatically by the build server, which obviously means
releases can then be deployed to live with confidence.

On 11 May 2011 10:15, Philipp Schmidt <phi.schmidt at gmail.com> wrote:

> On 11 May 2011 03:49, John Britton <public at johndbritton.com> wrote:
> > This is part of the argument against moving to the new site earlier. I'm
> not
> > opposed, but because we're going to have more and more real users on the
> new
> > site we'll have to spend a fair amount of time making sure things work
> > before we push them. The alternative is to be ready to fix things if they
> > are broken after we push them (I tend to prefer this approach).
> I suspect the right solution is somewhere in the middle. The old site
> is really starting to hurt us, and it would be great if we could move
> sooner rather than later. But I agree with John that we don't want to
> slow down development too much, and we also don't want real users to
> get frustrated by serious bugs. Could we keep pushing (push-then-fix)
> for now, and start increasing the testing / staging phase by a day at
> a time as we take on more users?
> It might also be useful to have an alpha.p2pu.org where those with
> interest and time, could always access the latest snapshot of
> development progress, and help test.
> P
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20110511/a6d212a1/attachment.html>

More information about the p2pu-dev mailing list