Re: Run tests only if a module is available

2018-10-12 Thread Fernando Santagata
Thank you, it's what I needed! On Fri, Oct 12, 2018 at 1:12 AM Timo Paulssen wrote: > I'd go with run-time loading and if the module doesn't exist, just "flunk" > or "skip" or what Test.pm6 offers. > > Here's a link that explains checking if a module is installed and loading > it if it is: > >

Re: Run tests only if a module is available

2018-10-11 Thread Timo Paulssen
I'd go with run-time loading and if the module doesn't exist, just "flunk" or "skip" or what Test.pm6 offers. Here's a link that explains checking if a module is installed and loading it if it is:     https://rakudo.org/post/lexical-require-upgrade-info Hope that helps!   - Timo On 11/10/2018

Re: Run tests only if a module is available

2018-10-11 Thread Vadim Belman
Hi, So far, the only potential solution for you issue would be Test::When. But the needed functionality was declared as 'soon to be implemented' and is not there yet. Perhaps, if you convince Zoffix Znet to complete it... > 11 жовт. 2018 р. о 13:08 Fernando Santagata > написав(ла): > >

Run tests only if a module is available

2018-10-11 Thread Fernando Santagata
Hello, I wish to run some tests on one module of mine only if there's a certain third-party module available during installation. Before I concocted something horrid using try/catch in the INIT phaser, is there any gentle way to do this? Thanks! -- Fernando Santagata