Individual comment from a non-dev who has just observed devs: it would seem we have no formal testing policy but that we gravely need one. Code is developed and requested to be merged by dev A, then dev B looks the code itself over. Hopefully at this point dev B would then build it and test the crap out of it to make sure everything still works perfectly, but I feel that doesn't get done thoroughly as often as it should and consequently regressions slip through.
Automated and standardized testing would be boss. Regards, Cassidy James On Apr 4, 2013 7:52 AM, "Craig" <webe...@gmail.com> wrote: > Hello everyone, > > I'm curious what you devs do for testing? I'm not particularly familiar > with Vala, but I'm learning a lot about testing at work and I'm trying to > develop myself to that end in my free time. I'm sending this email because > I'd like to get a pulse on what you Elementary devs think about testing and > what you actually do to test your code. Also, please feel encouraged to > talk about what you've done in the past, what has/hasn't worked for you, > and generally what your philosophy is about testing (or whether you have no > philosophy). Individual comments and comments on behalf of elementary as a > whole are both welcome. > > Sound off! > > Thanks, > Craig > > -- > Mailing list: https://launchpad.net/~elementary-dev-community > Post to : elementary-dev-community@lists.launchpad.net > Unsubscribe : https://launchpad.net/~elementary-dev-community > More help : https://help.launchpad.net/ListHelp > >
-- Mailing list: https://launchpad.net/~elementary-dev-community Post to : elementary-dev-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~elementary-dev-community More help : https://help.launchpad.net/ListHelp
