[Ux] CLOUD4ALL: PMT unit tests
colinbdclark at gmail.com
Thu Dec 4 11:49:12 EST 2014
From my perspective, unit tests are not optional in our system. They are a standard practice for any developer today, regardless of whether they work in industry or research. The requirement to write unit tests for all functionality shouldn't be unusual or difficult for most developers.
The reason is that if you don't write unit tests, we will have no way to verify that the PMT is actually functioning as expected and that it continues to work when things change as we prepare of the review and beyond. A practical example of this is the recent breakage of the PMT with the "fireball branch." Had there been an automated suite of unit tests, we would have caught this regression weeks ago.
Equally, if there are cases where you are expecting Flow Manager-side support for the PMT, we need unit tests to ensure that anything we implement is correctly meeting the contract that you expect. We can't be responsible for a working integration in the absence of unit tests.
When it comes to the pressure of deadlines related to the review (which I totally empathize with) and your desire to reduce scope by not writing unit tests, I will need to defer to Manuel and Gregg. My advice is that not writing unit tests is a technical risk, and you will likely need to be responsible for a more rigorous manual testing procedure (i.e. testing by hand daily against the latest maser branch of the whole system) in order to ensure that everything continues to work.
> On Dec 4, 2014, at 9:54 AM, Kostas Kalogirou <kalogir at certh.gr> wrote:
> Dear UXers and architecturers,
> I would like to ask you whether it is possible to not include unit tests for signup(http://issues.gpii.net/browse/GPII-947 <http://issues.gpii.net/browse/GPII-947>) , auto-adjust adjuster(http://issues.gpii.net/browse/GPII-1023 <http://issues.gpii.net/browse/GPII-1023> ), mobile adjusters(http://issues.gpii.net/browse/GPII-803 <http://issues.gpii.net/browse/GPII-803>)
> and context wireframes(http://issues.gpii.net/browse/GPII-1018 <http://issues.gpii.net/browse/GPII-1018>, GPII-1019, GPII-1020) for PMT development.
> It seems that we are running out of time and we have to finish the development of all of the above JIRAs, including the http://issues.gpii.net/browse/GPII-1029 <http://issues.gpii.net/browse/GPII-1029> (the new API provided by GPII server) and get ready for the E.C. review.
> Besides, I think that no one from the reviewers will examine the code to see whether we have included unit tests.
> Konstantinos Kalogirou
> Software Engineering/MSc at Digital Signal Processing
> Centre for Research & Technology Hellas(CE.R.T.H.)/
> Hellenic Institute of Transport (H.I.T.)
> 6th km Harilaou-Thermi Road,
> P.O. Box 60361, 57001 Thermi, Macedonia,
> Tel: +30 2310 498461
> Fax:+30 2310 498269
> www.imet.gr <http://www.certh.gr/>
> www.certh.gr <http://www.certh.gr/>
> Ux mailing list
> Ux at lists.gpii.net <mailto:Ux at lists.gpii.net>
> http://lists.gpii.net/cgi-bin/mailman/listinfo/ux <http://lists.gpii.net/cgi-bin/mailman/listinfo/ux>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ux