Download the PHP package phphd/api-testing without Composer
On this page you can find all versions of the php package phphd/api-testing. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package api-testing
PhdApiTestingBundle
🧰 Provides lightweight jwt authorization utilities for Api Testing in Symfony applications. In essence, this package integrates Lexik JWT Authentication Bundle into your Api Test Cases.
Quick Start
Installation 📥
-
Install via composer
- Enable the bundle in the
bundles.php
Configuration ⚒️
Create phd_api_testing.yaml configuration file under config/packages/test directory. It's necessary to specify
service id of application user provider here. If you
have only one authenticated user entity (hence, one provider), use current default configuration.
Usage 🚀
In your Api Test class use JwtLoginTrait and login method to handle authentication:
In this example, login is used to generate jwt token for username user so that api request will be sent on his
behalf.
Advanced Configuration ⚙️
Multiple Authenticators
It is possible to use multiple authenticators for your specific needs. For instance if you have admin panel alongside your main authenticated application, you may want to use the dedicated authenticator.
In essence, if you're utilizing security.user_providers, additional configuration is typically unnecessary,
since security.user_providers acts as a chain user provider, meaning that first found user from any subordinate
providers will be used.
Nonetheless, in case of conflicting usernames or any other specific reason, you may register an additional authenticator in the same configuration file by different name:
In this config, api_admin_user_provider is the name of user provider from security.yaml and admin - just an alias
for our usage in tests.
Having registered authenticator, we may use its alias as a second parameter of login method:
