Find all conference videos here: vuetoronto.com/videos Signup for conference updates here: vuetoronto.com Want to learn Vue 3.0 from the experts? bit.ly/2v8QALV
Coming from a PHP background I was familiar with TDD but how to apply these principles to Vue development had never really 'clicked' for me until watching this video. So thanks for helping me to have that 'aha' moment!
I loved this. I was trying TDD but was not confident in the approach but the way you explained made it very clear to me why this is necessary and also how to approach front-end components Test-driven development.
Excellent Talk, Thanks! 1. You are awesome! 2. The issue with TDD and Testing in global is the setup configuration and sometimes the time to run and get feedback from them. when u pass it over (as u say) the tests written is easier and faster Thanks for your explanation, very clear and U R Rock in live coding :)
Thank you Chen! Unit tests should run fast, because they test small units and don't touch I/O. In my presentation, they took a bit longer than usual because somehow, when I set my computer offline, Jest suddenly became slow. In reality and on a daily basis, they're blazing fast.
As an (embarrassingly recent) adopter of TDD, I now kinda laugh at myself from all the years I spent thinking I couldn;'t afford the time to write the tests first. It does take time, obviously. But it takes at least one order of magnitude less time than it does to debug and fix broken code, especially when the fixes on one part start breaking another. It's like that great Jack Bergman quote: "There's never enough time to do it right, but there's always enough time to do it over."
This just serves to remind me that I'm really bad at writing tests. That is, only one project I've ever written has used tests. And they're out of date. And they're badly written tests. I should put the ideas in this video into practice before I push to production again..
Why is "a non-regression test is always nice"? If we used storybook's storyshots (which is actually using a jest feature) with puppeteer, we would get for free al the tests, that Sarah wrote in this demo. I love storyshots:D I barely need e2e or unit tests next to them to feel confident about my code.
Find all conference videos here: vuetoronto.com/videos
Signup for conference updates here: vuetoronto.com
Want to learn Vue 3.0 from the experts? bit.ly/2v8QALV
That’s a very good introduction (and motivation) to TDD, applied to front-end development with Vue.js. Thank you, Sarah!
Coming from a PHP background I was familiar with TDD but how to apply these principles to Vue development had never really 'clicked' for me until watching this video. So thanks for helping me to have that 'aha' moment!
I loved this. I was trying TDD but was not confident in the approach but the way you explained made it very clear to me why this is necessary and also how to approach front-end components Test-driven development.
Excellent Talk, Thanks!
1. You are awesome!
2. The issue with TDD and Testing in global is the setup configuration and sometimes the time to run and get feedback from them.
when u pass it over (as u say) the tests written is easier and faster
Thanks for your explanation, very clear and U R Rock in live coding :)
Thank you Chen! Unit tests should run fast, because they test small units and don't touch I/O. In my presentation, they took a bit longer than usual because somehow, when I set my computer offline, Jest suddenly became slow. In reality and on a daily basis, they're blazing fast.
BTW i am just wrote a medium article full influence to your presentation in Angular :) [off course full feed back to u]
So Thanks 4 your expression :)
Great talk and the message is delivered very well! Thanks you Sarah.
Thanks for sharing a drop of knowledge, rich content.
Congratulations!
very well presented.
Success!
Omg she's so awesome! I would watch her teach stuff all day
I wrote first test suite for my vue components yesterday. took me only 2 days XD
Thank you! Its really simple to understand with 3 steps
Jeez I wish I could speak that succinctly. Great talk.
As an (embarrassingly recent) adopter of TDD, I now kinda laugh at myself from all the years I spent thinking I couldn;'t afford the time to write the tests first.
It does take time, obviously. But it takes at least one order of magnitude less time than it does to debug and fix broken code, especially when the fixes on one part start breaking another.
It's like that great Jack Bergman quote: "There's never enough time to do it right, but there's always enough time to do it over."
Love it! Finally the 2nd step makes sense to me!
This really helps how we code and helps see how to structure or refactor it.
This just serves to remind me that I'm really bad at writing tests. That is, only one project I've ever written has used tests. And they're out of date. And they're badly written tests.
I should put the ideas in this video into practice before I push to production again..
Thank you Sarah for the introduction, VueConf Toronto please upload code samples as well with the video.
2 minutes into the video and I'm already convinced
one of the best, Sarah
thank you!
Why is "a non-regression test is always nice"?
If we used storybook's storyshots (which is actually using a jest feature) with puppeteer, we would get for free al the tests, that Sarah wrote in this demo.
I love storyshots:D I barely need e2e or unit tests next to them to feel confident about my code.
really nice presentation. thx!
Great talk.
Great talk!
Good talk
thanks !
ty
A really good one!
gooooooooood, love you
Great talk
Does anyone know the vscode theme she is using?
yes mam
great great great
When I visit tailwind page I see her face now I'm seeing her video look more fater
Now I know who is displayed on the main page of Tailwind 😂
99% TDD 1% Vue testing
1:37 Uncle Bob said that not Yoda :)