Skip to content

Complete Refresh of the Transaction Scripting Examples Repo - #59

Open
lulbai-te wants to merge 4 commits into
masterfrom
transaction-scripting-repo-refresh
Open

Complete Refresh of the Transaction Scripting Examples Repo#59
lulbai-te wants to merge 4 commits into
masterfrom
transaction-scripting-repo-refresh

Conversation

@lulbai-te

Copy link
Copy Markdown
Collaborator

This PR request includes a complete refresh of the transaction scripting examples repo. The goal is to drive users to create tests with more standard and commonly used functionality rather than enumerate all of the possible ways to do something (especially it adds unnecessary complexity that we wouldn't recommend).

For anyone doing a review, be sure to take a look at any removed examples that we still want to keep and we can have a discussion if it was on purpose or how we want to be guiding users/agents with this repo.

@augflore-te

augflore-te commented Aug 24, 2026

Copy link
Copy Markdown

Hi @lulbai-te — as part of DOCS-4772, could PR #59 preserve compatibility stubs at legacy paths that are moved or removed, or is a clean break intentional?

The docs inventory found references to these legacy paths:

  • examples/usingTOTPTwoFactorAuth.js
  • examples/waitForDownload.js
  • examples/switchToNextTab.js
  • examples/switchToTabWithUrl.js
  • examples/scrollElementIntoView.js
  • examples/moveMouseIntoElement.js
  • applications/office-365/onedrive-download.js
  • applications/office-365/sharepoint-login-download.js
  • API-transaction-scripts/

A small deprecation stub or README at each old path that points to the maintained replacement would reduce broken bookmarks and external links. We will still update current product docs to maintained examples and pin historical release-note links to the pre-refresh commit. If compatibility stubs are not appropriate, that does not block the docs changes.

augflore-te

This comment was marked as outdated.

Lulu Bai added 3 commits August 26, 2026 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants