# vue
- b
bulky-sundown-74498
04/15/2021, 4:42 PMThe problem with setting up things globally that you forget about is that. quickly, they become hard to track - b
bulky-sundown-74498
04/15/2021, 4:43 PMIf it can be explicit and you do not loose too much time or maintainability by making it explicit, it creates tracability of failure, which is what you want to help you code faster - b
bulky-sundown-74498
04/15/2021, 4:43 PMTDD is supposed to make you more productive, not loose time tracking which setup you failed 😉 - l
little-shampoo-74692
04/15/2021, 4:44 PMIt's what we do in Jest as well. I just didn't see the 'new' in the actual export. An easy thing to miss. - b
bulky-sundown-74498
04/15/2021, 4:44 PMSo now, you could setup a
within your mount function to see what setup is workingdebugger; - l
little-shampoo-74692
04/15/2021, 4:45 PMWhoever is working on this, does that all make sense? - l
little-shampoo-74692
04/15/2021, 4:46 PM@User you can setup repetitive code as recursive to help speed it up. It is what it is. - l
little-shampoo-74692
04/15/2021, 4:49 PMI think this is one of the reasons we hate testing so much. We have to test each and every input and output and it's tedious (not to mention somewhat of just a self-reassurance). - l
little-shampoo-74692
04/15/2021, 4:50 PMReminds me of checking my own answers in math class. (And who enjoys that?) - b
bulky-sundown-74498
04/15/2021, 4:50 PMIn my case I hated component testing... until I tried it with cypress - b
bulky-sundown-74498
04/15/2021, 4:50 PMwill post a blogpost soon about it - b
bulky-sundown-74498
04/15/2021, 4:51 PMIt is now less painful to find what I want to test and why - b
bulky-sundown-74498
04/15/2021, 4:51 PMbecause I see it - b
bulky-sundown-74498
04/15/2021, 4:51 PMand can inspect/debug - r
red-refrigerator-13075
04/15/2021, 4:51 PMWell I think the mount helper that @User sid could work, because setting up each test file with the same line to add vue-i18n doesn't make sense for me but maybe in the future that could change - l
little-shampoo-74692
04/15/2021, 4:51 PMI'm interested to dive in. I haven't had a chance to look at it. But I've discussed it with my team and we may be implementing it into our flow. I think there is some concern that with browser-lead testing there may be a desire to test "is that really rendering blue", etc.. - r
red-refrigerator-13075
04/15/2021, 4:52 PMThat could be awesome, because as I said, many Vue developers will face the same issue jejeje - l
little-shampoo-74692
04/15/2021, 4:52 PMAs for myself, I see this as the future of testing (thank goodness!). - l
little-shampoo-74692
04/15/2021, 4:54 PMSo let's discuss TDD with Cypress. - l
little-shampoo-74692
04/15/2021, 4:55 PMUsually we have some Dom elements build (or at least in mind) for what we're trying to do. - r
red-refrigerator-13075
04/15/2021, 4:55 PMThe next step after making the helper function is going to be to add vuetify to the mix and see what other errors come out to bother you guys again hehehehe. - l
little-shampoo-74692
04/15/2021, 4:59 PMYou know what? I'm just going to have to dive into this and see what it's all about. I don't really think there's much more to it. Looks like you have a PS course, so I'll be spending some time with that to get up to speed. - r
red-refrigerator-13075
04/15/2021, 5:03 PM@User Any idea how can you listen and assert emits like in vue-test-utils? With vue-test-utils:expect(wrapper.emitted('click')).toBeTruthy() - b
bulky-sundown-74498
04/15/2021, 5:10 PMmount(SuperComponent).then(({wrapper}) => { }) - b
bulky-sundown-74498
04/15/2021, 5:11 PMcf Jess's talk - r
red-refrigerator-13075
04/15/2021, 5:11 PMok ok I'll try it later - b
bulky-sundown-74498
04/15/2021, 5:12 PMBut this should be fine - b
bulky-sundown-74498
04/15/2021, 5:16 PMactually my bad... - b
bulky-sundown-74498
04/15/2021, 5:17 PMCopy codejs mount(SuperComponent).then(() => { cy.vue().then(wrapper => expect(wrapper.emitted('click')).to.have.length(1)) })