- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
ID: python-best-practices/invalid-assert
Language: Python
Severity: Notice
Category: Best Practices
In Python, non-empty strings and non-empty tuples are considered True
in a boolean context. Therefore, assert "Something bad happened"
and assert (foo, bar)
will always evaluate to True
, even if foo
and bar
are False
or None
. This means that these assertions will never fail and are therefore invalid.
To avoid this, make sure that the expression after the assert
keyword is a boolean expression that can evaluate to either True
or False
. For example, instead of assert "Something bad happened"
, you could use assert foo is not None, "Something bad happened"
. This will raise an AssertionError
with the message “Something bad happened” if foo
is None
. Similarly, instead of assert (foo, bar)
, you could use assert foo == bar
to check if foo
and bar
are equal.
assert "Something bad happened"
assert (foo, bar)
assert foo == bar
assert booleanValue
assert portId.isnumeric(), "portId must be numeric"
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products