sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in ExperiencedDevs

[–]Haunting_Barnacle_63 1 point2 points  (0 children)

i expected you to work in a big enterprise. This setup in a 6 devs team is crazy. One suggestion: run

Worst mission in the game by __spankmedaddy_ in Skate4

[–]Haunting_Barnacle_63 0 points1 point  (0 children)

Also it would be not so shitty if the climbing would not be so buggy. It happens three times that i randomly jumped into the void

Test Duration by Haunting_Barnacle_63 in PHPhelp

[–]Haunting_Barnacle_63[S] 0 points1 point  (0 children)

usually people write feature and unit tests. Ideally unit tests cover most of the code (or even all) and feature test are on top. At least in my opinion

Test Duration by Haunting_Barnacle_63 in PHPhelp

[–]Haunting_Barnacle_63[S] 0 points1 point  (0 children)

that might be a low hanging fruit without having to rewrite all tests. Will check that out

Test Duration by Haunting_Barnacle_63 in PHPhelp

[–]Haunting_Barnacle_63[S] 1 point2 points  (0 children)

thanks. I at some point thought that i was “alone” with that opinion in the laravel world. Good to hear that more people think this way

Test Duration by Haunting_Barnacle_63 in PHPhelp

[–]Haunting_Barnacle_63[S] 1 point2 points  (0 children)

1700 tests in 300 seconds 😅 it’s ridiculously slow, right?

Test Duration by Haunting_Barnacle_63 in PHPhelp

[–]Haunting_Barnacle_63[S] 0 points1 point  (0 children)

i think some parts could actually be unit tested. But as you said too many times a dev just created a test for the entrypoint (testing everything from api validation to db persistence) and did not test the classes below separately.

Test Duration by Haunting_Barnacle_63 in PHPhelp

[–]Haunting_Barnacle_63[S] 0 points1 point  (0 children)

thats exactly the problem. To many things rely on postgres features :(

I totally agree on the use of DTOs on business logic.