gmane.comp.php.phpunit.devel

The mailinglist will be discontinued

Sebastian Bergmann — 2012-01-14T10:37:02

 Hello!

 The mailserver that is used to serve this mailinglist will soon be
 retired by Tobias Schlitt, who graciously donated it for the last couple
 of years.

 As the traffic on the PHPUnit mailinglists is not anymore what it used
 to be, I decided to discontinue them in favour of IRC, Twitter,
 StackOverflow, etc.

 Best,
Sebastian

Re: Selenium PHP Support

Ian MacLennan — 2011-09-29T13:24:13

I'm not entirely sure I see the value of coupling PHPUnit and Selenium.
There are a number of others working on Webdriver bindings that can be used
to create tests using Selenium just like you would a normal phpunit test.

Ian

Re: Selenium PHP Support

Nicolas Terray — 2011-09-29T08:15:49

That's pretty clear :)

Do you propose an alternative ? Like a switch to Sahi ?

Thanks,
Nicolas Terray

Re: Selenium PHP Support

Martin Eisengardt — 2011-09-29T06:47:24

Hi Sebastian.


Is it possible to find another project lead who would continue selenium support? I am already working on eclipse pdt plugins for selenium and would be happy if this module won't die.



-----Ursprüngliche Nachricht-----
Von: "Sebastian Bergmann" <sebastian< at >phpunit.de>
Gesendet: 29.09.2011 08:38:44
An: dev< at >phpunit.de
Betreff: Re: [phpunit-dev] Selenium PHP Support

Am 28.09.2011 16:47, schrieb Nicolas Terray:

I do not plan to work on PHPUnit_Selenium myself anymore.

--
Sebastian Bergmann Co-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/

Re: Selenium PHP Support

Wojtek O — 2011-09-29T06:42:46

2011/9/29 Sebastian Bergmann <sebastian< at >phpunit.de>:

Nicolas,
for UI tests you can take a look at behat + mink
http://behat.org/

Re: Selenium PHP Support

Sebastian Bergmann — 2011-09-29T06:38:44

Am 28.09.2011 16:47, schrieb Nicolas Terray:

 I do not plan to work on PHPUnit_Selenium myself anymore.

Re: assertIsSubset

Wojtek O — 2011-09-29T06:30:45

2011/9/29 Ben Selby <benmatselby< at >gmail.com>:

Assert contains doesn't work for nested arrays / objects

It's for tests like
{{{
$a = array(1,2,3);
$this->assertContains($a, 1);
}}}

$haystack needs to be array or instance of Traversable.
It might be worth extending assertContains instead, but It think
that's a different assertion.


assertIsSubset takes nested arrays/objects. So you can assert
{{{
$e = array(1, 'sub' => array(3));
$a = array(1, 2, 'sub' => array(3, 4, 5));
$this->assertIsSubset($e, $a);
}}}
..and more complicated arrays/objects

Re: assertIsSubset

Ben Selby — 2011-09-29T05:55:51

Wojtek

Is that not the same as assertContains?

http://www.phpunit.de/manual/3.5/en/writing-tests-for-phpunit.html#writing-tests-for-phpunit.assertions.assertContains

Kind Regards
Ben

Sent from my iPhone

On 29 Sep 2011, at 06:26, Wojtek O <wojtek.oledzki< at >gmail.com> wrote:

assertIsSubset

Wojtek O — 2011-09-29T05:26:11

Hi chaps,
I've just forked phpunit and added new assert for checking if a
$expected value is a subset of $actual.
Works with objects and arrays.

Make sense if you want to test you code but don't want to write 10
lines of assertEquals for individual fields.

example usage
{{{
$expected = array(
 'id' => 7,
 'nodes' => array(
  array('id' => 3),
  array('id' => 12),
 )
);
$actual = $myAPI->myCall();

$this->assertIsSubset($expected, $actual);
}}}

Whole idea is that your API might change over time (new fields in
response, ...) but this particular test doesn't care about whole
response. It's just checking if $actual variable meets the minimum
requirements.

What do you think? Can you see it useful?
I would love to hear some feedback.

https://github.com/hoborglabs/phpunit

Cheers,
W
--
Wojtek Oledzki
hoborglabs.com

assertIsSubset

Wojtek Oledzki — 2011-09-28T18:16:10

Hi chaps,
I've just forked phpunit and added new assert for checking if a
$expected value is a subset of $actual.
Works with objects and arrays.

Make sense if you want to test you code but don't want to write 10
lines of assertEquals for individual fields.

example usage
{{{
$expected = array(
 'id' => 7,
 'nodes' => array(
  array('id' => 3),
  array('id' => 12),
 )
);
$actual = $myAPI->myCall();

$this->assertIsSubset($expected, $actual);
}}}

Whole idea is that your API might change over time (new fields in
response, ...) but this particular test doesn't care about whole
response. It's just checking if $actual variable meets the minimum
requirements.

What do you think? Can you see it useful?
I would love to hear some feedback.

Cheers,
W
--
Wojtek Oledzki
hoborglabs.com

Selenium PHP Support

Nicolas Terray — 2011-09-28T14:47:51

Hi there,

I've read that the support of PHP in Selenium is deprecated. I would
like to know what this means with PHPUnit SeleniumTestCase for the future.

Thanks,
Nicolas Terray

PS: Maybe this has been already addressed, where can I read the archives
of this list?

assertIsSubset

Wojtek O — 2011-09-28T08:33:51

Hi chaps,
I've just forked phpunit and added new assert for checking if a
$expected value is a subset of $actual.
Works with objects and arrays.

Make sense if you want to test you code but don't want to write 10
lines of assertEquals for individual fields.

example usage
{{{
$expected = array(
 'id' => 7,
 'nodes' => array(
   array('id' => 3),
   array('id' => 12),
 )
);
$actual = $myAPI->myCall();

$this->assertIsSubset($expected, $actual);
}}}

Whole idea is that your API might change over time (new fields in
response, ...) but this particular test doesn't care about whole
response. It's just checking if $actual variable meets the minimum
requirements.

What do you think? Can you see it useful?
I would love to hear some feedback.

Cheers,
W
--
Wojtek Oledzki
hoborglabs.com

assertIsSubset

Wojtek Oledzki — 2011-09-28T07:45:15

Hi chaps,
I've just forked phpunit and added new assert for checking if a
$expected value is a subset of $actual.
Works with objects and arrays.

Make sense if you want to test you code but don't want to write 10
lines of assertEquals for individual fields.

example usage
{{{
$expected = array(
  'id' => 7,
  'nodes' => array(
    array('id' => 3),
    array('id' => 12),
  )
);
$actual = $myAPI->myCall();

$this->assertIsSubset($expected, $actual);
}}}

Whole idea is that your API might change over time (new fields in
response, ...) but this particular test doesn't care about whole
response. It's just checking if $actual variable meets the minimum
requirements.

What do you think? Can you see it useful?
I would love to hear some feedback.

Cheers,
W

Re: PHPUnit packages and PEAR (installer) minimal version required

Remi Collet — 2011-01-03T17:40:09

Le 03/01/2011 18:30, Sebastian Bergmann a écrit :

Yes, this perfect

Great

Thanks a lot.

Remi.

Re: PHPUnit packages and PEAR (installer) minimal version required

Sebastian Bergmann — 2011-01-03T17:30:17

  Will add them for future releases. Hope that is sufficient; don't really
  want to wade through Git history and write them for older releases after
  the fact.


  sb< at >thinkpad code-coverage % git log 1.0.2.. --oneline
  c730d5e Prepare release.
  79d8ec7 Update to RGraph 2010-12-24.
  334687c Update to YUI 2.8.2r1.
  dfa0901 Fix CS.
  d184a77 Create output directory when it does not exist
  97a5734 Bump copyright year.
  d833dc1 Remove superfluous code.
  81a8db1 Use assertAttributeInstanceOf() instead of assertAttributeType().
  f2aebfb Handle files that are included but not covered.
  7430853 Simplify.
  07349b2 Close #32.
  1335a9e Eliminate superfluous trim() call.
  26619c0 Fix getNumClasses().
  c3280fa Exclude abstract methods from statistics.


  Implemented for PHPUnit, will do for the other packages before their
  next release.


  Don't want to do this, at least not now because phpunit.de for the time
  being redirects to the GitHub page (and the README.markdown file).

Re: PHPUnit packages and PEAR (installer) minimal version required

Remi Collet — 2011-01-02T18:15:31

