[Cuis-dev] Proposal for more tests

[Hernan Wilkinson]

Hi Phil,
 I just wanted to let you know that I did not mean unit tests when I talked
about tests... They could be unit tests, integration tests, etc. In fact,
the ones I like the most are the functional tests, no matter if they are
unit tests or integration tests or component tests, etc.

 About the refactorings, I think it is the part of Cuis that has more
tests, 308 tests :-), but as we all know, tests do not assure the absence
of errors but gives you confidence when changing something and of course at
the end help reducing errors.

 So, in fact I agree with you Phil, we need more tests :-)

Cheers!
Hernan.


On Wed, Oct 21, 2020 at 1:28 AM Phil B <pbpublist at gmail.com> wrote:

> I agree with the sentiment (code quality has been slipping recently) but I
> really don't think fine-grained unit tests are going to fix it.  A lot of
> the problems I've been encountering lately have been along the lines of
> 'did anyone even try to use this?'  I do think more tests are in order but
> more along the lines of integration/system tests which we have surprisingly
> few of.
>
> For example, to exercise Morphic don't worry about testing every single
> feature of every single Morph related class, just have some unit tests that
> create and open some non-trivial Morphs (things like function graph,
> bouncing atoms and some of Ken's code would probably be good candidates for
> this like his solitaire game) and you'll likely catch a large fraction of
> issues most of us care about.  I'd also suggest better testing of
> refactoring as that has also been a non-trivial source of issues.  So
> essentially have tests that do something more substantial, and a lot of
> problems will fall out of a much smaller number of those sorts of tests.
> That's what I do and it works pretty well with minimal effort.
>
> Thanks,
> Phil
>
> On Tue, Oct 20, 2020 at 10:24 AM Hernan Wilkinson via Cuis-dev <
> cuis-dev at lists.cuis.st> wrote:
>
>> Hi all!
>>  I'd like to make a proposal.
>>  We are making lots of changes to Cuis, which is great, but at the same
>> time sometimes it generates errors and instability.
>>  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.
>>  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.
>>
>>  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.
>>
>>  What do you think? do we give it a try?
>>
>> Cheers!
>> Hernan.
>>
>> --
>>
>> *Hernán WilkinsonAgile Software Development, Teaching & Coaching*
>> *Phone: +54-011*-4893-2057
>> *Twitter: @HernanWilkinson*
>> *site: http://www.10Pines.com <http://www.10pines.com/>*
>> Address: Alem 896, Floor 6, Buenos Aires, Argentina
>> --
>> Cuis-dev mailing list
>> Cuis-dev at lists.cuis.st
>> https://lists.cuis.st/mailman/listinfo/cuis-dev
>>
>

-- 

*Hernán WilkinsonAgile Software Development, Teaching & Coaching*
*Phone: +54-011*-4893-2057
*Twitter: @HernanWilkinson*
*site: http://www.10Pines.com <http://www.10pines.com/>*
Address: Alem 896, Floor 6, Buenos Aires, Argentina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20201021/c4ecdc40/attachment-0001.htm>