On 10 nov. 08, at 19:51, Alexandre Bergel wrote:
Yes, this is the case. When you run the test, the result are stored
into the class that has been run.
Maybe we could store them in a location outside the package. But
test results will not be persistent.
Yes and no. The package becomes dirty only if the test results change
- ie if a test goes from failure to pass for example.
Alexandre
On 10 Nov 2008, at 14:40, Stéphane Ducasse wrote:
what would be nice if that the packages do not get dirty because
the tests run.
I do not know if this is the case but this is important.
On Nov 10, 2008, at 4:58 PM, Alexandre Bergel wrote:
I have seen this. We should continue this discussion offline, then
propose a robust and stable version to the pharo community.
Cheers,
Alexandre
On 10 Nov 2008, at 12:53, Simon Denier wrote:
On 10 nov. 08, at 11:07, David Röthlisberger wrote:
So let me know when I can load again and integrate your
extension.
Could you please check with SUnit-DavidRoethlisberger.42 in http://www.squeaksource.com/Pharo
and execute ScriptLoader class >> loadOB?
It is not enough
Starting from a fresh 10144 image, loading OB with scriptloader,
then your latest commit for sunit, I do get the icons in the
browser, but cant update their state: not lastRun method is
generated and it fails when I try to save the results in the
TestRunner. Best guess: the code generating lastRun on the class
side is lost.
Then after it would be great to have a button to run the tests
and
yes, we should have something like that in the browser.
David
Hi Stef,
as you as the SUnit extensions are integrated, you just need
to load OB. Any OB load method in ScriptLoader can be used for
this as this extension is also in the stable OB version now.
David
can you tell me what I should do to get the icons showing the
status of tests in your browser?
I should harvest the Sunit extensions and then?
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-
project
--
Simon
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
Simon
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
