@backstage/backend-test-utils
Advanced tools
Test helpers library for Backstage backends.
Add the library as a devDependency to your backend package:
# From your Backstage root directory, go to your backend package, or to a backend plugin
cd plugins/my-plugin-backend
yarn add --dev @backstage/backend-test-utils
BACKSTAGE_TEST_DISABLE_DOCKER
1 disables Docker for testsCI
1 enables long-running tests, including the ones utilizing DockerBACKSTAGE_TEST_DOCKER_REGISTRY
mycompany.docker.io/mirrorDOCKER_AUTH_CONFIG)Connection strings for different databases that are used for testing. The value of the string should point to the running instance of the database.
BACKSTAGE_TEST_DATABASE_POSTGRES13_CONNECTION_STRINGBACKSTAGE_TEST_DATABASE_POSTGRES12_CONNECTION_STRINGBACKSTAGE_TEST_DATABASE_POSTGRES11_CONNECTION_STRINGBACKSTAGE_TEST_DATABASE_POSTGRES9_CONNECTION_STRINGBACKSTAGE_TEST_DATABASE_MYSQL8_CONNECTION_STRINGFAQs
Test helpers library for Backstage backends
The npm package @backstage/backend-test-utils receives a total of 37,417 weekly downloads. As such, @backstage/backend-test-utils popularity was classified as popular.
We found that @backstage/backend-test-utils demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
The Socket Research Team investigates a malicious npm package that appears to be an Advcash integration but triggers a reverse shell during payment success, targeting servers handling transactions.
Security Fundamentals
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.
Security News
At VulnCon 2025, NIST scrapped its NVD consortium plans, admitted it can't keep up with CVEs, and outlined automation efforts amid a mounting backlog.