QAble

Browse by type

Explore all services
Functional
Functional Testing
End-to-end feature validation
Software Testing
Full-stack QA across disciplines
Software QA
Process, standards & audit QA
Independent Testing
Vendor-neutral V&V & sign-off
Cyber Security Testing
Pen testing & exploit validation
Enterprise Testing
ERP, CRM & core platform QA
Manual Testing
Human-driven QA testing
Exploratory Testing
Discover hidden edge cases
User Acceptance Testing
Business-aligned validation
Usability Testing
Real user experience testing
UI/UX Testing
Interface & interaction QA
Accessibility Testing
WCAG compliance testing
Accessibility Audit
Compliance gap assessment
Accessibility Remediation
Fix accessibility violations
Digital Accessibility
End-to-end inclusive design QA
Security & VAPT
Vulnerability assessment
VAPT Testing
Penetration testing & compliance
Performance Testing
Load & stress testing
Non-Functional Testing
Performance, security & reliability
Compatibility Testing
Cross-device & browser QA
Scalability Testing
Capacity & growth QA
Agile Testing
Sprint-aligned QA
Localization Testing
Language & regional QA
Digital Testing
Digital experience QA

What's New

Solution

Tesbo-X, Playwright Automation Framework

Intelligent test selection, parallel CI execution, and rich trace reporting unified in a single automation system.

Try for Free →
View all services
About UsWhy QAbleCertificationsCareers
Knowledge HubBlogQAble WeeklyCase StudiesEbooksUtilities
BetterBugs
BetterBugs
Tesbo-X
Tesbo-X
Talk to QA Advisor
Browse the Knowledge Hub74 resources
/Test Cases/Embedded firmware update test cases

Test cases

Firmware update test cases, for the device that will not boot

Twenty eight cases covering power loss during the write and during first boot, automatic rollback and health confirmation, signature verification and anti rollback, battery thresholds, ordered multi component updates, configuration migration, staged rollouts, halt on failure and a documented recovery path.

28cases/8coverage types/13state cases/FreeCSV download

All 28 test cases, ready to copy

Free to use and adapt, no sign-up. Download as CSV or Markdown, or copy it straight into your own tooling.

Last updated

28 worked examples

FW-01

Complete an update on a healthy device

TypeFunctionalPriorityHigh
Test data
A current device updated to the next release over the air
Expected result
Downloads, verifies, installs and reboots into the new version, and the reported version matches the installed image exactly.
FW-02

Survive power loss during the write

TypeStatePriorityHigh
Test data
Cut power at the start, middle and end of the flash write
Expected result
Device boots in every case, on the previous image if the new one is incomplete. This single case is what separates a recoverable fleet from a recall.
FW-03

Survive power loss during the reboot into new firmware

TypeStatePriorityHigh
Test data
Cut power during the switch between images and during first boot
Expected result
Bootloader falls back to the known good image rather than leaving the device in a state where neither partition is marked valid.
FW-04

Roll back automatically when new firmware fails to boot

TypeStatePriorityHigh
Test data
An image that boots but fails its health check, and one that does not boot at all
Expected result
Both revert to the previous image within the watchdog window, and the failure is reported once connectivity returns.
FW-05

Confirm the new image before marking it good

TypeStatePriorityHigh
Test data
A new image that boots and passes checks, and one that boots but cannot reach the network
Expected result
Image is only marked permanent after a successful health check including connectivity, otherwise a working but unreachable device is unrecoverable remotely.
FW-06

Refuse unsigned or tampered firmware

TypeSecurityPriorityHigh
Test data
An unsigned image, one signed by the wrong key, and a valid image with one byte altered
Expected result
All refused before any write to flash, with signature verification performed on the device rather than trusted from the delivery channel.
FW-07

Refuse a downgrade to a vulnerable version

TypeSecurityPriorityHigh
Test data
A correctly signed but older image containing a known vulnerability
Expected result
Refused through anti rollback protection, since a valid signature on old firmware is otherwise a supported path back to a fixed vulnerability.
FW-08

Verify the image after writing, before switching

TypeSecurityPriorityHigh
Test data
Corrupt the written image on flash before the reboot
Expected result
Checksum or signature is verified from flash rather than only on the downloaded stream, so a bad write is caught before it becomes the active image.
FW-09

Resume an interrupted download

TypeStatePriorityHigh
Test data
Interrupt the download at 60 per cent, then reconnect
Expected result
Resumes from the interruption point rather than restarting, which matters when the device is on a metered or very slow connection.
FW-10

