You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to add allure reporting to the framework.
I am getting an error message "ERROR @wdio/local-runner: Failed launching test session: TypeError: ReporterClass is not a constructor"
This is my wdio.conf.js
const path = require("path");
exports.config = {
//
// ====================
// Runner Configuration
// ====================
//
runner: 'local',
port: 4723, // default appium port
services: [
[
'appium',
{
args: {
},
command: 'appium'
}
]
],
//
// ==================
// Specify Test Files
// ==================
// Define which test specs should run. The pattern is relative to the directory
// from which wdio was called.
//
// The specs are defined as an array of spec files (optionally using wildcards
// that will be expanded). The test for each spec file will be run in a separate
// worker process. In order to have a group of spec files run in the same worker
// process simply enclose them in an array within the specs array.
//
// 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: ["./test/specs/AppLogin.js"],
//specs: ["./test/specs/**/.js"],
// 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://saucelabs.com/platform/platform-configurator
//
capabilities: [
{
platformName: "Android",
"appium:deviceName": "Pixel 3 API 31",
"appium:platformVersion": "12.0",
"appium:automationName": "UIAutomator2",
"appium:app": path.join(process.cwd(), "./app/android/app-release.apk"),
},
],
//
// ===================
// Test Configurations
// ===================
// Define all options that are relevant for the WebdriverIO instance here
//
// Level of logging verbosity: trace | debug | info | warn | error | silent
logLevel: "debug",
//
// Set specific log levels per logger
// loggers:
// - webdriver, webdriverio
// - @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/utils
// Level of logging verbosity: trace | debug | info | warn | error | silent
// logLevels: {
// webdriver: 'info',
// '@wdio/appium-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: ["appium"],
// Framework you want to run your specs with.
// The following are supported: Mocha, Jasmine, and Cucumber
// see also: https://webdriver.io/docs/frameworks
//
// Make sure you have the wdio adapter package for the specific framework installed
// before running any tests.
framework: "mocha",
//
// 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
reporters: ['spec', ['allure', {
outputDir: 'allure-results',
disableWebdriverStepsReporting: false,
disableWebdriverScreenshotsReporting: false,
}]],
//
// Options to be passed to Mocha.
// See the full list at http://mochajs.org/
mochaOpts: {
ui: "bdd",
timeout: 400000,
require:["@babel/register"],
},
//
// =====
// 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 {[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 initialized
@param {[type]} execArgv list of string arguments passed to the worker process /
// onWorkerStart: function (cid, caps, specs, args, execArgv) {
// },
/*
Gets executed just after a worker process has exited.
I am trying to add allure reporting to the framework.
I am getting an error message "ERROR @wdio/local-runner: Failed launching test session: TypeError: ReporterClass is not a constructor"
This is my wdio.conf.js
const path = require("path");
exports.config = {
//
// ====================
// Runner Configuration
// ====================
//
runner: 'local',
port: 4723, // default appium port
services: [
[
'appium',
{
args: {
},
command: 'appium'
}
]
],
//
// ==================
// Specify Test Files
// ==================
// Define which test specs should run. The pattern is relative to the directory
// from which
wdio
was called.//
// The specs are defined as an array of spec files (optionally using wildcards
// that will be expanded). The test for each spec file will be run in a separate
// worker process. In order to have a group of spec files run in the same worker
// process simply enclose them in an array within the specs array.
//
// 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, sowdio
// will be called from there.
//
specs: ["./test/specs/AppLogin.js"],
//specs: ["./test/specs/**/.js"],
// 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://saucelabs.com/platform/platform-configurator
//
capabilities: [
{
platformName: "Android",
"appium:deviceName": "Pixel 3 API 31",
"appium:platformVersion": "12.0",
"appium:automationName": "UIAutomator2",
"appium:app": path.join(process.cwd(), "./app/android/app-release.apk"),
},
],
//
// ===================
// Test Configurations
// ===================
// Define all options that are relevant for the WebdriverIO instance here
//
// Level of logging verbosity: trace | debug | info | warn | error | silent
logLevel: "debug",
//
// Set specific log levels per logger
// loggers:
// - webdriver, webdriverio
// - @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/utils
// Level of logging verbosity: trace | debug | info | warn | error | silent
// logLevels: {
// webdriver: 'info',
// '@wdio/appium-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/
(likesome/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: ["appium"],
// Framework you want to run your specs with.
// The following are supported: Mocha, Jasmine, and Cucumber
// see also: https://webdriver.io/docs/frameworks
//
// Make sure you have the wdio adapter package for the specific framework installed
// before running any tests.
framework: "mocha",
//
// 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
reporters: ['spec', ['allure', {
outputDir: 'allure-results',
disableWebdriverStepsReporting: false,
disableWebdriverScreenshotsReporting: false,
}]],
//
// Options to be passed to Mocha.
// See the full list at http://mochajs.org/
mochaOpts: {
ui: "bdd",
timeout: 400000,
require:["@babel/register"],
},
//
// =====
// 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.
/**
/
// onPrepare: function (config, capabilities) {
// },
/*
/
// onWorkerStart: function (cid, caps, specs, args, execArgv) {
// },
/*
/
// onWorkerEnd: function (cid, exitCode, specs, retries) {
// },
/*
/
// beforeSession: function (config, capabilities, specs, cid) {
// },
/*
browser
. It is the perfect place to define custom commands./
// before: function (capabilities, specs,device) {
// },
/*
/
// beforeCommand: function (commandName, args) {
// },
/*
/
// beforeSuite: function (suite) {
// },
/*
/
// beforeTest: function (test, context) {
// },
/*
/
// beforeHook: function (test, context) {
// },
/*
/
// afterHook: function (test, context, { error, result, duration, passed, retries }) {
// },
/*
undefined
{ attempts: 0, limit: 0 }
*/
// afterTest: function(test, context, { error, result, duration, passed, retries }) {
// },
/**
/
// afterSuite: function (suite) {
// },
/*
/
// afterCommand: function (commandName, args, result, error) {
// },
/*
/
// after: function (result, capabilities, specs) {
// },
/*
/
// afterSession: function (config, capabilities, specs) {
// },
/*
/
// onComplete: function(exitCode, config, capabilities, results) {
// },
/*
*/
// onReload: function(oldSessionId, newSessionId) {
// }
};
Can someone help me with this
The text was updated successfully, but these errors were encountered: