Can't wait to see what you come up with 😉

I tried quitting all chrome tabs and windows and retrying, same issue starting at 18/62. I even tried the following:

rm -rf ~/Library/Caches/Cypress
rm -rf node_modules
npm install

I was pretty confident the above would do it but it didn't. I'm going to try to try some other things before I try clearing all chrome cookies and history. I will update when i'm back on track

Open the activity monitor

there is a chrome process hanging somewhere

closing all tabs is not enough

chrome is a google software it does not want to be quit ever

^^

So you have to tell it explicitly to quit using ctrl-Q

closing all tabs is not enough

Yes, sorry i did Ctrl-Q

And the activity monitor is still showing nothing ?

Okay this is bazar...i was going to take a video of before/after, and when i went to run it for the before video, its working?

Yeah, we really need to get a hang of those orphans chrome instances

it's like the maintainability gods are playing games with me....so disappointed in my mission to get us on track to a maintainable front-end lol

Thanks again for your help, i will push the changes for getting this working now.

no worries

Hey there, first of all. Kudos to the team for the awesome v7 release and the Component Test Runner 👏 , I'm playing around with it this weekend.

Can't wait to see what you make !!... and what you think of it

I have a question that pop out, from what I read

mount

function is similar to the one used on Vue Test Utils, but isn't exactly the same right? I'm trying to setProps to the wrapper but got an error

cmp.setProps is not a function

describe('AsButton', () => {
  let cmp;
  beforeEach(() => {
    cmp = mount(AsButton, {
      propsData: {
        type: btnType.PRIMARY,
        label: `I'm a sexy button`,
      },
    });
  });
  it('renders a secodary button', () => {
    cmp.setProps({
      type: btnType.SECONDARY,
    });

    cy.get('button').should('have.class', 'btn-secondary');
  });
});

In short (and this in not obvious) the cypress mount function calls the mount from VTU but does not return the same object

But you can still access the returned value of mount in

Cypress.vueWrapper

We are working an rerender function on the same idea as testing library that would allow you to do that

Just curious though: - Why do you use setProps instead of another mount? The second mount would probably be safer since you get a fresh instance to test with. - Why test that a class is actually rendering? It feels like testing that vue actually works.

Probably your tests are way more complicated

> Why do you use setProps instead of another mount? the

beforeEach

hook would create a new mount for each test with some default props, sometimes you want to test what happens on a component when a prop value updates. > Why test that a class is actually rendering? It feels like testing that vue actually works. Yep is just an example, as you say the proper tests are more complicated than that.

Did the vueWrapper help you at all?

I did not think of the default values scenario. Thanks for bringing it up!

I manage to access it, but calling the method

setProps

there doesn't trigger changes on the mount

it('renders a primary button', () => {
      mount(AsButton, {
        propsData: {
          type: btnType.PRIMARY,
          label: `I'm a sexy button`,
        },
      });

      Cypress.vueWrapper.setProps({
        type: btnType.SECONDARY,
      });

      cy.wait(1000);

      cy.get('button').should('have.class', 'btn-secondary'); // Fails
    });

🤔

Vue 2 ?