Complete an update over a constrained link

TypePerformancePriorityHigh
Test data
An update delivered over the slowest supported connection with high packet loss
Expected result
Completes within the stated window without exhausting the device data allowance, and the device remains functional throughout the download.
FW-11

Refuse to update below a safe battery level

TypeBoundaryPriorityHigh
Test data
Attempt an update at 5 per cent battery and while on external power
Expected result
Refused on battery below the documented threshold and permitted on external power, since running out mid write is the most common cause of a dead device.
FW-12

Defer an update while the device is in use

TypeStatePriorityHigh
Test data
Trigger an update while the device is performing its primary function
Expected result
Deferred to a safe moment or the user is asked, since interrupting an active safety or medical function to install an update is not acceptable.
FW-13

Update dependent components in the correct order

TypeBoundaryPriorityHigh
Test data
A release updating both application firmware and a radio or coprocessor image
Expected result
Ordered so the device remains recoverable at every intermediate point, and a failure partway does not leave two components on incompatible versions.
FW-14

Migrate stored configuration across versions

TypeCompatibilityPriorityHigh
Test data
Device settings and calibration data written by the previous version
Expected result
Migrated and preserved, and a rollback leaves the older firmware able to read what the newer one wrote rather than failing on an unknown format.
FW-15

Update from the oldest firmware still in the field

TypeCompatibilityPriorityHigh
Test data
The oldest shipped version updated directly to the current release
Expected result
Succeeds, or the required intermediate steps are enforced automatically, since devices in the field skip many releases.
FW-16

Preserve buffered data across the update

TypeStatePriorityHigh
Test data
Unsynced readings held on the device when the update begins
Expected result
Buffer survives the update and syncs afterwards, rather than being wiped because the storage layout changed between versions.
FW-17

Stage a rollout to a small cohort first

TypeStatePriorityHigh
Test data
A rollout targeted at a small percentage of the fleet
Expected result
Only the cohort receives it, and cohort membership is stable so a device does not move in and out of the rollout between check ins.
FW-18

Halt a rollout in progress

TypeStatePriorityHigh
Test data
Stop a rollout after failures are detected in the first cohort
Expected result
No further devices start the update within the stated window, and devices mid update either complete safely or roll back cleanly.
FW-19

Detect a failing rollout automatically

TypeStatePriorityHigh
Test data
A cohort where a proportion of devices fail to report after updating
Expected result
Rollout pauses on the documented failure threshold rather than continuing to the whole fleet, which is the difference between an incident and a recall.
FW-20

Avoid every device downloading at once

TypePerformancePriorityHigh
Test data
A rollout released to a large cohort simultaneously
Expected result
Downloads are staggered with randomised delay so the distribution endpoint and the local network are not saturated in the same minute.
FW-21

Report update status accurately

TypeStatePriorityHigh
Test data
Devices in downloading, verifying, installing, succeeded, rolled back and failed states
Expected result
Each is distinguishable in the fleet view, and a device that has gone quiet mid update is shown as unknown rather than as still installing indefinitely.
FW-22

Recover a device that has failed repeatedly

TypeStatePriorityHigh
Test data
A device that has rolled back from the same update three times
Expected result
Stops attempting automatically, is flagged for intervention, and does not loop indefinitely consuming bandwidth and battery.
FW-23

Provide a documented recovery path

TypeStatePriorityHigh
Test data
A device that will not boot either image
Expected result
A documented recovery mode exists and works, so the worst case is a support procedure rather than a physical replacement.
FW-24

Protect the update transport

TypeSecurityPriorityHigh
Test data
Intercept the download, present an invalid certificate, and redirect to another host
Expected result
Device validates the server certificate and refuses the redirect, and signature verification means transport compromise alone cannot install firmware.
FW-25

Refuse an update targeted at a different hardware revision

TypeNegativePriorityHigh
Test data
An image built for another hardware variant or region
Expected result
Refused on a hardware compatibility identifier before writing, since installing the wrong variant is a reliable way to brick a device permanently.
FW-26

Keep secrets out of the firmware image

TypeSecurityPriorityHigh
Test data
Inspect the distributed image for credentials, keys and endpoints
Expected result
No shared secret or private key is present, since the image is distributed publicly and can be extracted by anyone who owns a device.
FW-27

Keep the update audit trail complete

TypeSecurityPriorityHigh
Test data
A rollout including successes, rollbacks and a halt
Expected result
Each device records which version it ran and when, so a field failure can be tied to a specific image rather than inferred from a release date.
FW-28

Communicate update state to the user

TypeAccessibilityPriorityMedium
Test data
A device with a minimal interface updating, and one where the update fails
Expected result
Progress and outcome are indicated through whatever the device has, and a failure is distinguishable from an ordinary fault rather than appearing as an unexplained restart.

What goes in each field

ID

Required

Stable identifier, prefixed by module.

Test case

Required

What is being verified, in one line.

Type

Functional, negative, boundary, security, state, performance, accessibility or compatibility. Use it to check coverage is spread rather than clustered on the happy path.

Priority

Risk based, with recoverability first. Anything that can leave a device unable to boot, accept unsigned firmware, or brick a fleet through a staged rollout is High, because the remedy is physical rather than a redeploy.

Test data

The specific values, including the invalid and boundary ones.

Expected result

Required

The precise observable outcome, including message text where the wording itself is the requirement.

How To Use This

Cut the power halfway through

This is the only set here where the worst outcome is physical. A device that will not boot has to be collected, opened or replaced.

Pull power during the flash write

At the start, the middle and the end. The device must boot on the previous image every time. This single case is the difference between a recoverable fleet and a recall.

Ship an image that boots but cannot connect

A device that passes its own health check and cannot reach the network is unrecoverable remotely. Connectivity has to be part of confirming the image is good.

Sign an old vulnerable version correctly

A valid signature on old firmware is a supported path straight back to a vulnerability you already fixed. Anti rollback protection is what closes it.

Fail a cohort deliberately

The rollout must pause on its own when devices stop reporting. Continuing to the whole fleet after the first cohort fails is how an incident becomes a recall.

What Most Sets Miss

Why firmware defects need a truck

Every other set in this collection describes defects that can be fixed with a deployment. This one does not. A device that will not boot has to be physically collected, opened or replaced, and if the fault reached the whole fleet then the cost is measured in logistics rather than engineering hours. That inverts the usual priorities: recoverability comes before functionality, and the first case is not whether the update works but whether the device survives the update failing.

Power loss during the write is the scenario everything else is arranged around. An A and B partition scheme with a bootloader that only switches after verification means an interrupted write leaves the previous image intact and bootable. Getting this wrong is not a rare edge case: devices lose power, batteries die, and users unplug things. The related case is confirming the new image rather than assuming it: an image that boots but cannot reach the network is functionally bricked from your point of view, because you can no longer send it anything, so connectivity belongs in the health check that marks the image permanent.

Firmware security has one property that application security does not: the image is distributed publicly, so anyone who owns a device can extract it. That makes any embedded secret a fleet wide secret. Signature verification has to happen on the device before writing, because trusting the delivery channel means transport compromise becomes firmware compromise. And anti rollback matters more than it sounds, since a correctly signed older image is a legitimate path back to a vulnerability that was already patched.

Finally, rollouts are a safety mechanism rather than a convenience. Staging to a small cohort, halting automatically when devices stop reporting, and staggering downloads so the fleet does not saturate the distribution endpoint in one minute are all cheap to build and expensive to omit. The case worth running deliberately is the failing cohort: if the rollout does not pause on its own, the operator has to notice and intervene faster than the rollout progresses, and that is not a reliable control.

Suggest an improvement

Testing embedded or connected hardware?

QAble tests firmware delivery end to end, including interrupted writes, rollback behaviour, signature and anti rollback enforcement and staged fleet rollouts.

Embedded testing services

More test case sets

View all

Test cases for a login page

Test cases25 cases across functional, negative, boundary, security, session and accessibility paths, including account enumeration and lockout.

Test cases for a registration form

Test cases28 cases covering validation, duplicate accounts, email verification, password rules and the enumeration leak most signup forms ship with.

Test cases for search functionality

Test cases28 cases across relevance, partial and fuzzy matching, filters, pagination, empty states, injection attempts and performance under load.

Test cases for a shopping cart

Test cases27 cases on quantity limits, price recalculation, stock changes, coupon stacking, guest to account merge and cart persistence.

Test cases for checkout and payment

Test cases30 cases including 3D Secure, declines, timeouts, duplicate charges, idempotency, refunds and partial captures.

Test cases for file upload

Test cases28 cases on size and type limits, spoofed content types, malicious filenames, progress, resume, virus scanning and storage limits.

