Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:37
    damodharan108 commented #3868
  • 14:37
    damodharan108 commented #3868
  • 14:37
    damodharan108 commented #3868
  • 14:33
    sebastianbergmann commented #3868
  • 14:33
    sebastianbergmann closed #3868
  • 14:33
    sebastianbergmann commented #3868
  • 14:32
    damodharan108 labeled #3868
  • 14:32
    damodharan108 opened #3868
  • 06:23

    sebastianbergmann on 3.1.1

    (compare)

  • 06:23
    sebastianbergmann closed #84
  • 06:23

    sebastianbergmann on master

    Closes #84 (compare)

  • 06:21
    sebastianbergmann edited #84
  • 06:17
    Arcesilas opened #84
  • 05:14

    sebastianbergmann on master

    Eliminate superfluous variable Remove fine-grained code covera… Fix CS/WS issues and 1 more (compare)

  • Sep 16 06:31
    heiglandreas commented #3833
  • Sep 16 06:24
    sebastianbergmann commented #3833
  • Sep 16 06:22
    localheinz commented #3833
  • Sep 16 06:22
    localheinz commented #3833
  • Sep 15 06:20
    sebastianbergmann closed #3867
  • Sep 15 06:20
    sebastianbergmann commented #3867
Ewout Pieter den Ouden
@epdenouden
--testdox might even cache all of the run results to be able to put them back in the original order
Ewout Pieter den Ouden
@epdenouden
well, just going to put this out here: sebastianbergmann/phpunit#3736
Markus Podar
@mfn

@epdenouden

A picture is worth a thousand data points.

Love that :)

Markus Podar
@mfn

good question, I don't think there is currently

I guess so too.

I wonder why not more people would have request for such a feature. Especially on large test suites which take longer, the earlier the feedback, the better.

Ewout Pieter den Ouden
@epdenouden
@mfn I want something like that myself, too, it would be very useful during development.
Is there a ticket/issue for it already?
Markus Podar
@mfn
I can create one 🤞
Ewout Pieter den Ouden
@epdenouden
please do! coming weeks I'll (hopefully) be busy building the upgraded data providers
after that I'd be happy to look at logging some more; have some small requests gathering dust
github issues never turn out like fine wine, do they :(
there's still some buffering+sequencing stuff to be looked at and your request fits right in
Markus Podar
@mfn

I mean https://github.com/ScriptFUSION/PHPUnit-Immediate-Exception-Printer really worked well for the older phpunit I tried it.

And it's not a lot code to adapt fix but the project sees dormant and I feel like a direct addition in phpunit would be interesting to a lot of people. Or so

Ewout Pieter den Ouden
@epdenouden
it would
let's have a quick look at that plugin
hmmm that screenshot looks a lot like the colorized TestDox in v8
that gives you too much output still?
Markus Podar
@mfn

I'm open to this TBH, but the current testdox/teamcity feel way to verbose.

I'm not interesting in specifics of successful tests but about failed ones needed to be fixed.

Ewout Pieter den Ouden
@epdenouden
thx :)
I relate to that a lot! I only want to see what is still borking
you know about --order-by=defects?
it sorts all previously failed tests to the front of the run as much as possible
I use that a lot when cycling [make small change -> run -> oops -> repeat]
Markus Podar
@mfn

Personally I don't have local development in mind; I use PhpStorm built in unit runner which already solves my problem.

But not all test suites are suitable to be run locally, especially with integration tests, and may take >10 minutes but the earlier I know what tests failed, the sooner I can get productive again.

Ewout Pieter den Ouden
@epdenouden
yes, test collections get ever larger and those use cases can be supported better
PhpStorm/IntelliJ indeed have this "run defects first" option built-in
really handy!
Markus Podar
@mfn
Hmm, Mr. Bergmann feels otherwise unfortunately ( in regards to sebastianbergmann/phpunit#3737 )
Ewout Pieter den Ouden
@epdenouden
welllllll yeah we've been here before
he is correct though, preferably somebody would update the printer plugin
did you have a look how much work that would be?
I mean: is it only the declared return/param types that were recently introduced? I have no idea how that printer works
I am a bit preoccupied with refactoring data providers for the next while
akshaygoyal614
@akshaygoyal614
hi , i need help
anybody is there?
I am new in php unit and i just saw some tutorials. I installed phpunit by composer require phpunit/phpunit command and created phpunit.xml file and defined bootstrap = vendor/autoload.php in xml file and created a folder tests on root but i am still getting the configuration and other things
Nicolas Hohm
@nickel715
@akshaygoyal614 sounds all good so far. can you precise your question please.
Markus Podar
@mfn

I mean: is it only the declared return/param types that were recently introduced? I have no idea how that printer works

I think something with namesspaces and change exceptions type or so. I believe the fix is rather easy but the package tries to be so compatible down to PHPUnit 5/6 that it's no fun and I'm almost tempted to just create my own version from 8 and onwards.

Ewout Pieter den Ouden
@epdenouden
@mfn yes, new work I am doing is only aimed at 8; backporting new features to 7 isn't even 'allowed'
also
hi, i need help, too
refactoring the data providers is so much fun! also, please send chocolate and drugs
Ewout Pieter den Ouden
@epdenouden
maybe we need a phpunit slack
Markus Podar
@mfn
What's so bad about gitter :)
FWIF also running slack for other stuff but couldn't care less
Ewout Pieter den Ouden
@epdenouden
ah morning :)
I'll just assume then everything works and everybody is testing all-green at 100% coverage all day every day ;-)
Markus Podar
@mfn
Ewout Pieter den Ouden
@epdenouden
as long as the data providers just crash to shell, there's no red test right ;-)
Markus Podar
@mfn
image.png
Ewout Pieter den Ouden
@epdenouden
@mfn oooo graphql that's a nice toy