zoom_in Click to enlarge

Introduce Assertion

▲ ▼

description Introduce Assertion Overview

Introduce Assertion is an automated refactoring tool available in JetBrains integrated development environments (IDEs) such as IntelliJ IDEA and PyCharm. It analyzes source code to identify invariants and automatically generates assert statements that check for mandatory conditions during runtime execution. This feature is designed for software developers who want to improve code reliability and debuggability by explicitly validating assumptions without writing boilerplate checks manually.

help Introduce Assertion FAQ

What does the Introduce Assertion refactoring do?

It turns an assumption about a value or condition into an explicit assertion in the code. For example, a comment saying that a discount rate must not be negative can become an assertion such as assert(discountRate >= 0). [Refactoring pattern](https://refactoring.guru/introduce-assertion)

Is Introduce Assertion a standard built-in command in IntelliJ IDEA?

JetBrains' documented refactoring list includes actions such as Extract Method, Introduce Variable, Rename, and Change Signature, but it does not list a built-in command named Introduce Assertion. Treat this catalog entry as a refactoring pattern or plugin-assisted action unless the installed IDE exposes that exact command. [JetBrains refactoring documentation](https://www.jetbrains.com/help/idea/refactoring-source-code.html)

How is an introduced assertion different from a test assertion?

A code assertion checks an invariant while the program is running, such as requiring an object to be non-null at a particular point. A test assertion checks whether a test result matches an expected value, so the two serve different purposes even though both can report failure.

Can Introduce Assertion replace validation for user input?

No. In Java, language assertions are disabled by default unless the runtime is started with -ea, and a failed enabled assertion throws AssertionError. External input should be checked with normal validation and error handling instead.