More tests for new frameworks
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
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
On Sat, Feb 13, 2016 at 8:22 PM, Max Leske <maxleske@gmail.com> wrote:
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?
Yes, there's Hapao http://objectprofile.com/Hapao.html you can install it from Catalog Browser under the name "Spy2". (There's more to Spy2, but Hapao is included.) So maybe CI could run the coverage and issue a warning if it is under a certain threshold, however the doesn't really cover adding new features (e.g. project has 80% coverage⦠new untested features are added, coverage drops to 75% and nobody notices). Peter
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
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
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
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
-- Mariano http://marianopeck.wordpress.com
I agree. Now what I would like is the community to push and shout for tests. The question that we can ask ourselves is how can we push more tests. Stef Le 15/2/16 14:15, Mariano Martinez Peck a écrit :
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 <mailto: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 <mailto: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 <mailto: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
-- Mariano http://marianopeck.wordpress.com
participants (5)
-
Alejandro Infante -
Mariano Martinez Peck -
Max Leske -
Peter Uhnák -
stepharo