Test cases for forgot password

Test cases26 cases on reset token expiry, single use enforcement, session invalidation and the enumeration and rate limit gaps that are routine here.

Test cases for OTP verification

Test cases26 cases on expiry, resend throttling, attempt limits, code reuse, delivery failure and the brute force window teams forget to close.

Test cases for user roles and permissions

Test cases26 cases on horizontal and vertical privilege checks, direct object access, role changes mid-session and permission inheritance.

Test cases for form validation

Test cases27 rules-based cases on required fields, length and numeric boundaries, client and server parity, hidden field tampering and error accessibility.

Test cases for a date picker

Test cases26 cases on timezone shifts, ambiguous day and month order, impossible dates, min and max limits, leap years and keyboard operation.

Test cases for pagination

Test cases24 cases on ordering stability, records changing mid-session, page size caps, deep offset cost, permission-filtered totals and state restore.

Test cases for push notifications

Test cases26 cases on app states, deep link routing, token release on sign out, lock screen privacy, preferences, provider failures and platform differences.

Test cases for reports and data export

Test cases25 cases on permission filtering in the file, spreadsheet formula injection, encoding, typed numbers and dates, row limits and audit logging.

Test cases for a chatbot

Test cases28 cases on paraphrased intents, context, fallback loops, human handoff, policy grounding, prompt injection and data scoping.

Test cases for net banking transactions

Test cases28 cases on duplicate debits from a retried request, concurrent transfers against one balance, daily limits across channels, beneficiary cooling periods, second factor binding and reconciliation.

Test cases for wallet and UPI payments

Test cases28 cases on payments that time out with no response, idempotency on retry, racing balances, caps across devices, collect request fraud, mandates and refunds.

Test cases for insurance claim submission

Test cases28 cases on coverage at the date of loss, waiting periods, deductibles and sub limits, exclusions and riders, duplicate claims and settlement reconciliation.

Test cases for patient records in an EHR

Test cases28 cases on duplicate detection and merge, wrong patient entry, units of measure, allergy and interaction alerting, break glass access and audit of reads.

Test cases for CRM lead management

Test cases28 cases on duplicate leads under concurrency, routing and the unrouted fallback, round robin races, territory visibility, conversion and bulk import.

Test cases for an ERP purchase order

Test cases28 cases on approval thresholds, amendments that must reset approval, budget commitment races, over receipt tolerance, three-way match and duplicate invoices.

Test cases for OTT video playback

Test cases28 cases on bitrate recovery after a dip, DRM renewal mid stream, concurrent stream limits and leaked slots, resume conflicts, ad cue points and offline expiry.

Test cases for game level progression

Test cases28 cases on save corruption during a crash write, cloud save conflicts, offline queue replay, unlock gating, currency exploits and purchase restore.

Test cases for a REST API

Test cases28 cases on status code correctness, cross tenant resource access, mass assignment, idempotent retries, cursor pagination, rate limits and contract drift.

Test cases for SSO and social login

Test cases28 cases on linking an account on an unverified email, state and code replay, redirect allow lists, token signature and issuer, deprovisioning and session rotation.

Test cases for subscription and billing

Test cases28 cases on mid cycle proration, duplicate and out of order webhooks, renewal double charges, dunning and grace, trials, coupons, metered usage and tax.

Test cases for data tables, filters and sorting

Test cases28 cases on unstable sorts across pages, filters that must reset pagination, selection surviving a filter change, bulk action scope and export fidelity.

Test cases for session timeout and concurrent login

Test cases28 cases on tokens that survive sign out, refresh token reuse, idle against absolute lifetime, multi tab expiry, session limits and remote revocation.

Test cases for a multi step form wizard

Test cases28 cases on values lost to back navigation, refresh and session expiry, step skipping, server side revalidation, duplicate submission and conditional branches.

Test cases for email verification

Test cases28 cases on token reuse and expiry, invalidating earlier links, account enumeration, header injection, safe address change and mail scanner prefetching.

Test cases for dashboards and analytics widgets

Test cases28 cases on reconciling against source rows, widgets that disagree, timezone aggregation, zero baselines, no data shown as zero and permission leaks in aggregates.

Test cases for booking and reservation

Test cases28 cases on concurrent bookings for the last slot, inventory holds that leak, payment without a booking, cancellation boundaries and channel sync.

Test cases for mobile app install and update

