Unable to run describe block in parallel when in single spec file

[jphalak]

Hello,
Automation for mobile app
I am trying to run the describe blocks in parallel of a single spec file.
I have tried adding maxInstances and maxInstancesPerCapability but still those are running sequentially

Below is my baseConfig
import { browser } from '@wdio/globals'; export const baseConfig = { // // ==================== // Runner Configuration // ==================== // WebdriverIO supports running e2e tests as well as unit and component tests. runner: 'local', autoCompileOpts: { autoCompile: true, tsNodeOpts: { project: './tsconfig.json', transpileOnly: true, }, }, // ===================== // Server Configurations // ===================== // Host address of the running Selenium server. This information is usually obsolete as // WebdriverIO automatically connects to localhost. Also, if you are using one of the // supported cloud services like Sauce Labs, Browserstack, Testing Bot or LambdaTest you don't // need to define host and port information because WebdriverIO can figure that out // according to your user and key information. However, if you are using a private Selenium // backend you should define the host address, port, and path here. // // // ================= // Service Providers // ================= // WebdriverIO supports Sauce Labs, Browserstack, Testing Bot and LambdaTest (other cloud providers // should work too though). These services define specific user and key (or access key) // values you need to put in here in order to connect to these services. // // // If you run your tests on Sauce Labs you can specify the region you want to run your tests // in via the regionproperty. Available short handles for regions areus(default),euandapac. // These regions are used for the Sauce Labs VM cloud and the Sauce Labs Real Device Cloud. // If you don't provide the region it will default for the us`

//
// ==================
// Specify Test Files
// ==================
// Define which test specs should run. The pattern is relative to the directory
// of the configuration file being run.
//
// 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.
//
// The path of the spec files will be resolved relative from the directory of
// of the config file unless it's absolute.
//
specs: ['./test/specs/app/**/*.tsx'],

suites: {
login: ['./test/specs/app/LoginTests//*.tsx'],
p0: ['./test/specs/app//p0..tsx'],
p1: ['./test/specs/app/**/p1..tsx'],
},

// 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.
//
product: 'appAutomation',
maxInstances: 4,

// maxInstancesPerCapability: 2,
// wdio:maxInstances:6,
//
// 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
//
//
// ===================
// 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:8080',
//
// Default timeout for all waitFor* commands.
waitforTimeout: 10000,
//
// Default timeout in milliseconds for request
// if browser driver or grid doesn't send response
connectionRetryTimeout: 600000,
//
// Default request retries count
connectionRetryCount: 1,
//
// 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', 'visual', 'rerun'],

// 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: 'jasmine',

//
// 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 spec files 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' }]],

// Options to be passed to Mocha.
// See the full list at http://mochajs.org/
jasmineOpts: {
defaultTimeoutInterval: 600000,
},

//
// =====
// 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.} capabilities list of capabilities details
  /
  // onPrepare: function (config, capabilities) {
  // },
  /*
• Gets executed before a worker process is spawned and can be used to initialize 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 {object} caps object containing capabilities for session that will be spawn in the worker
• @param {object} specs specs to be run in the worker process
• @param {object} args object that will be merged with the main configuration once worker is initialized
• @param {object} 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.
• @param {string} cid capability id (e.g 0-0)
• @param {number} exitCode 0 - success, 1 - fail
• @param {object} specs specs to be run in the worker process
• @param {number} retries number of retries used
  /
  // onWorkerEnd: function (cid, exitCode, specs, retries) {
  // },
  /*
• 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.} capabilities list of capabilities details
• @param {Array.} specs List of spec file paths that are to be run
• @param {string} cid worker id (e.g. 0-0)
  /
  // beforeSession: function (config, capabilities, specs, cid) {
  // },
  /*
• 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.} capabilities list of capabilities details
• @param {Array.} specs List of spec file paths that are to be run
• @param {object} browser instance of created browser/device session
  /
  // before: function (capabilities, specs) {
  // },
  /*
• 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) {
  // },
  /*
• Hook that gets executed before the suite starts
• @param {object} suite suite details
  /
  // beforeSuite: function (suite) {
  // },
  /*
• Function to be executed before a test (in Mocha/Jasmine) starts.
  */

/**

• Hook that gets executed before a hook within the suite starts (e.g. runs before calling
• beforeEach in Mocha)
  /
  // beforeHook: function (test, context, hookName) {
  // },
  /*
• Hook that gets executed after a hook within the suite starts (e.g. runs after calling
• afterEach in Mocha)
  /
  // afterHook: function (test, context, { error, result, duration, passed, retries }, hookName) {
  // },
  /*
• Function to be executed after a test (in Mocha/Jasmine only)
• @param {object} test test object
• @param {object} context scope object the test was executed with
• @param {Error} result.error error object in case the test fails, otherwise undefined
• @param {*} result.result return object of test function
• @param {number} result.duration duration of test
• @param {boolean} result.passed true if test has passed, otherwise false
• @param {object} result.retries information about spec related retries, e.g. { attempts: 0, limit: 0 }
  */
  afterTest: async function (
  test,
  context,
  { error, result, duration, passed, retries },
  ) {
  await browser.reloadSession();
  },

/**

• Hook that gets executed after the suite has ended
• @param {object} suite suite details
  /
  // afterSuite: function (suite) {
  // },
  /*
• 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.} capabilities list of capabilities details
• @param {Array.} specs List of spec file paths that ran
  /
  / after: function (result, capabilities, specs) {

}, /
/*

• Gets executed right after terminating the webdriver session.
• @param {object} config wdio configuration object
• @param {Array.} capabilities list of capabilities details
• @param {Array.} 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.} capabilities list of capabilities details
• @param {} 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) {
  // }
  /*
• Hook that gets executed before a WebdriverIO assertion happens.
• @param {object} params information about the assertion to be executed
  /
  // beforeAssertion: function(params) {
  // }
  /*
• Hook that gets executed after a WebdriverIO assertion happened.
• @param {object} params information about the assertion that was executed, including its results
  */
  // afterAssertion: function(params) {
  // }
  };
  `

This is my capabilities config
`import { baseConfig } from './wdio.conf.app';

export const config = {
...baseConfig,
hostname: 'mobile-hub.lambdatest.com',
port: 80,
path: '/wd/hub',
baseUrl: 'https://mobile-hub.lambdatest.com',
user: process.env.LT_USERNAME,
key: process.env.LT_ACCESS_KEY,

capabilities: [
{
'lt:options': {
deviceName: '.*',
isRealMobile: true,
app: process.env.APP_ID,
platformName: 'Android',
automationName: 'UiAutomator2',
appiumVerison: '2.1.3',
build: process.env.BUILD_ID,
region: 'US',
w3c: true,
enableCustomTranslation: true,
},
},
],

services: [
...baseConfig.services,
[
'lambdatest',
{
setSessionStatus: true,
tunnel: true,
},
],
],
};
`

[christian-bromann]

I am trying to run the describe blocks in parallel of a single spec file.

WebdriverIO doesn't support running parallel describe blocks within a single file. The project runs every spec file and every capability in a single worker process and do not plan to move away from this concept as it would require us to implement our own framework runner which we don't have the capacity to do so.

Let me know if you have further questions.

[jphalak]

can we run it block in parallel then?