Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > it.comp.www.php > #21275

Re: code coverage

From alex <1j9448a02@lnx159sneakemail.com.invalid>
Newsgroups it.comp.www.php
Subject Re: code coverage
Date 2016-11-18 09:21 +0100
Organization Aioe.org NNTP Server
Message-ID <o0mdmb$1e7m$1@gioia.aioe.org> (permalink)
References (4 earlier) <o0kd6h$m0i$1@gioia.aioe.org> <o0kekh$ofr$1@gioia.aioe.org> <40qr2c9gsnqomveu8v411memphi850egsf@L.Serni> <o0kvv4$1mva$1@gioia.aioe.org> <6e428265-0a3b-4ffa-9b53-6f3368daad99@googlegroups.com>

Show all headers | View raw

Il 17/11/2016 20:39, fmassei@gmail.com ha scritto:
> On Thursday, November 17, 2016 at 2:21:12 PM UTC-5, alex wrote:
>> Il 17/11/2016 18:25, Leonardo Serni ha scritto:
>>> Sostanzialmente, sì.
>>>
>>> Poi è lavoro che ti ritrovi, credimi :-)
>>>
>>> Consideralo un investimento.
>>
>> anche se è probabile che in futuro queste funzionalità saranno già
>> integrate in php, senza installare pacchi extra :)
>>
>
> Non credo: la scelta dei meccanismi di testing dipendono dal processo di
> sviluppo, che è diverso da azienda a azienda. :)
>
> Ciao!
>

inserire qualche funzione ad uso immediato tipo covered_lines() non 
sarebbe cmq male, a prescindere...

Back to it.comp.www.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-17 10:12 +0100
  Re: code coverage Alessandro Pellizzari <shuriken@amiran.it> - 2016-11-17 10:25 +0000
    Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-17 12:42 +0100
      Re: code coverage fmassei@gmail.com - 2016-11-17 03:51 -0800
        Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-17 15:01 +0100
          Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-17 15:25 +0100
            Re: code coverage Leonardo Serni <lserni@gmail.com> - 2016-11-17 18:25 +0100
              Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-17 20:21 +0100
                Re: code coverage fmassei@gmail.com - 2016-11-17 11:39 -0800
                Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-18 09:21 +0100
            Re: code coverage Alessandro Pellizzari <shuriken@amiran.it> - 2016-11-18 08:13 +0000
              Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-18 17:54 +0100
                Re: code coverage fmassei@gmail.com - 2016-11-18 09:04 -0800
                Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-18 21:05 +0100
                Re: code coverage fmassei@gmail.com - 2016-11-18 12:53 -0800
                Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-19 11:17 +0100
                Re: code coverage fmassei@gmail.com - 2016-11-19 11:11 -0800
                Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-19 21:45 +0100
                Re: code coverage fmassei@gmail.com - 2016-11-21 18:20 -0800
                Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-23 14:58 +0100
      Re: code coverage "ciccio" <21669invalid@mynewsgate.net> - 2016-11-17 16:54 +0000
        Re: code coverage alex <1j9448a02@lnx159sneakemail.com.invalid> - 2016-11-17 20:24 +0100

csiph-web