An interesting thought I have regarding the mistake that was made a few times with a leading zero on time: I feel that if this was a real project, and there was no specific requirements stating how it should be formatted for a particular reason, I'd argue that if you're getting confused over the time, the time you keep thinking it was honestly just should be the way the time gets formatted. Obviously this was just for demo purposes, but I feel that if something is confusing in how software behaves, it's a bug.
I personally write a very high level test to ensure the feature is working as expected generally. For edge cases I'll write a unit test when needed. I only see value in tests to allow for future refactoring jobs to go smoothly. The reality in 90% of the time tests dont bring much value to the company in comparison to spending time writing new features. I would suggest looking up theprimeagen/theo unit test on youtube for a good discussion.
Hey povillas, just wanna thank you for your explanation about the difference between feature and unit test. Anyway, can you give us video about testing simple crud? I'm still confused with how to use test
Unit tests don't have access to facades by default so you would have to change the "extends TestCase", in the end you would have a Feature Test, if you make very complex.
I have a gaming project in which one of the apis is to serve 2 functionalities: - assigning mission to user (mission is some sort of quest that once getting complete, user'd get rewards). - fetching a list of missions currently assigned to user. Each functionality has very complex logic inside and each requires seeding to make the test running. So if I want to test if these 2 functionalities, should it be called unit test or feature test? If its called unit test, meaning it would not require any seeding or DB call but there must be DB call in both cases. But how could it be called feature test when they are not the whole api end point? Any insight would be much appreciated.
my soft and no content plays, I would really appreciate so guidance on how to fix tNice tutorials problem so I can actually move pass tNice tutorials, thank
Since I started to work with nodeJS many things have changed, testing with nodeJS (jest) it makes more sense and it's easier to write unit tests but for laravel projects it's so much easier to write feature tests, I'd say "it depends"
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
Perfect video format. Watching your channel on daily basis while having breakfast. Please keep going with such short videos.
This video gave me clear understanding about the concept of tests. Thank you!
Thanks so much for your thoughtful and detailed videos! On to the soft!
Glad Everyone found this useful
thanks for this video, now I understand how laravel test works
I also heard that unit test usually runs faster because they don't interact with IO, and that's very important in CI/CD setup.
Thanks for sharing such a valuable information with us 😊
I was just waiting for this
An interesting thought I have regarding the mistake that was made a few times with a leading zero on time:
I feel that if this was a real project, and there was no specific requirements stating how it should be formatted for a particular reason, I'd argue that if you're getting confused over the time, the time you keep thinking it was honestly just should be the way the time gets formatted.
Obviously this was just for demo purposes, but I feel that if something is confusing in how software behaves, it's a bug.
I personally write a very high level test to ensure the feature is working as expected generally. For edge cases I'll write a unit test when needed. I only see value in tests to allow for future refactoring jobs to go smoothly. The reality in 90% of the time tests dont bring much value to the company in comparison to spending time writing new features. I would suggest looking up theprimeagen/theo unit test on youtube for a good discussion.
Hey povillas, just wanna thank you for your explanation about the difference between feature and unit test. Anyway, can you give us video about testing simple crud? I'm still confused with how to use test
I've created a course about it: laraveldaily.teachable.com/p/laravel-testing-for-beginners-phpunit-and-pest
really useful one thanks man ❤️
Unit tests don't have access to facades by default so you would have to change the "extends TestCase", in the end you would have a Feature Test, if you make very complex.
Titanic reference is legit.
I have a gaming project in which one of the apis is to serve 2 functionalities:
- assigning mission to user (mission is some sort of quest that once getting complete, user'd get rewards).
- fetching a list of missions currently assigned to user.
Each functionality has very complex logic inside and each requires seeding to make the test running.
So if I want to test if these 2 functionalities, should it be called unit test or feature test?
If its called unit test, meaning it would not require any seeding or DB call but there must be DB call in both cases.
But how could it be called feature test when they are not the whole api end point?
Any insight would be much appreciated.
I guess I would call "feature test" any test that touches a DB.
Thank you very much
you are the best!
Are api requests tests feature or unit tests ?
Feature
my soft and no content plays, I would really appreciate so guidance on how to fix tNice tutorials problem so I can actually move pass tNice tutorials, thank
I did not know about it
cool
wondering if u would be willing to collab to make a . TNice tutorials would be my first and I would understand and apprehensions you may
I always skip testing 🦋
most of your test should be feature test
lol what?)) how about test pyramid?
Since I started to work with nodeJS many things have changed, testing with nodeJS (jest) it makes more sense and it's easier to write unit tests but for laravel projects it's so much easier to write feature tests, I'd say "it depends"