API should be the same, but the subcommand will change. (old one will also still work -- unchanged ) I'll ping you when it comes out so you can play. It'll open up widely in about 4 weeks, but we're trying to get feedback early

oh very cool. definitely - would love to try it! 🙂

Hi everyone, just got here while testing @cypress/vue (1.0.0-alpha.4), Im trying out the manual installation (my client project doesn't use vue-cli) and I'm getting an Unexpected Error occurred:

TypeError: cannot read property 'rules of undefined

From

cypress/plugins/index.js

preprocessor(on, config)

step. Somebody went trough something similar? Thanks in advance

Not using Vue CLI will be tricky @User

Actually I raised a ticket https://github.com/cypress-io/cypress/issues/14973, because the error occurs only in the dist generated file for

preprocessor/webpack.js

, the source coude in the repo is correct

Do you have the webpack config and the integration code inside of plugins?

I need to know what webpack version, too

Essentially this part of your webpack configuration is empty/null

Adding this to your webpack config should work.

module: {
  rules: []
}

We're rewriting this code completely and shipping that very very shortly so we could fix it if this workaround doesn't work. Basically, we are removing preprocessor and all of this "one off" logic that assumes your webpack configuration is in a certain shape. We're switching to webpack-dev-serveer.

It's pretty unusual that webpack contains no rules. I suppose you don't transpile your code with babel or generate scss, etc

Responded in the issue, too.

Thanks for getting on Discord -- we're much better responding on here. Since you're not using a "normal/common" webpack install, would you be interested in testing out our new architecture when it lands? Depending on how big your project is... it's as fast are your dev-server 🙂

Sure thing, is a big one, lets do it

I already sould out the whole idea of e2e to the client and PM, so it's on

LOL

Hmm, this is actually for component testing not E2E.

E2E works with any framework because you have to bundle and serve your app. Component Testing is where you import your components and mount them (like Jest + Vue Test Utils)

I know hehe, wanted to comment that they're already open to testing which is not always easy to convince from business side 😅. I want to substitute the unit testing with this Component Testing that's why I'm interest, e2e are already in progress

Well I'll ping you when it's out ^.^

Hi all, jr dev here trying to experiment with component testing. I am having difficulty getting Bootstrap/Vue to display in my tests. Not sure if I'm missing a loader or not understanding mount options etc.

Score.spec.js:

import bootstrapVue from '@/src/plugins/bootstrap-vue';
mount(Score, {
  use: [bootstrapVue],
  propsData: {
    isEditable: true,
  },
});
Cypress.vue.status.loading = true;

cy.get('div.spinner').should('exist');

^^ Much simplified version. BootstrapVue is Vue.use(bootstrapvue)'d in that plugins folder bootstrap-vue.js file. (applied as plugin to main.js) in Vue CLI app.

I'm just getting plain HTML parts to show up.

Score.vue:

<template>
  <div
    class="form-group my-5 score-editor"
    :class="{
      'spinner spinner-right': status.loading,
      errors: hasErrors,
      success: status.success,
    }"
    v-if="isEditable"
>
  <input ... >
</template>

Will the

@cypress/vue

3.0.0-alpha releases at https://www.npmjs.com/package/@cypress/vue work with Vite? Eager to start testing things out! 😁

Looks like it’s a syntax thing? If you look at the docs the extensions need to be passed in as an extensions object like ‘mount (Score, { extensions: { use... }})

I'll give it a shot.

@User I gave it a shot and basic HTML cy.get() works, but I don't visually see bootstrap element spinner in the window.

oh, catching up to this now!