Stef, I know it's easy to speak with Monday's newspaper, but I wouldn't accept projects for Pharo that do not have tests. I do not pretend X number of percentage, but at least some tests. Otherwise, YOU will have to pay the costs.��
Max: we already have a test coverage tool already in the image since years. Open Test Runner -> Run Coverage.��
Cheers,��
On Sun, Feb 14, 2016 at 9:14 AM, stepharo <stepharo@free.fr> wrote:
Thanks
I do not have the cycle for that but I would love to get some feedback on if this is possible to run
and for which packages.
Stef
Le 14/2/16 04:09, Alejandro Infante a ��crit :
If you plan to add it to an automatic CI Job with Hapao, I would recommend to load the following group of Spy2:
���������������
(ConfigurationOfSpy2 project version: #stable) load: #HapaoCore
���������������
This is going to load just the core of Spy and Hapao and will not load Roassal, GT-Inspector and GT-Debugger extensions.
Cheers,
Alejandro
On Feb 13, 2016, at 6:39 PM, stepharo <stepharo@free.fr> wrote:
Yes I would even buy 20% coverage right now.
Stef
Le 13/2/16 20:22, Max Leske a ��crit :
How about enforcing coverage? I know that coverage tests don���t say anything about the quality of the test cases but it���s (almost) always better to have some tests than none. I wouldn���t set the bar too high either for coverage, maybe 60 or 70%. 100% is unrealistic, but 60 to 70 should be achievable with a couple of well written tests.
Of course we would need a way to run coverage tests on the test suite. Do we have a tool for coverage tests?
On 13 Feb 2016, at 19:35, stepharo <stepharo@free.fr> wrote:
Hi guys
with damien cassou we had an interesting discussion. Basically we are teaching tests and we see that many Pharo subsystems are not really well tested. I wonder how we can change this. For example, we will have a new graphical core without any tests
and this is sad because tests could be really good to make sure that we will be able to move forward in the future.
I would like to get tests for Ring.
Stef
--