Re:Ask HN: Broken tests, huge (250 commit) pull requests, gr...
by plet on Friday November 13, 2015 @01:40PM
(#10561526)
A : "we're delivering features"
B : Would you rather deliver features or make sure the platform that you're working on stays running ?
For the product/project itself, setup a continuous delivery pipeline. Allow (if possible) one pull request at a time. Let integration/load/benchmark tests prove that its not breaking anything. If the tests are broken, whoever breaks them gets to fix them. They're not in the team anymore? no problem. Whoever needs to push a change, need to make sure the pipeline is working.
Growing team needs direction. Set up tenants / guidelines / vision. Assign product owners that are responsible to customers/stakeholders.
Also, figure out why nobody cares. Is it lack of knowledge / best practices? Is it lack of interest? Is it not-my-job phenomenon ?
B : Would you rather deliver features or make sure the platform that you're working on stays running ?
For the product/project itself, setup a continuous delivery pipeline. Allow (if possible) one pull request at a time. Let integration/load/benchmark tests prove that its not breaking anything. If the tests are broken, whoever breaks them gets to fix them. They're not in the team anymore? no problem. Whoever needs to push a change, need to make sure the pipeline is working.
Growing team needs direction. Set up tenants / guidelines / vision. Assign product owners that are responsible to customers/stakeholders.
Also, figure out why nobody cares. Is it lack of knowledge / best practices? Is it lack of interest? Is it not-my-job phenomenon ?