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 think retryFailedStep should be disabled in TryTo block ,but when I use the laster version of CodeceptJS , retryFailedStep works fine in Tryto block.
What do you get instead?
Details
CodeceptJS version: 3.5.7
NodeJS Version: v20.3.1
Operating System: macos 13.4.1
appium 2.0.0-rc.4
Configuration file:
// load env variables - this should be the first line of config
require('dotenv-extended').config({
path: './tests/acceptance/config/codecept.dev.env',
defaults: './tests/acceptance/config/codecept.env',
});
require('ts-node/register');
@kobenguyent quick question: what is the reasoning behind disabling retryFailedStep if tryTo is enabled?
the way i see it: the main benefit of retryFailedStep is a convenient way to write less verbose code and get more leeway in timing sensitive scenarios. for instance, when clicking a submit button in a dynamically validated form, one would usually have to wait until the submit button gets enabled (I.waitForEnabled). instead, i can just click it and rely on the retries no matter how long the form validation takes. why shouldn't this approach of writing tests apply tryTo blocks?
I guess the nature of tryTo is to return true/false immediately of a given step and won't fail the test.
And let's say there is "Accept Cookie" banner which may surprisingly appear on a page. You use tryTo to handle test better and don't want your test to fail unexpectedly yet to retry multiple times to make sure the banner either appears or not right?
What are you trying to achieve?
I think retryFailedStep should be disabled in TryTo block ,but when I use the laster version of CodeceptJS , retryFailedStep works fine in Tryto block.
What do you get instead?
Details
// load env variables - this should be the first line of config
require('dotenv-extended').config({
path: './tests/acceptance/config/codecept.dev.env',
defaults: './tests/acceptance/config/codecept.env',
});
require('ts-node/register');
const { configure, cleanReports } = require('codeceptjs-configure');
const REPORT_OUTPUT_DIR = './tests/acceptance/report';
let conf = {
name: 'Rakuma E2E Sanity Android Test',
// tests: './tests/acceptance/specs//.spec.ts',
output: REPORT_OUTPUT_DIR,
};
exports.config = configure.create(conf);
The text was updated successfully, but these errors were encountered: