Should You Test As A Web Developer?
HTML-код
- Опубликовано: 25 июн 2024
- A chat about writing tests as a web developer. I talk about what testing is, the benefits, types of testing, and when and if you should write tests for your projects.
Check out my premium courses:
traversymedia.com
Jest Crash Course:
• Jest Crash Course - Un...
React Testing Course:
• Jest Crash Course - Un...
TDD Course:
• Intro To JavaScript Un...
Timestamps:
0:00 - Intro
0:54 - What Is Testing?
1:56 - TDD (Test Driven Development)
3:19 - Types Of Testing
5:28 - When Should You Write Tests?
Social Media:
Github - github.com/bradtraversy
Twitter - / traversymedia
Instagram - / traversymedia
Facebook - / traversymedia
Linkedin - / bradtraversy Наука
I know the text description is wrong for unit testing. I didn't realize until after upload. Sorry about that.
What is your opinion on testing? What do you agree/disagree with?
One request, A Custom Framework with API Development and testing API using PHP would be helpful.
I agreed with testing and I'm interested to learn testing in js.
hi sir i want please to ask you about something i have 33years old i lost my job in 2020 from this years and now we are in 2023 i didnt find job so i thinking to change my career and my life and i love programming and they say to me age is problem to be frontend developer in this age and to find job like freelance or in another country is not easy is this true please say to me the true
@@soumiarouba2729 It's not complex thing, you can still learn and get a job, so, don't be sad about it. you can start HTML and CSS from this channel's. playlist too 'HTML and CSS', where you can start watching from first video, learn 10-15 minutes of content of video, and practice it until you get comfortable with concepts taught in the video, then in the next day, revise what you've learned previous day and move. ahead with next 10-15 minutes of content.
testing is also a type of documentation ;) but the problem is if the project you are working on is already a monster with tight deadlines, so testing becomes really not worth it because you know this thing is not well designed but just mantained and basically needs to be redone
all those developer he taught for free over these years on RUclips , they(me included) are now old enough to realise that testing was the most important part of development. People now prioritise mental peace after production deployment than learning new tech stacks. Thanks.... I developed my first server application at my work by watching your tutorials.
Great video Brad. And thanks for doing the annual guide. I fully heared the 2023 annual guide 20+ times while driving and its sooooooo good. Great Job, Please keep it up.
One of the best instructor on RUclips ❤️💙
I am Laravel developer and use Cypress for frontend and Pest test for backend. I must say, you will find it difficult initially but it is lot better practice in longer term
I've tested a ton in my career, for most of my side projects, I don't do any testing at all except spot testing e2e stuff. Testing is the most tedious, boring part of our career. It's never straight forward, but it's hugely important for real money making operations.
@realchrishawkes I am intrested in getting few helpful details about testing from your earn, Thanks in advance.
@TraversyMedia Keep up the good work bro. Your courses and the way you teach things has given me alot of inspiration to keep moving forward with a career in web development.
I've always love Brad honesty
Thanks a lot for this video sir. Recently I've been reading more on Jest for testing my web applications. I really appreciate the insights put into this video.
By the way, I've learnt a lot from your channel. Thanks sir
Good to see you man
Your great fan and student here from Ethiopia 🇪🇹. God bless you ❤
great topic sir, thanks for all of your amazing content. Also looks like you have been working out, grats on that too! :)
Brad, can't wait for your Laravel course!
Have you ever thought about hosting a meetup? I feel like whoever would go to that would be the exact devs I'd like to meet
Thanks Brad
Playwright with a BDD style approach to developing user stories has been a phenomenal experience for me, but I'm an SDET by trade so this comes naturally to me.
Thanks for this video, yesterday we had a conversation with my friend about testing but one of the things he advised me is that know how to code first then dive into test.
Testing is important when you are collaborating and you want to push your product (code).
You are an awesome person!
just the video i needed
Hey Brad! I love your courses man! I know this might be very newbie stuff, but have you ever considered doing a crash course on programming logic or even further the topic with computational thinking? I'm coursing your HTML & CSS on Udemy and I love your teaching approach. Bye.
I haven't watched your videos since a year or so, YOU'VE LOST SOME WEIGHT BRO!! Congrats!
We write tests for our backend. There are some for our frontends too but not as extensive. More like if a component was found and whatnot.
Should we call it Personal Home Page or Pre Hypertext Processor?
you going to do more videos on this? specifically php unit testing
While short, your summary of TDD is exactly why we have this tab vs spaces culture around it. Your summary leads everyone to believe all TDD is, is just a chicken and the egg type thing. Write the test first or the production code first, you end up at the same destination. This is flat out wrong. True TDD practitioners know that TDD is more about better software design, among many other things than come from it. Before anyone @ me, go pick up Kent Beck’s book. Pick up Uncle Bob’s Clean Craftsmanship. Work through them and then actually commit to the practice for 30 straight working days. After that, @ me all you want. I’d love to have a conversation, especially for those that still think TDD isn’t necessary or over hyped. Maybe I’ll learn something and gain a different view. Maybe they’ll learn what they thought was TDD wasn’t really TDD and they were lying to themselves. Either way, we’re gonna find out something and learn. Green and growing.
@TraversyMedia What kind of microphone do you use?
I see new video from Traversy Media, I like the video immediately. 👍
Aspire to be more than a like-bot.
Unit Tests, Functional Tests and Performance testing taken very seriously in my backend position.
If you would repeatedly manually test something, and you can write a good test for it, then it makes sense to automate. Technically, there is nothing wrong with tests, but for my own project it's like 98% coding, and 2% comments and tests. Typescript also reduces the value proposition of tests. This all said, testing is better than it used to be because AI is good at writing tests, so you usually get them for free.
It depends on how much damage a faulty build can cause. I don't write tests at all for personal projects because nobody cares if something breaks. But for my job when there are real dollars at stake it's a different question.
TS and AI mean no testing?
My future is secure.
Typescript reduces the value you get from tests... Funny how strict type systems exists in many other programming languages, and testing still seems to be highly valued by teams that use those languages.
Tests serve primarily as another ecosystem for code validation. Similar to how a lab might serve as an environment to validate changes to existing manufacturing processes. No type system replaces or reduces the value of testing.
E2E manual tests after pushing to prod to make sure things still work is 10000% more valuable than unit testing. So many teams I see pushing code and assuming "tests are all automated so we are good" ... then a few minutes/hours later, pager duty alerts flying wild. Now there are 8 people on a call trying to figure out "why"
E2E manual testing does not scale at all. And your argument also holds for E2E manual tests.
It’s not either or, you need both. E2e tests primarily tell you THAT something is wrong but unit tests also tell you WHAT is wrong.
I’m not so much a fan of integration tests though, they tend to be quite flaky and break easily during refactoring
@@avwie132 Stop being a tech bro. They scale fine for 99% of apps inside companies. Show me an app that you can't take a few minutes post launch to go through and check out?
@@krumbergify Unit tests tell you Potentially what is wrong in a given unit of code. That is all. Does nothing for the app as a whole and what the user sees.
@@jamessullenriota few mins? We have web apps with user business processes that can take up to a few hours to complete with: signing of contracts, payments, identification, communication with multiple external agencies. And that is only one of the features. How would I test that in a few mins?
With scale I mean: if you add features to your product your E2E manual regression testing scales linearly. Unless everything remains stable (which it doesn’t because of library upgrades) it is difficult to remove manual tests.
And you mention “post launch”. So you test in production? Mate…
What kind of role do you have that you see “so many teams”?
Do you have any courses especially for mocking functions? Is verry hard to understand in my oppinion
Can a developer use testing inside a version control platform??
My Favourite teacher or whaaat???? 🙂
Hi brother love from India ❤
The Time-Factor might be the most controversial thing. It only seems logical, that you're faster not writing tests, but there comes a tipping point where the technical debt catches up. And, from my experience, introducing testing afterwards is practically impossible.
That's when your time is suddenly at least 70% Bug fixing and praying your fixes don't produce new horrors.
But I can't tell you at which project size that tipping point occurs exactly. It just some sort of six sense you develop over the years as a dev
Testing it important, not so much for the new code that you're introducing but to ensure that existing code is still working as expected.
I don't use TDD, though. I don't think it's viable unless your requirements are very clear which is just not the case in many projects.
Often you have to iterate a couple of times before you arrive at the desired result.
Of course you have to be pragmatic about the scope of your tests. You don't need 100% test coverage.
"not so much for the new code that you're introducing but to ensure that existing code is still working as expected"
absolutely! I would have created prod fires if not for specs failing on me. I hate writing them, but if I still have a job and colleagues that can tolerate my existence, it's thanks to them!
thks for your vids sir. I would add one important point to consider before starting tests or TDD : cost. Doing tests it costs a lot. So it is often the first part of the project to be reduce to save costs
One question: as a Reactjs front end developer should i only do unit testing using react testing library or should i test also integration testing and e2e testing ?
e2e is recommended
🔥
if its workings its working if its not its not
Can you send a resume to my company... so we can blacklist you?
Testing application in multiple ways in different environment is necessary. If things working for you do not meant it would expect to work for others
@@owaisahmed7820 there was testing class in my degree program. 8 people signed but 10 people needed to open the class. nobody cared. nobody needs it.
@@SLRModShop😂 can you send us your company name so we can avoid your fragile environment.
Do not feel a little frustrated because of AI, which may be able to perform the programmer's job in the future!
This is my feeling and I don't know if I am thinking true or just imagining
Hello sar thanks to make this video but I would like to tell you one more important aspect of testing which is accessibility testing accessibility testing is make sure your product accessible with assistive devices for person with disability without accessibility person with disability face many problem to access product I think you are a responsible and respect to person on RUclips please mention in your videos about accessibility I am accessibility tester thank you if we will not provide accessibility then we don't get like Stephen hawkings
Looking healthy dude
Wow Brad your arms are growing MASHALLAH
Oh the accent comes out when he says "shopping cARt"
You lost a good amount of weight. It’s good to see you are taking care of yourself.
I wish more people would discuss BDD over TDD. It's better and more viable. TDD is too loose and open handed. You're attempting to paint yourself into a corner before knowing if you're even in a room.
No rest only test
Sounds like a bodybuilding mantra
gotta test puppeteer with selenium hahaha
no, this automation library called puppeteer is hard to test; manually it takes ages because some automation is complex; need to split that code and make it testaable
Im the only developer for a small company and after 4 years I have yet to write a test for anything.....😂
Most of the time it's not even a choice, but a requirement.
I hate the idea of TDD. I always do it after. Generally I would say just develop quickly and get the functionality working and it will quickly become apparent which areas need testing to ensure reliability etc
me writing codes with 0 test my my last 3 projects lol
Have you lost weight? Looking good, Brad.
First thing I thought too
Gotta love this guy's theme sounds like it's saying, "I am very smart but I talk very monotone". Haha, ok I'll stop.
definitely test, atleast 250mg a week. as for software testing hell naw bruh that shts gay af
I hadn't seen a video from you for a while. You've lost weight, right?
Damn, you seem to have lost alot of weight
You have lose weight. Good to see you
Bro you've lost weight
First