• webdriver.io监测下载并删掉下载的文件


    最近要做一个检测下载的自动化...因为框架为webdriover.io 在国内比较少人使用,所以目前只找到了下面这个

    启发来自链接:http://cn.voidcc.com/question/p-cgufghmo-ut.html

    我想知道在单击下载按钮后,如何使用Selenium Webdriver验证是否下载了文件。

    如果你想在本地(在Chrome)实现这一那么答案是“YES ”,你可以做这样的事情:

    在wdio.conf.js(要知道它在哪里得到下载)

    var path = require('path'); 
    
    const pathToDownload = path.resolve('chromeDownloads'); 
    
    // chromeDownloads above is the name of the folder in the root directory 
    exports.config = { 
    capabilities: [{ 
         maxInstances: 1,  
         browserName: 'chrome', 
         os: 'Windows',  
         chromeOptions: { 
          args: [ 
           'user-data-dir=./chrome/user-data', 
          ], 
          prefs: { 
           "download.default_directory": pathToDownload, 
          } 
         } 
        }], 

    而且你的spec文件(要检查的文件被下载或不)

    describe('User can download and verify a file',() =>{ 
    
        before(() => { 
         // Clean up the chromeDownloads folder and create a fresh one 
         fsExtra.removeSync(pathToChromeDownloads); 
         fsExtra.mkdirsSync(pathToChromeDownloads); 
        }); 
    
        it('Download the file',() =>{ 
         // Code to download 
        }); 
    
        it('Verify the file is downloaded',() =>{ 
         // Code to verify 
         // Get the name of file and assert it with the expected name 
        }); 
    }); 

    更多关于FS-EXTRA:https://www.npmjs.com/package/fs-extra

    希望这会有所帮助。

    解决方案:

    20220225
    问题:在没有任何提示的情况下怎么自动化验证chrome下载文件成功?
    3种验证思路:
    1、截取response中的img url查看是否正确(感觉更适用于接口测试)
    2、使用OCR/OpenCV 图像识别的库去识别左下角下载完成的图片
    3、用fs-extra判断文件是否存在

    选择思路3进行实现:先点击下载之后用node.js下的fs-extra的exist()方法判断
    但是,默认下载的地址是C盘,但是不同的电脑不同的系统mac,linux,win无法兼容不同的盘符
    找了一晚上的js获取系统文件盘,获取chrome默认下载位置..找不到..
    最后说明因为安全性基本上不会让大家有获取到文件路径的入口和权限
    当前的框架是在wdio.conf.js来用js修改浏览器下载文件的位置在chrome参数的prefs配置'download.default_directory':‘D:\\’
    更改浏览器的默认下载文件位置,然后再直接在这个地址上校验文件 process.cwd()获取当前运行程序地址
    直接将内容下载在这个地址上

    关键步骤:
    1.设置chrome参数的prefs配置'download.default_directory':‘D:\\’更改运行代码时下载时默认下载位置
    2.获取当前程序运行的位置process.cwd() 将其转化为字符串 process.cwd().toString()
    3.用例数据回收,下载后的资源分类到指定文件夹,验证结束后销毁,fs.emptyDir()

    wdio.conf.js

    exports.config = {
        //
        // ====================
        // Runner Configuration
        // ====================
        //
        // WebdriverIO allows it to run your tests in arbitrary locations (e.g. locally or
        // on a remote machine).
        runner: 'local',
        //
        // ==================
        // Specify Test Files
        // ==================
        // Define which test specs should run. The pattern is relative to the directory
        // from which `wdio` was called. Notice that, if you are calling `wdio` from an
        // NPM script (see https://docs.npmjs.com/cli/run-script) then the current working
        // directory is where your package.json resides, so `wdio` will be called from there.
        //
        specs: [
            './tests/**/*.feature'
        ],
        // Patterns to exclude.
        exclude: [
            // 'path/to/excluded/files'
        ],
        //
        // ============
        // Capabilities
        // ============
        // Define your capabilities here. WebdriverIO can run multiple capabilities at the same
        // time. Depending on the number of capabilities, WebdriverIO launches several test
        // sessions. Within your capabilities you can overwrite the spec and exclude options in
        // order to group specific specs to a specific capability.
        //
        // First, you can define how many instances should be started at the same time. Let's
        // say you have 3 different capabilities (Chrome, Firefox, and Safari) and you have
        // set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec
        // files and you set maxInstances to 10, all spec files will get tested at the same time
        // and 30 processes will get spawned. The property handles how many capabilities
        // from the same test should run tests.
        //
        maxInstances: 10,
        //
        // If you have trouble getting all important capabilities together, check out the
        // Sauce Labs platform configurator - a great tool to configure your capabilities:
        // https://docs.saucelabs.com/reference/platforms-configurator
        //
        capabilities: [{
        
            // maxInstances can get overwritten per capability. So if you have an in-house Selenium
            // grid with only 5 firefox instances available you can make sure that not more than
            // 5 instances get started at a time.
            maxInstances: 5,
            //
            browserName: 'chrome',
            'goog:chromeOptions': {
                args: process.env.HEADLESS == 'true' ? ["--headless", "--no-sandbox", "--disable-dev-shm-usage", "--disable-gpu", "--window-size=1530,860"] : ["--window-size=1530,860"],
                prefs: {
                    'intl.accept_languages': 'en,en_US',
                    'download.default_directory':process.cwd().toString()+'\\testdata\\downloadResources'
                }
            },
            acceptInsecureCerts: true
            // If outputDir is provided WebdriverIO can capture driver session logs
            // it is possible to configure which logTypes to include/exclude.
            // excludeDriverLogs: ['*'], // pass '*' to exclude all driver session logs
            // excludeDriverLogs: ['bugreport', 'server'],
        }],
        //
        // ===================
        // Test Configurations
        // ===================
        // Define all options that are relevant for the WebdriverIO instance here
        //
        // Level of logging verbosity: trace | debug | info | warn | error | silent
        logLevel: 'error',
        //
        // Set specific log levels per logger
        // loggers:
        // - webdriver, webdriverio
        // - @wdio/applitools-service, @wdio/browserstack-service, @wdio/devtools-service, @wdio/sauce-service
        // - @wdio/mocha-framework, @wdio/jasmine-framework
        // - @wdio/local-runner
        // - @wdio/sumologic-reporter
        // - @wdio/cli, @wdio/config, @wdio/sync, @wdio/utils
        // Level of logging verbosity: trace | debug | info | warn | error | silent
        // logLevels: {
        //     webdriver: 'info',
        //     '@wdio/applitools-service': 'info'
        // },
        //
        // If you only want to run your tests until a specific amount of tests have failed use
        // bail (default is 0 - don't bail, run all tests).
        bail: 0,
        //
        // Set a base URL in order to shorten url command calls. If your `url` parameter starts
        // with `/`, the base url gets prepended, not including the path portion of your baseUrl.
        // If your `url` parameter starts without a scheme or `/` (like `some/path`), the base url
        // gets prepended directly.
        baseUrl: 'http://localhost',
        //
        // Default timeout for all waitFor* commands.
        waitforTimeout: 10000,
        //
        // Default timeout in milliseconds for request
        // if browser driver or grid doesn't send response
        connectionRetryTimeout: 120000,
        //
        // Default request retries count
        connectionRetryCount: 3,
        //
        // Test runner services
        // Services take over a specific job you don't want to take care of. They enhance
        // your test setup with almost no effort. Unlike plugins, they don't add new
        // commands. Instead, they hook themselves up into the test process.
        services: [['selenium-standalone', {skipSeleniumInstall: process.argv.indexOf('--skipSeleniumInstall') != -1 ? process.argv[process.argv.indexOf('--skipSeleniumInstall') + 1] : false }]],
        
        // Framework you want to run your specs with.
        // The following are supported: Mocha, Jasmine, and Cucumber
        // see also: https://webdriver.io/docs/frameworks.html
        //
        // Make sure you have the wdio adapter package for the specific framework installed
        // before running any tests.
        framework: 'cucumber',
        //
        // The number of times to retry the entire specfile when it fails as a whole
        // specFileRetries: 1,
        //
        // Delay in seconds between the spec file retry attempts
        // specFileRetriesDelay: 0,
        //
        // Whether or not retried specfiles should be retried immediately or deferred to the end of the queue
        // specFileRetriesDeferred: false,
        //
        // Test reporter for stdout.
        // The only one supported by default is 'dot'
        // see also: https://webdriver.io/docs/dot-reporter.html
        reporters: [['allure', {
            outputDir: './reports/allure-results',
            disableWebdriverStepsReporting: false,
            disableWebdriverScreenshotsReporting: false,
        }]],
    
    
        //
        // If you are using Cucumber you need to specify the location of your step definitions.
        cucumberOpts: {
            // <string[]> (file/dir) require files before executing features
            require: ['./tests/steps/**/*.js'],
            // <boolean> show full backtrace for errors
            backtrace: false,
            // <string[]> ("extension:module") require files with the given EXTENSION after requiring MODULE (repeatable)
            requireModule: ['@babel/register'],
            // <boolean> invoke formatters without executing steps
            dryRun: false,
            // <boolean> abort the run on first failure
            failFast: false,
            // <string[]> (type[:path]) specify the output format, optionally supply PATH to redirect formatter output (repeatable)
            format: ['pretty'],
            // <boolean> hide step definition snippets for pending steps
            snippets: true,
            // <boolean> hide source uris
            source: true,
            // <string[]> (name) specify the profile to use
            profile: [],
            // <boolean> fail if there are any undefined or pending steps
            strict: false,
            // <string> (expression) only execute the features or scenarios with tags matching the expression
            tagExpression: '',
            // <number> timeout for step definitions
            timeout: 60000,
            // <boolean> Enable this config to treat undefined definitions as warnings.
            ignoreUndefinedDefinitions: false
        },
        
        //
        // =====
        // Hooks
        // =====
        // WebdriverIO provides several hooks you can use to interfere with the test process in order to enhance
        // it and to build services around it. You can either apply a single function or an array of
        // methods to it. If one of them returns with a promise, WebdriverIO will wait until that promise got
        // resolved to continue.
        /**
         * Gets executed once before all workers get launched.
         * @param {Object} config wdio configuration object
         * @param {Array.<Object>} capabilities list of capabilities details
         */
        // onPrepare: function (config, capabilities) {
        // },
        /**
         * Gets executed before a worker process is spawned and can be used to initialise specific service
         * for that worker as well as modify runtime environments in an async fashion.
         * @param  {String} cid      capability id (e.g 0-0)
         * @param  {[type]} caps     object containing capabilities for session that will be spawn in the worker
         * @param  {[type]} specs    specs to be run in the worker process
         * @param  {[type]} args     object that will be merged with the main configuration once worker is initialised
         * @param  {[type]} execArgv list of string arguments passed to the worker process
         */
        // onWorkerStart: function (cid, caps, specs, args, execArgv) {
        // },
        /**
         * Gets executed just before initialising the webdriver session and test framework. It allows you
         * to manipulate configurations depending on the capability or spec.
         * @param {Object} config wdio configuration object
         * @param {Array.<Object>} capabilities list of capabilities details
         * @param {Array.<String>} specs List of spec file paths that are to be run
         */
        // beforeSession: function (config, capabilities, specs) {
        // },
        /**
         * Gets executed before test execution begins. At this point you can access to all global
         * variables like `browser`. It is the perfect place to define custom commands.
         * @param {Array.<Object>} capabilities list of capabilities details
         * @param {Array.<String>} specs        List of spec file paths that are to be run
         * @param {Object}         browser      instance of created browser/device session
         */
        before() {
            browser.maximizeWindow(); //set window to max size
            // require('dotenv').config() //Initialize environment information
        },
        /**
         * Runs before a WebdriverIO command gets executed.
         * @param {String} commandName hook command name
         * @param {Array} args arguments that command would receive
         */
        // beforeCommand: function (commandName, args) {
        // },
        /**
         * Runs before a Cucumber feature
         */
        // beforeFeature: function (uri, feature, scenarios) {
        // },
        /**
         * Runs before a Cucumber scenario
         */
        // beforeScenario: function (uri, feature, scenario, sourceLocation, context) {
        // },
        /**
         * Runs before a Cucumber step
         */
        // beforeStep: function ({ uri, feature, step }, context) {
        // },
        /**
         * Runs after a Cucumber step
         */
        afterStep: function ({ uri, feature, step },
            context, { error, result, duration, passed, retries }) {
            if (error) {
                browser.takeScreenshot();  
            }
        },
        /**
         * Runs after a Cucumber scenario
         */
        afterScenario: async function (uri, feature, scenario, result, sourceLocation, context) {
            const {TestrailTool} = require('./tests/utils/testrail-support')
            TestrailTool.collectResult(scenario,result)
        },
        /**
         * Runs after a Cucumber feature
         */
        // afterFeature: function (uri, feature, scenarios) {
        // },
        
        /**
         * Runs after a WebdriverIO command gets executed
         * @param {String} commandName hook command name
         * @param {Array} args arguments that command would receive
         * @param {Number} result 0 - command success, 1 - command error
         * @param {Object} error error object if any
         */
        // afterCommand: function (commandName, args, result, error) {
        // },
        /**
         * Gets executed after all tests are done. You still have access to all global variables from
         * the test.
         * @param {Number} result 0 - test pass, 1 - test fail
         * @param {Array.<Object>} capabilities list of capabilities details
         * @param {Array.<String>} specs List of spec file paths that ran
         */
        after: async function (result, capabilities, specs) {
            const {TestrailTool} = require('./tests/utils/testrail-support')
            const {TESTRAIL_CONFIG} = require('./config')
            if (TESTRAIL_CONFIG.email){
                await TestrailTool.uploadAllResults(TESTRAIL_CONFIG)
            }
        },
        /**
         * Gets executed right after terminating the webdriver session.
         * @param {Object} config wdio configuration object
         * @param {Array.<Object>} capabilities list of capabilities details
         * @param {Array.<String>} specs List of spec file paths that ran
         */
        // afterSession: function (config, capabilities, specs) {
        // },
        /**
         * Gets executed after all workers got shut down and the process is about to exit. An error
         * thrown in the onComplete hook will result in the test run failing.
         * @param {Object} exitCode 0 - success, 1 - fail
         * @param {Object} config wdio configuration object
         * @param {Array.<Object>} capabilities list of capabilities details
         * @param {<Object>} results object containing test results
         */
        // onComplete: function(exitCode, config, capabilities, results) {
        // },
        /**
        * Gets executed when a refresh happens.
        * @param {String} oldSessionId session ID of the old session
        * @param {String} newSessionId session ID of the new session
        */
        //onReload: function(oldSessionId, newSessionId) {
        //}
    }

    page-object

    import assert from "assert"
    const fs = require('fs-extra');
    const rootPath = process.cwd().toString()+'\\testdata\\downloadResources'
    const file1 = rootPath+'\\Åndedrettssystemet.flipchart'
    const file2 = rootPath+'\\Pacote de recursos - Mamiferos 3.as4a'
    const file3 = rootPath+'\\eurekamath_1_m6_l28_01.pwb'
    class DownloadResources {
        get operateResourceButton(){ return $$('.icon-round-more_vert-24px')[0]}
        get downloadResourceButton(){ return $$('.ant-dropdown-menu-item')[0]}
        get downloadFlipResourceButton(){ return $$('.ant-dropdown-menu-item')[1]}
        get downloadDescription(){return $('#description')}
        downloadFirstResource(keyword){
            this.operateResourceButton.click()
            if (keyword=='Flipcharts'){
                this.downloadFlipResourceButton.click()
            }else{
                this.downloadResourceButton.click()
            }
        }
    
        verifyFirstResourceHasDownload(keyword) {
            switch(keyword) {
                case 'Flipcharts':
                    fs.pathExists(file1)
                      .then((exists) => assert.strictEqual(exists,true))
                      .catch((e) => console.log(e));
                     break;
                case 'ResourcePacks':
                    fs.pathExists(file2)
                        .then((exists) => assert.strictEqual(exists,true))
                        .catch((e) => console.log(e));
                     break;
                case 'Whiteboardfiles':
                    fs.pathExists(file3)
                        .then((exists) => assert.strictEqual(exists,true))
                        .catch((e) => console.log(e));
                     break;
            }
        }
    
        removeDownloadResources(){
            fs.emptyDir(rootPath, err => {
                if (err) return console.error(err)
                console.log('Remove download resources success!')
            })
        }
    }
    export default new DownloadResources()
  • 相关阅读:
    记一次线上Kafka消息堆积踩坑总结
    golang Time to String
    转MongoDB 使用Skip和limit分页
    golang mongodb (mgo)插入或读取文档的字段值为空(nil)问题解决
    Golang 中操作 Mongo Update 的方法
    基础知识
    Linux安全之SSH 密钥创建及密钥登录
    ssh配置authorized_keys后仍然需要输入密码的问题
    SSH隧道技术----端口转发,socket代理
    社会信息化环境下的IT新战略
  • 原文地址:https://www.cnblogs.com/chenxiaomeng/p/15956211.html
Copyright © 2020-2023  润新知