Le 09/11/2010 17:22, Sebastian Bergmann a écrit :

Hi all and Happy new year !

< at >Sebastian, ChangeLog.markdown and README.markdown, available on Git
repository, are really usefull files, which I'm used to provides in the
packages.

Could it be possible (order by importance) :

1/ to have a Changelog file for other packages.

For example, I don't find any information about Changes in new
PHP_CodeCoverage version 1.0.3, which is quite annoying to publish this
update without any information for users. (A simple "New upstream
version" is really discouraged by Fedora Guidelines)

Workaround : another source for this ?

2/ to provide Readme and Changelog files in your package (of course,
tagged with role="doc")

This files are really small, and shouldn't be a big "space" problem

Workaround : I can continue to add it manually, from git, as for now

3/ to add a LICENCE File

Yes, I know... but some distro, (and RH legal) like to have a really
explicit Licence file for each package.

Workaround : no Licence in package stay acceptable.

4/ to split README into INSTALL (no interest for RPM users, so removed
from RPM) + README

In fact, no need to "install" the INSTALL file... of course (chicken/egg).

Workaround : I can remove the "Install" part from the readme file... or
not...


Best regards
Remi.

P.S yes, this seems like a list to Santa Claus, I should have send it a
few weeks ago ;)

one question about phpunit

2010-11-18T01:44:25

Hi phpunit specialists,


When I designed tests through phpunit, One failure occurred. 
test file: testFile.php
one test function, for example testFunction1()
run: phpunit testFile.php

The line 49, 50, there are 2 assertion, they should be failed all, but the report only tell one, ignor the other.

also I see one option for phpunit --stop-on-failure, seems it does not work,
 though I assigned FALSE to stop-on-failure, (/usr/share/php/PHPUnit/TextUI/Command.php)

Are there any guys can help me? thank you very much.

Thanks,

Best Regards,
-----------------------------------------------------------------
Larry Shi(Shi Yao-Bin)
Open Source Program Office (EB-BAS-BECOM-BJ)
China Hewlett-Packard
yao-bin.shi< at >hp.com
------------------------------------------------------------------

Re: Pull requests

David Harkness — 2010-11-09T17:14:28



I do understand being busy. I am as well or I would have stopped in to say
"hi" when you were out here in California last week giving talks at the Zend
conference. I know integrating other people's code can take much more time
than writing it yourself. I've been there. :)

My question is more "Is there anything I can do to make it easier?" than
"Why haven't you taken my patches?" With other patches being integrated but
no word on mine, I feared they might be unacceptable. And it turns out they
broke tests which to me *is* unacceptable. Anyway, I believe they are in
good states now.

Thanks for the heads up.

Sincerely,
David

Re: Pull requests

Sebastian Bergmann — 2010-11-09T16:26:44

Am 05.11.2010 23:45, schrieb David Harkness:

 Hello David,

 I can understand that you are frustrated that accepting/reviewing your
 patches is taking so long. For that, please accept my apologies. I am
 too busy at the moment to spend too much time on PHPUnit. I hope this
 will change in a couple of weeks.

 Best,
Sebastian

Re: Introduce myself and first question related to packaging

Sebastian Bergmann — 2010-11-09T16:25:25

Am 26.09.2010 11:11, schrieb Remi Collet:

 It is because of this circular dependency that DbUnit, for instance,
 does not depend on PHPUnit.


 I do not see how this would make things simpler.

Re: PHPUnit packages and PEAR (installer) minimal version required

Sebastian Bergmann — 2010-11-09T16:22:28

Am 07.11.2010 08:43, schrieb Remi Collet:

 The PEAR package itself also provides the functionality used by
 PHPUnit to run PHPT tests. http://pear.php.net/bugs/bug.php?id=17292
 is the reason why PEAR 1.9.1 is required.


 That was my opinion as well back when I maintained PHP and PEAR
 packages for Gentoo Linux. Now, however, I think that the PEAR
 Installer should be used instead of the Linux distribution's native
 package management system as only this guarantees timely updates for
 PEAR-packaged software.


 I do, but due to the bug in PEAR 1.9.0 that I quoted above I have to
 require PEAR 1.9.1, I'm afraid. Thank you for you efforts, Remi, and do
 not hesitate to contact me if there anything I can do to make your work
 easier,
Sebastian