# Smoke Tests

Smoke tests are quick end-to-end functional tests of a software solution's basic functionality; a failure indicates a serious problem.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How to Configure Playwright Test to run smoke tests, headed tests, and debug versions through scripts in package.json

DevFeed: [How to Configure Playwright Test to run smoke tests, headed tests, and debug versions through scripts in package.json](<https://devfeed.tech/articles/how-to-configure-playwright-test-to-run-smoke-tests-headed-tests-and-debug-versions-through-scripts-in-package-json-22419.md>)

Original publisher: [Read original article](<https://www.tjmaher.com/2026/08/how-to-configure-playwright-test-to-run.html>)

Author: T.J. Maher (noreply@blogger.com)

Published: 2026-08-20T02:13:32Z

Content type: tutorial

Language: en

Sources: [T.J. Maher](<https://devfeed.tech/sources/t-j-maher.md>)

Topics: [Playwright](<https://devfeed.tech/topics/playwright.md>), [Script](<https://devfeed.tech/topics/script.md>), [Bun](<https://devfeed.tech/topics/bun.md>), [Smoke Tests](<https://devfeed.tech/topics/smoke-tests.md>), [test](<https://devfeed.tech/topics/test.md>), [Package manager](<https://devfeed.tech/topics/package-manager.md>)

Tags: [bun](<https://devfeed.tech/tags/bun.md>), [bun-create-playwright](<https://devfeed.tech/tags/bun-create-playwright.md>), [commands](<https://devfeed.tech/tags/commands.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [install](<https://devfeed.tech/tags/install.md>), [playwright](<https://devfeed.tech/tags/playwright.md>), [test](<https://devfeed.tech/tags/test.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

A tutorial on configuring Playwright Test commands in package.json scripts. It demonstrates shortcuts for headed, traced, Chromium, Firefox, WebKit, smoke, debugging, reporting, linting, formatting, and type-checking workflows, and explains using Bun and bunx to run commands.

### Source excerpt

Earlier, we went over how we could create scripts in the package.json file of our Playwright framework to add typechecking, linting, and formatting your code with prettier. Want to see the entire bun-create-playwright project? It is on tinyurl.com/bun-create-playwright! With this post, we will explore how the built-in test runner for Playwright Test can run headed tests, debug versions of tests, and smoke tests. ... and shortcuts for all of these can be set up in the scripts in your package.json! If you are using "bun" as a package manager, as we are in bun-create-playwright, just type out "bun run", a space and then the shortcut such as: bun run test package.json "scripts": { "test": "playwright test", "test:headed": "playwright test --headed", "test:trace": "playwright test --trace on", "test:chromium": "playwright test --project=chromium", "test:firefox": "playwright test --project=firefox", "test:webkit": "playwright test --project=webkit", "test:smoke": "playwright test --project=chromium --grep '@smoke'", "test:flaky": "playwright test --project=chromium --repeat-each=20", "test:ui": "playwright test --ui", "test:debug": "playwright test --debug", "test:failed": "playwright test --last-failed", "test:login": "playwright test tests/login.spec.ts", "test:secure-area": "playwright test tests/secure-area.spec.ts", "report:list": "playwright test --reporter=list", "report:line": "playwright test --reporter=line", "report:dot": "playwright test --reporter=dot", "report:blob": "playwright test --reporter=blob", "report": "playwright show-report", "codegen": "playwright codegen", "lint": "eslint .", "lint:ci": "eslint . --max-warnings 0", "lint:fix": "eslint . --fix", "format": "prettier --write .", "format:check": "prettier --check .", "format:debug": "prettier --check . --log-level debug", "format:diff": "prettier --list-different", "typecheck": "tsc --noEmit" }, bun-create-playwright / package.json Do you need to really set up shortcuts like these? Certainly not! B

## Building On-call: Continually testing with smoke tests

DevFeed: [Building On-call: Continually testing with smoke tests](<https://devfeed.tech/articles/building-on-call-continually-testing-with-smoke-tests-11731.md>)

Original publisher: [Read original article](<https://incident.io/blog/continually-testing-our-product-with-smoke-tests>)

Author: Rory Malcolm

Published: 2024-08-09T10:00:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [Smoke Tests](<https://devfeed.tech/topics/smoke-tests.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [pull-requests](<https://devfeed.tech/topics/pull-requests.md>), [Containers](<https://devfeed.tech/topics/containers.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [building](<https://devfeed.tech/tags/building.md>), [containers](<https://devfeed.tech/tags/containers.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article explains how a product team uses smoke tests to protect the reliability of its On-call product. A full end-to-end suite runs every minute in production and staging, exercises infrastructure and third-party integrations, and also runs for pull requests and deployments using containers. The tests cover core alerting and escalation journeys as well as malformed-input edge cases, helping the team detect regressions and make changes confidently.

### Source excerpt

Launching On-call meant we had to make our system rock-solid from the get-go. Our solution? Smoke tests to let us continually test product health and make sure we're comfortable making changes at pace.

## Firebase App Distribution Introduces Automated Tester (Beta)

DevFeed: [Firebase App Distribution Introduces Automated Tester (Beta)](<https://devfeed.tech/articles/firebase-app-distribution-introduces-automated-tester-beta-16537.md>)

Original publisher: [Read original article](<https://firebase.blog/posts/2024/02/automated-smoke-testing-app-distribution>)

Author: Radhika Advani

Published: 2024-02-21T00:00:00Z

Content type: release

Language: en

Sources: [Firebase Blog](<https://devfeed.tech/sources/firebase-blog.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [Smoke Tests](<https://devfeed.tech/topics/smoke-tests.md>), [Android](<https://devfeed.tech/topics/android.md>), [Testing](<https://devfeed.tech/topics/testing.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [announce](<https://devfeed.tech/tags/announce.md>), [apk](<https://devfeed.tech/tags/apk.md>), [app-distribution](<https://devfeed.tech/tags/app-distribution.md>), [app-quality](<https://devfeed.tech/tags/app-quality.md>), [automated](<https://devfeed.tech/tags/automated.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [firebase-cli](<https://devfeed.tech/tags/firebase-cli.md>), [test-lab](<https://devfeed.tech/tags/test-lab.md>)

### AI overview

Firebase App Distribution introduces Automated Tester (Beta), which runs automated smoke tests on Android app builds across selected devices and API levels. Results include reports with screenshots, video recordings, and issues, with Test Lab rates applying after the daily no-cost cap.

### Source excerpt

News, tutorials, and updates from the Firebase team.

## Retry flaky tests with dotnet test and PowerShell

DevFeed: [Retry flaky tests with dotnet test and PowerShell](<https://devfeed.tech/articles/retry-flaky-tests-with-dotnet-test-and-powershell-20782.md>)

Original publisher: [Read original article](<https://conductofcode.io/post/retry-flaky-tests-with-dotnet-test-and-powershell/>)

Author: {"twitter"=\>"hlaueriksson"}

Published: 2023-03-26T19:00:00Z

Content type: tutorial

Language: en

Sources: [Henrik Lau Eriksson](<https://devfeed.tech/sources/henrik-lau-eriksson.md>)

Topics: [PowerShell](<https://devfeed.tech/topics/powershell.md>), [.NET](<https://devfeed.tech/topics/net.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Smoke Tests](<https://devfeed.tech/topics/smoke-tests.md>), [Playwright](<https://devfeed.tech/topics/playwright.md>), [Selenium](<https://devfeed.tech/topics/selenium.md>)

Tags: [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [cli](<https://devfeed.tech/tags/cli.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [dotnet](<https://devfeed.tech/tags/dotnet.md>), [flaky](<https://devfeed.tech/tags/flaky.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [mstest](<https://devfeed.tech/tags/mstest.md>), [nunit](<https://devfeed.tech/tags/nunit.md>), [playwright](<https://devfeed.tech/tags/playwright.md>), [powershell](<https://devfeed.tech/tags/powershell.md>), [retry](<https://devfeed.tech/tags/retry.md>), [selenium](<https://devfeed.tech/tags/selenium.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [unit-tests](<https://devfeed.tech/tags/unit-tests.md>), [xunit](<https://devfeed.tech/tags/xunit.md>)

### AI overview

This tutorial presents a PowerShell script that uses dotnet test and TRX result files to track failed tests, retry them, report the final result, and allow a configured percentage of failures. It demonstrates the script with NUnit, MSTest, and xUnit.

### Source excerpt

Introducing test.ps1, a script for running flaky tests - Keeps track of failing tests and retries them - Notifies the test framework of the current retry iteration - Makes it possible to accept a certain percentage of failing tests - Outputs the test result in a coherent way

## On behavior verifications

DevFeed: [On behavior verifications](<https://devfeed.tech/articles/on-behavior-verifications-27280.md>)

Original publisher: [Read original article](<https://blog.pchudzik.com/201709/behavior-verifications/>)

Published: 2017-09-06T00:00:00Z

Content type: article

Language: en

Sources: [Paweł Chudzik](<https://devfeed.tech/sources/pawe-chudzik.md>)

Topics: [Refactoring](<https://devfeed.tech/topics/refactoring.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>), [Smoke Tests](<https://devfeed.tech/topics/smoke-tests.md>)

Tags: [integration-test](<https://devfeed.tech/tags/integration-test.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [test](<https://devfeed.tech/tags/test.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

A developer recounts refactoring springmock after its double-definition parsing class accumulated responsibilities. The article explains the resulting test failures and recommends incremental refactoring, integration or smoke tests, and verifying behavior through tests.

### Source excerpt

When I've got some free time I try to add new features to springmock. Lately, after adding some new stuff I realized that double definition parsing class has more than one responsibility (class parsing, naming, definition creation, etc). So I've decided it's time to refactor it and split responsibilities into dedicated classes. Once I did that and tests in the shared kernel started to pass I executed mvn verify just to be sure that everything was working and it wasn't... Read more