Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trash trash trash #3546

Closed
solarengineering opened this issue Feb 28, 2019 · 2 comments
Closed

Trash trash trash #3546

solarengineering opened this issue Feb 28, 2019 · 2 comments

Comments

@solarengineering
Copy link

My experience:
Fresh install of phpunit 7 existing in a fresh laravel project.
I run the example feature test after renaming-

    /** @test */
    public function anyone_can_see_the_index_page()
    {
        $response = $this->get('/');
        $response->assertStatus(200);
    }

failure based on server responding with 500... WHAT?!

Certainly I have an index, I'm looking at it in the browser, but the error logging of phpunit is worth NOTHING. So where do I go from here? After a few trys I realize my database was deleted entirely. Fucking awesome phpunit.

After rebuilding my database (a few times), I try a few other things like cache:clear and $response->dump() to try to get some headway, but to no avail.

I try to update this package to 8 and get a plethora of errors basically telling me to uninstall phpunit completely before reinstalling.

Now I am at phpunit 8, and unable to get any testing accomplished based on new errors with setUp and tearDown.

Ugh, I can NOT believe this is such a popular package. It is TRASH and has literally helped me NONE.

Might as well manually input shit every time, just as efficient.

@epdenouden
Copy link
Contributor

image

@solarengineering Writing software is complex and often frustrating, I feel you. It looks like you're working on doing end-to-end testing on a whole webstack and that is not trivial at all. Hang in there.

If you want to see more error logging, have a look at running PHPUnit with the --testdox --colors=always --verbose flag. This gives you a lot more output and the v8 implementation adds a lot of new legibility features and extra details: #3439

@spriebsch
Copy link

Is the purpose of your post seeking advice or complaining about PHPUnit? If the latter, please bear in mind that actual people spend their valuable time developing and maintaining PHPUnit (and the other software you have probably used there). You are aware that those people are human, have feelings, and might feel offended by your post?

Other than that, there are thousands of developers out there using PHPUnit (and the other software you have probably used there) quite successfully. Are you sure that you did everything right?

On a personal note: it has taken me days, if not weeks in total to get into test automation. It is, as was mentioned before, a complex topic. You should not put the pressure on you to expect that everything will work right out of the box.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants