𝗛𝗼𝘄 𝗜 𝗥𝘂𝗻 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗧𝗲𝘀𝘁𝘀 𝗼𝗻 𝗦𝘁𝗮𝗴𝗶𝗻𝗴

𝗛𝗼𝘄 𝗜 𝗥𝘂𝗻 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗧𝗲𝘀𝘁𝘀 𝗼𝗻 𝗦𝘁𝗮𝗴𝗶𝗻𝗴

Staging is your final check before production. Code often passes CI tests but fails on staging. Real data and strict rules cause these failures. Automated tests on staging stop emergency rollbacks.

Common problems in staging:

• Flaky tests from unstable tools.
• Mixed up test data.
• Expired tokens.
• Config drift.

Focus on these tests:

• Smoke tests: Check if users log in and finish main flows.
• Regression tests: Ensure old features still work.
• API tests: Check how services talk to each other.
• Performance checks: Check response times with tools like k6.

How to set it up:

• Match configs to production.
• Reset data for every run.
• Trigger tests automatically in your CI pipeline.

Tools to use:

• Playwright for modern apps.
• Selenium for browser flexibility.
• Cypress for fast frontend feedback.
• BrowserStack or Sauce Labs for real device testing.

Final tips for you:

• Use parameters instead of hard-coded URLs.
• Align feature flags between staging and production.
• Fix flaky tests instead of ignoring them.

Prioritize tests based on business risk. Focus on payments and core transactions. Stable staging makes releases feel controlled.

Source: https://dev.to/crissy-joshua/how-i-run-automated-tests-on-staging-without-disrupting-releases-5ac6