Re: Writing tests about aliased functions
| From: | Raghubansh | Date: | Thu, 07 May 2009 11:03:26 +0000 |
| Subject: | Re: Writing tests about aliased functions | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-64889@lists.php.net to get a copy of this message | ||
Hi Olivier,
As per as i know, we don't write test for aliased function if test are
existing tests for original function. If there are no testcases for either
(orignal or aliased) of them then we should consider writing test cases.
I recall writing tests for is_int() and its aliases, namely is_integer() &
is_long(). While we wrote tests for is_int() we made sure that we also
called its alias in the same test. Consider looking at is_int.phpt under
ext/standard/tests/general_functions.
I am not sure how fast the gcov data is refreshed on web. Request other to
comment here. you can always do a local gcov build by extracting source from
CVS (which is latest) or downloading from snaps.php.net (which is few hour
delayed) and find out the current coverge.
Hope this helps.
with Regards,
Raghubansh
On Thu, May 7, 2009 at 3:45 PM, Olivier Doucet <webmaster@ajeux.com> wrote:
> Hello everyone,
>
> I would like to know if phptests should cover aliased PHP functions like
> get_required_files().
> I can see at
>
> http://gcov.php.net/viewer.php?version=PHP_5_3&func=tested_functions
> that
> many functions are not tested, and some of them are aliases. Is this an
> expected behaviour or not ?
>
> Also, could you tell me when is refreshed all gcov.php.net data (code
> coverage, valgrind ...) ? Latest update is 10 days ago, and I wanted to
> write some tests about not covered code (and I don't want to do work that
> has already been done - especially in this worlwide test fest period :) ).
>
> Thank you
>
> Olivier
>
--
with Regards,
Raghubansh