#16 | Migrate from V7 to V8 | WebdriverIO Mocha Framework

Поделиться
HTML-код
  • Опубликовано: 26 янв 2023
  • In this video, we will learn how to #migrate from #webdriverio #v7 to #v8 and update necessary config files.
    In this #tutorial series, we will be building a fully functional #testautomation #framework in #typescript using #webdriverio and integrate our tests with #mocha and Allure Report.
    Important Link:
    ------------------------
    webdriver.io/blog/2022/12/01/...
    www.npmjs.com/package/npm-che...
    adamcoster.com/blog/commonjs-...
    Git Repository: github.com/sadabnepal/Webdriv...
    Connect with me on LinkedIn: / sadabnepal
    #webdriverio #typescript #nodejs #wdio #mocha #async #testingvideo #videotutorial #testing #testautomation #npm
  • НаукаНаука

Комментарии • 12

  • @tanyasharma4836
    @tanyasharma4836 Год назад +1

    Hi, I have updated my dependencies while updating webdriverio 7 to 8 and observed that there is a change in expect condition. It is not allowing custom error messages to be passed in expect condition. But earlier, I was able to pass. Can you please help me in knowing the exact reason for the same?

  • @tuna1867
    @tuna1867 Год назад

    Thanks for the video. But Im getting an error now
    ERROR @wdio/config:ConfigParser: Failed loading configuration file: ...configs/wdio.conf.ios.generated.ts: Cannot use import statement outside a module
    > import type { Options } from '@wdio/types'
    Any ideas how to fix it? :)

  • @crazyshotss1297
    @crazyshotss1297 Год назад +1

    I am getting no spec file error while upgrading my wdio cucumber typescript framework from v7 to v8. Do you have any solution for that?

    • @TestAutomationHub
      @TestAutomationHub  Год назад

      more detail can help to give proper solution but from what i understand it's file path issue (probably step definition). Check if that is correct. I hope you followed all steps mentioned in webdriver.io/blog/2022/12/01/webdriverio-v8-released

  • @milanradusin4289
    @milanradusin4289 Год назад

    Hmm, now I have a problem with dotenv library, it's like the system doesn't see the env variables

    • @TestAutomationHub
      @TestAutomationHub  Год назад

      to help with issue i need to know where you storing env variable (command line or .env file) and how you are trying to read the variable

    • @milanradusin4289
      @milanradusin4289 Год назад

      @@TestAutomationHub I''m storing variables in .env files and read that with process.env.NAMEOFVARIABLE from the code. All was perfect in v7 but now ...

    • @TestAutomationHub
      @TestAutomationHub  Год назад

      @@milanradusin4289 try using www.npmjs.com/package/dotenv

  • @lamisamamou239
    @lamisamamou239 Год назад

    I cant migrate to v8 with v7 config ( babel, package.json, wdio.conf.js and .js spec files).
    Any idea. Thanks

    • @prash20052005noob
      @prash20052005noob 9 месяцев назад

      This is hard . Its better to drop that framework and try a new one from scratch

    • @TestAutomationHub
      @TestAutomationHub  9 месяцев назад

      I have done it successfully. There is no big change from 7-8

    • @prash20052005noob
      @prash20052005noob 9 месяцев назад

      @@TestAutomationHub Can you share some insights. Its not that easy I believe. Our files are Js and they are mix of CommonJS and ES6 module JS.
      The new config files from WDIO are throwing issues "ERROR @wdio/config:ConfigParser: Failed loading configuration file:" which are not resolvable unless we create new project with latest WDIO/CLI setup wizard.