Hi,

can you please include in the README at the very least how it should be
launched? Looking through the code I eventually found that there's a world
menu entry... but that's not exactly the best way to discovery.

I've ran it on couple of projects, but it didn't show anything apart from
self skip, but if you find something else, I'd be interested to see what it
can detect.

https://github.com/peteruhnak?utf8=%E2%9C%93&tab=repositories&q=&type=source&language=smalltalk


Also when I filter packages and select one, the test cases list contains
some random unrelated tests. When the filtering is not on, the test cases
are correct.




Cheers,
Peter

On Thu, Jul 5, 2018 at 7:16 PM, Max Leske <[email protected]> wrote:

> Fuel: https://github.com/theseion/Fuel
> Seaside: https://github.com/SeasideSt/Seaside
>
> On 5 Jul 2018, at 16:31, Serge Stinckwich wrote:
>
>
>
> On Thu, Jul 5, 2018 at 3:24 PM Julien <[email protected]> wrote:
>
>> Hello Pharo community,
>>
>> I am currently working on detecting rotten tests in Pharo projects.
>>
>> Rotten tests are defined as test methods containing one or many
>> assertions in their source code but one or many of these assertions are not
>> executed when the test is run.
>> To have more details on the subject, you can check the research report
>> related to our first definition of these tests freely available on HAL [1].
>>
>> In this context, we built a test analyser which, given a Pharo package
>> containing tests, finds rotten tests [2]. This analyser is still under
>> development.
>>
>> We would like to extend the experiment of our research report [1] and to
>> analyse more projects in order to get a better understanding of rotten
>> tests.
>>
>> To do that, we need your help. You can help us in two ways:
>> 1. Answer this email with links to one or many open-source Pharo projects
>> containing tests.
>>
>
> ​We have 774 tests in PolyMath:
> https://github.com/PolyMathOrg/PolyMath
>
> --
> Serge Stinckwich
> UMI UMMISCO 209 (SU/IRD/UY1)
> "Programs must be written for people to read, and only incidentally for
> machines to execute."http://www.doesnotunderstand.org/
>
>

Reply via email to