Download the PHP package amirrezam75/laravel-assertions without Composer
On this page you can find all versions of the php package amirrezam75/laravel-assertions. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download amirrezam75/laravel-assertions
More information about amirrezam75/laravel-assertions
Files in amirrezam75/laravel-assertions
Package laravel-assertions
Short Description A set of helpful assertions when testing Laravel applications.
License MIT
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 laravel-assertions
Installation
composer require amirrezam75/laravel-assertions
assertRedirection
I was working on a project and in order to test oauth2 redirection, I ended up with something like this:
Before
I think it would be cleaner and much more readable if have something similar to AssertableJson class.
After
We can assert other parts of URI using these methods:
- whereFragment($value)
- whereHost($value)
- wherePass($value)
- wherePath($value)
- wherePort($value)
- whereScheme($value)
- whereUser($value)
IMO It's not practical but we can only check for existence of component using these methods:
- hasFragment()
- hasHost()
- hasPass()
- hasPath()
- hasPort()
- hasScheme()
- hasUser()
etc()
Like AssertableJson it uses Interaction trait, this will automatically fail your test when you haven't interacted with at least one of the props in a URI query string. Hence the sequence is fixed in other parts of URI; they don't need to be affected by interacted method and can be asserted using assertRedirectContains method.
