On Mon, Jun 15, 2015 at 5:05 PM, Ashvin A <[email protected]> wrote: > Hi, > > We need a fast verification method for testing any changes, I agree. I > think test categories/groups is a step in the correct direction. Then as a > developer, I can quickly verify my changes at the module level. As Kirk > said, we will invest in writing new tests and also identifying and fixing > tests taking very long. > > However I think it is important to execute all tests before committing any > changes. New developers will prefer shortcuts, but it is very difficult to > weed out bugs later. I would not encourage reduced test set as a commit > criteria. I fear that tests will be ignored once a reduced set is created.
Yup. And that's exactly why the pipeline that Jun built for Amabari has *two* independent jobs running tests. One for reporting back to the JIRA (via testpatch) and the other to test the health of the branch once the commit is made. Both are important. Thanks, Roman.
