[Pharo-dev] Calypso idea - inherited tests

ducasse stepharo at netcourrier.com
Thu May 30 08:59:07 EDT 2019


I will try to save them when I get them.


> On 30 May 2019, at 08:09, Denis Kudriashov <dionisiydk at gmail.com> wrote:
> 
> Hi guys.
> 
> Would be nice to see the error stack. 
> Which variable is nil in that case?
> 
> I really do not see such errors. Is it pharo 7 or 8?
> 
> 
> чт, 30 мая 2019 г., 11:17 ducasse <stepharo at netcourrier.com <mailto:stepharo at netcourrier.com>>:
> 
> 
>> On 29 May 2019, at 23:58, Ben Coman <btc at openinworld.com <mailto:btc at openinworld.com>> wrote:
>> 
>> 
>> 
>> On Thu, 30 May 2019 at 06:26, Denis Kudriashov <dionisiydk at gmail.com <mailto:dionisiydk at gmail.com>> wrote:
>> Hi Ben.
>> 
>> There are already two features that support inherited tests:
>> - run all tests using class icon: there will be extra red method group "broken tests" which will show failed inherited tests.
>> - toggle inheritance visibility with checkbox in third panel: you will see inherited tests and standard method icon will run them.
>> 
>> Ahh, excellent... the second is exactly what I wanted.
>> 
>> Although using TestDelaySemaphoreSchedulerMicrosecondTicker as an example,
>> clicking on a test gives me an error "#selected was sent to nil" in "ClyBrowserToolMorph>>isTabSelected"
>> Do you get the same?
> 
> Yes this happens to me often. 
> I think that calypso forks too many processes. 
>> 
>> cheers -ben
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20190530/c9b50153/attachment.html>


More information about the Pharo-dev mailing list