Technology & Testing Core B · Official guidance Platform: Web

React

React is a JavaScript library for component-based interfaces. Data, props, or state changes can update the screen. It is not ReAct.

See how it works
You might call it React.jsReact UI

See how it works

Original worked exampleReact

Another example

A support console combines a ticket list, conversation panel, and reply form. Server data and draft input have clear owners.

Main parts

  1. 01Code or behavior under test
  2. 02Observable evidence
  3. 03Coverage, failure, and recovery

Use it when

Use React when its components and tools fit the interactions, rendering method, and team workflow.

Do not use it when

Do not put every value in state or replace clear data flow with effects. Static pages may not need it.

Name used in code

components + props + state + reconciliation

Before you ship

Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback.

Request you can copy

Outcome: Use or review React as a technical building block that the team can maintain. User context: A support console combines a ticket list, conversation panel, and reply form. Server data and draft input have clear owners. Technology or engineering concept: React. Why it fits: Use React when its components and tools fit the interactions, rendering method, and team workflow. Do not use it when: Do not put every value in state or replace clear data flow with effects. Static pages may not need it. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.

Check this request

Review the current use of React. Definition: React is a JavaScript library for component-based interfaces. Data, props, or state changes can update the screen. It is not ReAct. Release checks: Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

B
How official is this term?

Official guidance

The named platform, framework, project, or expert group has an official guide for this term.

It is official for that source. Other platforms or teams may use the term in another way.

Scope
React
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source · React · stable React Reference Scope: React Role here: Authority within stated scope Source covers: canonical name, definition, platform API, implementation, usage guidance

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.