Test cases28 cases on migration chains across skipped versions, crashes during post upgrade migration, forced update lockouts, deep links and clean reinstall.

Test cases for accessibility (WCAG 2.2 AA)

Test cases28 cases on keyboard only completion, focus management, live region announcements, contrast, reflow at 320 pixels, target size and screen reader verification.

Test cases for performance and load

Test cases28 cases on spikes with no ramp, recovery after peak, soak and leak detection, pool exhaustion, cold caches, retry storms and data correctness under load.

Test cases for the OWASP Top 10

Test cases28 cases on broken access control, mass assignment, injection across every input surface, credential stuffing, session invalidation, SSRF and exposed secrets.

Test cases for cross browser compatibility

Test cases28 cases on storage that throws in private mode, blocked third party cookies, engine date parsing, mobile viewport units, in app browsers and ad blockers.

Test cases for database and data integrity

Test cases28 cases on uniqueness under concurrency, lost updates, counter races, orphaned rows, migration and backfill safety, replica lag and verified restores.

Test cases for localisation and multi language support

Test cases28 cases on text expansion, concatenated sentences, plural rules, locale date parsing, decimal separators, right to left layout, collation and encoding.

Test cases for outbound webhooks

Test cases28 cases on retry backoff and dead letter stores, one dead consumer degrading the pipeline, payload signing and replay windows, out of order delivery and endpoint SSRF.

Test cases for background jobs and queues

Test cases28 cases on work outliving the visibility timeout, idempotent handlers, poison messages, priority starvation, scheduler overlap across instances and graceful drain.

Test cases for real time features and websockets

Test cases28 cases on messages lost in the reconnect gap, half open connections, per channel authorisation, tokens expiring mid connection, backpressure and fanout across instances.

Test cases for file storage and media processing

Test cases28 cases on signed URL scope and expiry, serving before scanning completes, content type sniffing, metadata stripping, orphaned objects and derivative failures.

Test cases for CSV import and bulk operations

Test cases28 cases on reruns duplicating successes, delimiters inside quoted fields, byte order marks, leading zeros, ambiguous dates and bulk action scope.

Test cases for feature flags and progressive rollout

Test cases28 cases on unreachable flag services, unstable bucketing, rollouts that reshuffle users, kill switch latency, server and client mismatch and stale flags.

Test cases for Android app lifecycle and permissions

Test cases28 cases on state lost to process death, configuration changes, permanent permission denial, revocation while backgrounded, doze and battery restrictions.

Test cases for iOS app lifecycle and permissions

Test cases28 cases on the keychain surviving uninstall, suspended termination, limited photo access, allow once location, app switcher snapshots and biometric invalidation.

Test cases for wearable app sync

Test cases28 cases on data recorded away from the phone, duplicate records on resync, full buffers, clock drift, health permissions, battery budgets and unworn readings.

Test cases for VR and AR experiences

Test cases28 cases on the frame rate comfort floor, tracking loss, guardian boundaries, involuntary camera movement, AR anchor drift and spatial data privacy.

Test cases for IoT device pairing and telemetry

Test cases28 cases on offline buffering and reconnect floods, fleet wide reconnection storms, shared credentials, wrong device clocks and stale queued commands.

Test cases for user profile and account settings

Test cases28 cases on partial saves reported as success, optimistic updates the server rejected, mass assignment through a profile form, avatar content inspection and session invalidation.

Test cases for account deletion and data export

Test cases28 cases on export links that must be authorised and expiring, deletion cascading to storage, caches, logs and processors, grace periods, legal holds and deadlines.

Test cases for consent and cookie management

Test cases28 cases on cookies and tracking requests firing before consent, reject parity with accept, tag manager bypass, withdrawal, cached banners and server side forwarding.

Test cases for notification preferences and delivery

Test cases28 cases on opt outs honoured on one channel and ignored on another, marketing sent as transactional, unsubscribe scope, imports resetting consent and digest timezones.

Test cases for admin impersonation and support access

Test cases28 cases on actions attributed to the customer instead of the admin, credential exposure, chained and upward impersonation, session expiry and immutable access records.

Test cases for audit logs and activity history

Test cases28 cases on forged entries through log injection, immutability and tamper detection, actor attribution across impersonation and jobs, retention and legal holds.

Want your update path proven, not assumed?

QAble covers functional, state and security paths with ISTQB-certified engineers. Start with a free QA audit of your device platform.

Talk to QA Advisor