Remove deprecated I.retry() and I.limitTime() (#5567)

* Remove deprecated I.retry() and I.limitTime()

Both were deprecated in 3.x; removed in 4.x as part of the major break.
The step options API (step.retry() / step.timeout() passed as the last
step argument) is the replacement and behaves identically without the
3.x footgun of leaking config onto the following step.

- lib/actor.js: drop retry()/limitTime() and now-unused imports
- typings: remove retry()/limitTime() actor declarations
- migrate runner fixtures and actor unit test to step.retry()/step.timeout()
- migration-4.md: document removal with 3.x->4.x mappings
- fix stale I.retry()/I.limitTime() references in docs and plugin doc-comments

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Fix dtslint: drop removed clickLink/retry/limitTime from typings tests

- typings/tests/helpers/Playwright.types.ts + PlaywrightTs.types.ts:
  remove clickLink expectType assertions (clickLink was removed from
  the Playwright helper)
- typings/tests/actor.types.ts: drop the now-invalid I.retry() calls;
  document that retry()/limitTime() were removed (I is `any` here so
  the removal cannot be asserted at the type level)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: DavertMik <davert@testomat.io>
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: 3 people

docs/custom-helpers.md

@@ -212,7 +212,7 @@ _before() {
 }
 ```
 
-`recorder.retry` acts similarly to `I.retry()` and accepts the same parameters. It expects the `when` parameter to be set so it would handle only specific errors and not to retry for every failed step.
+`recorder.retry` registers a retry rule at the recorder level and accepts the same options as `step.retry()` (`retries`, `minTimeout`, `when`, ...). It expects the `when` parameter to be set so it would handle only specific errors and not to retry for every failed step.
 
 Retry rules are available in array `recorder.retries`. The last retry rule can be disabled by running `recorder.retries.pop()`;
 

docs/detox.md

@@ -31,7 +31,7 @@ CodeceptJS provides next features over standard Detox:
 
 * **Unified API**. The same test can be executed in Appium or Detox. Unified API helps different teams to use the same syntax and easy port tests from one engine to another.
 * [Interactive pause](/basics#pause). When starting/stopping an application takes a long time, debugging and writing tests can be hard. CodeceptJS solves this by pausing an execution and letting you try different commands and locators. With this feature a test can be writtern during one running session.
-* [Auto-retries](/basics#retries) using `retryFailedStepPlugin` and `I.retry()`
+* [Auto-retries](/basics#retries) using the `retryFailedStep` plugin and `step.retry()`
 * **Cross-Platform testing** - one test can be executed on different engines. When needed, platform-specific actions and locators can be easily applied.
 
 ## A Test

docs/index.md

@@ -100,7 +100,7 @@ Scenario('Create a new store', async ({ I, login, SettingsPage }) => {
   I.fillField('Email', faker.internet.email());
   I.fillField('Telephone', faker.phone.phoneNumberFormat());
   I.selectInDropdown('Status', 'Active');                     // Use custom methods
-  I.retry(2).click('Create');                                 // Retry flaky step
+  I.click('Create', step.retry(2));                           // Retry flaky step
   I.waitInUrl('/settings/setup/stores');                      // Explicit waiter
   I.see(storeName, '.settings');                              // Assert text present inside an element (located by CSS)
   const storeId = await I.grabTextFrom('#store-id');          // Use await to get information from browser

docs/migration-4.md

@@ -473,18 +473,26 @@ Use one of:
 
 The `customLocators` strategy registration in Playwright config is removed. Use the `customLocator` plugin or built-in ARIA locators (`{ role: 'button', name: 'Submit' }`).
 
-### `I.retry()` is deprecated
+### `I.retry()` and `I.limitTime()` removed
 
-Use the step options API:
+Both were deprecated in 3.x and are **removed in 4.x**. They configured the *next* step through a chained call; the replacement is the step options API — pass a `step.*` config as the **last argument** of the step itself.
 
 ```js
 import step from 'codeceptjs/steps'
 
-I.click('Submit', step.retry(3))
-I.fillField('Email', 'a@b.c', step.timeout(10))
+// 3.x (removed)            →  4.x
+I.retry(3).click('Submit')  //  I.click('Submit', step.retry(3))
+I.limitTime(10).fillField('Email', 'a@b.c') // I.fillField('Email', 'a@b.c', step.timeout(10))
+```
+
+`step.*` configs are also composable with the other step options:
+
+```js
 I.click('Add', step.opts({ elementIndex: 2 }))
 ```
 
+The behavior is unchanged — the option applies only to the step it is attached to, not to subsequent steps (this also fixes the 3.x footgun where `I.retry()` could leak retry settings onto the following step). `recorder.retry()` is unaffected and remains available for custom helpers.
+
 ### `within` Is Now an Effect
 
 In 3.x, `within(...)` was a global statement available everywhere. In 4.x it's an effect alongside `tryTo`, `retryTo`, and `hopeThat`. Under `noGlobals: true` you must import it:

docs/plugins/retryFailedStep.md

@@ -61,7 +61,7 @@ plugins: {
 
 #### Disable Per Test
 
-This plugin can be disabled per test. In this case you will need to stet `I.retry()` to all flaky steps:
+This plugin can be disabled per test. In this case you will need to add `step.retry()` to all flaky steps:
 
 Use scenario configuration to disable plugin for a test
 

docs/plugins/stepTimeout.md

@@ -29,7 +29,7 @@ Run tests with plugin enabled:
 
 *   `timeout` - global step timeout, default 150 seconds
 
-*   `overrideStepLimits` - whether to use timeouts set in plugin config to override step timeouts set in code with I.limitTime(x).action(...), default false
+*   `overrideStepLimits` - whether to use timeouts set in plugin config to override step timeouts set in code with `I.action(..., step.timeout(x))`, default false
 
 *   `noTimeoutSteps` - an array of steps with no timeout. Default:
 

docs/timeouts.md

@@ -118,7 +118,7 @@ plugins: {
 When multiple timeouts are configured, CodeceptJS applies them in priority order:
 
 1. **stepTimeoutHard** — plugin with `overrideStepLimits: true`
-2. **codeLimitTime** — `step.timeout()` or `I.limitTime()`
+2. **codeLimitTime** — `step.timeout()`
 3. **stepTimeoutSoft** — plugin with `overrideStepLimits: false`
 4. **testOrSuite** — global test/suite timeout
 

lib/actor.js

@@ -1,10 +1,7 @@
 import Step, { MetaStep } from './step.js'
 import recordStep from './step/record.js'
-import retryStep from './step/retry.js'
 import { methodsOfObject } from './utils.js'
-import { TIMEOUT_ORDER } from './timeout.js'
 import event from './event.js'
-import store from './store.js'
 import output from './output.js'
 import Container from './container.js'
 
@@ -30,38 +27,6 @@ class Actor {
       output.say(msg, `${color}`)
     })
   }
-
-  /**
-   * set the maximum execution time for the next step
-   * @function
-   * @param {number} timeout - step timeout in seconds
-   * @return {this}
-   * @inner
-   */
-  limitTime(timeout) {
-    if (!store.timeouts) return this
-
-    console.log('I.limitTime() is deprecated, use step.timeout() instead')
-
-    event.dispatcher.prependOnceListener(event.step.before, step => {
-      output.log(`Timeout to ${step}: ${timeout}s`)
-      step.setTimeout(timeout * 1000, TIMEOUT_ORDER.codeLimitTime)
-    })
-
-    return this
-  }
-
-  /**
-   * @function
-   * @param {*} [opts]
-   * @return {this}
-   * @inner
-   */
-  retry(opts) {
-    console.log('I.retry() is deprecated, use step.retry() instead')
-    retryStep(opts)
-    return this
-  }
 }
 
 /**

lib/plugin/retryFailedStep.js

@@ -77,7 +77,7 @@ const RETRY_PRIORITIES = {
  *
  * #### Disable Per Test
  *
- * This plugin can be disabled per test. In this case you will need to stet `I.retry()` to all flaky steps:
+ * This plugin can be disabled per test. In this case you will need to add `step.retry()` to all flaky steps:
  *
  * Use scenario configuration to disable plugin for a test
  *

lib/plugin/stepTimeout.js

@@ -32,7 +32,7 @@ const defaultConfig = {
  * #### Configuration:
  *
  * * `timeout` - global step timeout, default 150 seconds
- * * `overrideStepLimits` - whether to use timeouts set in plugin config to override step timeouts set in code with I.limitTime(x).action(...), default false
+ * * `overrideStepLimits` - whether to use timeouts set in plugin config to override step timeouts set in code with `I.action(..., step.timeout(x))`, default false
  * * `noTimeoutSteps` - an array of steps with no timeout. Default:
  *     * `amOnPage`
  *     * `wait*`