Jon, > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Jon A. Cruz > Sent: Tuesday, March 24, 2015 2:12 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Fwd: Re: Re: [Request for feedback] IoTivity 0.9.1 Release > Schedule & Feature > > > > On 03/24/2015 06:38 AM, Lankswert, Patrick wrote: > > June and Thiago, > > > > BTW, test engineering has been very aggressive in ramping. They have > > already started automated testing on the CA branch. Someone from test > > engineering should speak to the results to date. However, there are > > blocks of tests that work on master that do not work on the CA branch. > > The biggest set are "ACK request" (confirmable) which is still not > > supported in the CA. > > > > So, this is the order of delivery: > > > > 1) Feature complete > > > > 2) Fully reviewed > > > > 3) Unit tested (not system tests) > > > > 4) Acceptable (meaning good enough) testing engineering report > > > > 5) Ready to merge > > > > > In my experience projects complete much quicker when unit testing is done > as part of the initial coding, or at least immediately before review. System > testing can be added later, but the developer initially coding some aspect of > the feature can most quickly and effectively write tests for code when that > code is still fresh in their mind. > > if IoTivity is going to be holding to aggressive scheduling, then we should > really look at different ways to ramp up the unit testing. Then the question of > pushing for more Test Driven Development (TDD) practices might also be > examined.
Of course, you are right. I should not have said delivery. This is the order of my checklist. I look for the review first, because it may change code that can break a unit test. And, any code change as a result of failure in unit testing or validation sends you back to review. Pat -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150324/f5f86c76/attachment.p7s>
