<div dir="ltr">Hi Everyone!<div><br></div><div>+1<br></div><div>IMHO, I think Hernan's proposal is spot on.</div><div><br></div><div>At least from my experience understanding, using, and modifying Cuis in the past two years I found the lack of tests to get in the way of what I was trying to do.</div><div>I feel it requires a lot more from me (both in terms of time and cognitive load, so to speak) to get things done.</div><div><br></div><div>I also found the lack of tests to be a stopper whenever I tried to improve existing code, too.</div><div>That required me to put a lot of time & effort in writing the missing ones before I was able to contribute, and make sure I didn't break anything in the process :P</div><div><br></div><div>Of course, as Hernan said, this is not something that can be done immediately and/or might not apply to, say, experiments that are not part of the core.</div><div><br></div><div>I believe having a clear direction on this topic will make things better for all of us in the future.</div><div>Would love to hear your thoughts about this.</div><div><br></div><div>Cheers,</div><div>Nico PM </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 20, 2020 at 11:24 AM Hernan Wilkinson via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all!<div> I'd like to make a proposal.</div><div> We are making lots of changes to Cuis, which is great, but at the same time sometimes it generates errors and instability. </div><div> My proposal has to do with keeping the quality and stability that Cuis has and it is that everytime we make a change or improvement to Cuis, to attach tests that prove the change is correct. </div><div> Having tests is not only for today but for the future of Cuis. It is the only way we have to keep its good quality and stability.</div><div> </div><div> We all know that it is not possible to test everything, for example the changes that Juan just did to Morph are very difficult and time consuming to test with automatic tests, but there are other changes, mainly to core classes or tools, that are possible to test and I think we should try our best to do it.</div><div><br></div><div> What do you think? do we give it a try?</div><div><br></div><div>Cheers!</div><div>Hernan.</div><div><br></div><div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-family:tahoma,sans-serif;font-size:xx-small;border-collapse:collapse"><strong><span style="font-size:8pt"><span><span style="font-size:small"><font size="2"><span style="font-weight:normal"><span style="font-weight:bold">Hernán Wilkinson</span><br>Agile Software Development, Teaching & Coaching</span></font></span></span></span></strong></span></div><div><span style="font-family:tahoma,sans-serif;font-size:xx-small;border-collapse:collapse"><strong><span style="font-size:8pt"><span><span style="font-size:small"><font size="2"><span style="font-weight:normal">Phone: +54-011</span></font></span></span></span></strong></span><font face="tahoma, sans-serif" size="2">-4893-2057</font></div><div><strong style="font-family:tahoma,sans-serif;font-size:xx-small"><span style="font-size:8pt"><span style="font-size:small"><font size="2"><span style="font-weight:normal">Twitter: @HernanWilkinson</span></font></span></span></strong></div><div><span style="font-family:tahoma,sans-serif;font-size:xx-small;border-collapse:collapse"><strong><span style="font-size:8pt"><span><span style="font-size:small"><font size="2"><span style="font-weight:normal">site: <a href="http://www.10pines.com/" style="color:rgb(17,65,112)" target="_blank">http://www.10Pines.com</a></span></font></span></span></span></strong></span></div><div><font face="tahoma, sans-serif"><span style="border-collapse:collapse">Address: Alem 896</span></font>, Floor 6, Buenos Aires, Argentina</div></div></div></div></div></div></div></div></div></div></div></div></div></div>
-- <br>
Cuis-dev mailing list<br>
<a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br>
<a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><br>Nicolás Papagna</div>