+ Use
+ Blumilk\BLT\Features\Application context
+ or add
+ Blumilk\BLT\Features\Traits\Application trait to test your application's
+ application features.
+
+ In the development and testing of Laravel applications, mocking services is quite important. By mocking + services, you can isolate and test specific parts of your application without relying on external dependencies. + This ensures your tests are reliable and focused. +
+
+ This chapter covers the Application trait in the BLT package, which provides methods to mock
+ services in your Laravel application during tests. You will learn how to mock individual services and multiple
+ services at once using this trait.
+
+ The following example demonstrates how to mock a specified service with a given mock class. This method ensures + that the specified service is replaced by the mock during the test scenario. +
+
+ In this example, the NotificationService is replaced with NotificationServiceMock.
+ This allows the test to run with the mocked version of the service.
+
+ The following example demonstrates how to mock multiple services at once using a table to specify the services + and their respective mocks. This method ensures that each specified service is replaced by the corresponding + mock during the test scenario. +
+
+ In this example, both the EmailService and PaymentService are replaced with their
+ respective mocks, EmailServiceMock and PaymentServiceMock. This allows the test to run
+ with the mocked versions of these services.
+
+ Use
+ Blumilk\BLT\Features\Authentication context
+ or add
+ Blumilk\BLT\Features\Traits\Authentication trait to test your application's
+ authentication features.
+
+ The Authentication trait provides several methods to manage and verify authentication states for
+ various objects within your Laravel application. These methods ensure that your application's authentication
+ features are functioning as expected.
+
+ This snippet authenticates a user by a specified value in a given field and logs them into the session. +
++ This snippet logs out any authenticated user from the session. +
++ This snippet authenticates a user with the specified attributes. +
++ This snippet logs out any authenticated user, ensuring no user is authenticated. +
++ This snippet authenticates a user with a specified email. +
++ This snippet asserts that no user is authenticated in the session. +
++ This snippet asserts that the authenticated user in the session has a specific value in a given field. +
++ This snippet asserts that the authenticated user's email matches the specified value. +
++ This snippet asserts that the authenticated user has a specific attribute with a given value. +
++ This snippet logs out the authenticated user and asserts that no user is authenticated. +
++ This snippet asserts that the authenticated user is redirected to a specified URL. +
++ This snippet asserts that a user with a specified email cannot access a given URL. +
++ To start using BLT you need to add it to your Behat context: +
++ Now you can start writing tests. For most of the tests you won't need to write single line of code. +
+
+ Add
+ Blumilk\BLT\Features\Traits\CodeBlocks trait to use ready complex functions from Codeblocks.
+
+ The CodeBlocks trait provides several methods to manage and verify authentication states for
+ various objects within your Laravel application. These methods ensure that your application's authentication
+ features are functioning as expected.
+
+ This snippet authenticates a user by a specified value in a given field and logs them into the session. +
++ This snippet authenticates a user by a specified value in a given field and logs them into the session. +
+
+ The config file in the BLT package contains the configuration settings for the package. You can customize these settings to suit your application's requirements.
Here's default configuration file that is being stored in config/blt.php:
+
+ The configuration allows for specifying default namespaces and types for the package. You can also define custom helpers that are extending existing ones to better fit your application's needs. +
+
+ Use
+ Blumilk\BLT\Features\Console context
+ or add
+ Blumilk\BLT\Features\Traits\Console trait to test your application's
+ console features.
+
+ The Console trait provides several methods to handle console commands within your Laravel application. These methods help ensure that your application's command-line interface is functioning as expected and can be tested effectively.
+
+ This snippet runs a specified Artisan command. It allows you to test scenarios where specific console commands need to be executed.
+
+ You can specify the command to run and capture its output and exit code.
+
+ The runCommandWithOptionsAndArguments method runs a specified Artisan command with options and arguments provided in a table. This is useful for testing scenarios where commands require additional parameters.
+
+ The seeInConsole method verifies that the console output contains a specified string. This is useful for ensuring that the command's output includes expected messages or results.
+
+ The consoleOutputIsNotEmpty method verifies that the console output is not empty. This is useful for ensuring that the command produces output.
+
+ The consoleOutputIsEmpty method verifies that the console output is empty. This is useful for ensuring that the command produces no output.
+
+ The consoleExitCodeIs method verifies that the console exit code matches the expected code. This is useful for ensuring that the command exits with the correct status.
+
+ In this package, both context classes and traits are utilized to extend the functionality and modularity of your + Behat tests. While context classes serve as the primary structure for defining test behaviors, traits allow you + to encapsulate and reuse common test logic across different contexts. +
+
+ Traits provide predefined methods that can be included in your context classes to perform specific actions. By
+ using traits, you can avoid code duplication and ensure consistency across your test scenarios. For example, the
+ HttpResponse trait includes methods for asserting the status and content of HTTP
+ responses, while the Translations trait provides methods for testing translation
+ features in your Laravel application.
+
+ To use a trait in your context class, simply include it using the use keyword. Here is an example of how to
+ include the HttpResponse trait in a context class:
+
+ By leveraging traits, you can streamline your test scenarios and ensure consistent behavior across different + contexts. This modular approach helps maintain cleaner and more efficient test code. +
+
+ Use
+ Blumilk\BLT\Features\Cookies context
+ or add
+ Blumilk\BLT\Features\Traits\Cookies trait to test your application's cookie features.
+
+The Cookies trait provides several methods to handle cookie operations within your Laravel application. These methods help ensure that your application's cookies are correctly set up and managed for testing purposes.
+
+ This snippet sets a cookie with a specified name and value. It allows you to simulate setting cookies in your application. +
+
+ The assertCookieValue method verifies that a cookie with the specified name has the expected value. This is useful for ensuring that cookies are set correctly in your application.
+
+ The deleteCookie method removes a cookie with the specified name. This is useful for testing scenarios where you need to clear cookies.
+
+ The assertCookieNotExists method verifies that a cookie with the specified name does not exist. This is useful for ensuring that cookies are properly deleted or not set.
+
+ The assertCookiesExist method verifies that multiple cookies with specified names and values are present. This is useful for checking the state of several cookies in your application.
+
+ Use
+ Blumilk\BLT\Features\Database context
+ or add
+ Blumilk\BLT\Features\Traits\Database trait to test your application's
+ database features.
+
+ The Database trait provides several methods to handle database operations within your Laravel
+ application. These methods help ensure that your application's database state is correctly set up for testing
+ purposes.
+
+ This snippet refreshes the database. It ensures that the database schema is up-to-date and empty from all + records. +
+
+ The refreshDatabaseWithSeeding method refreshes and seeds the database. This is useful for
+ scenarios where you need both a fresh schema and initial data.
+
+ The seederWasRan method runs a specified seeder class. This is useful for adding specific data sets
+ to your database as needed for your test scenarios.
+
+ Use
+ Blumilk\BLT\Features\Dispatcher context
+ or add
+ Blumilk\BLT\Features\Traits\Dispatcher trait to test your application's
+ dispatcher features.
+
+ The Dispatcher trait provides several methods to handle the dispatching of jobs and events within
+ your Laravel application. These methods ensure that your application's event and job dispatching features are
+ functioning as expected.
+
+ This snippet starts the bus fake, allowing you to simulate the dispatching of jobs within your tests. +
+
+ The fakeEvents method starts the event fake, allowing you to simulate the dispatching of events
+ within your tests.
+
+ The dispatchObject method dispatches a specified number of jobs or events with optional parameters.
+ This is useful for testing scenarios where you need to dispatch multiple instances of a job or event.
+
+ The assertDispatched method verifies that a specified number of jobs or events have been
+ dispatched. This is useful for assertions in your tests to ensure that the expected jobs or events have been
+ dispatched.
+
+ Use
+ Blumilk\BLT\Features\Eloquent context
+ or add
+ Blumilk\BLT\Features\Traits\Eloquent trait to test your application's
+ eloquent features.
+
+ The Eloquent trait provides several methods to handle Eloquent models and their relationships
+ within your Laravel application. These methods help ensure that your application's database interactions and
+ model relationships are functioning as expected.
+
+ This snippet seeds a specified model into the database with optional attributes. This is useful for scenarios
+ where you need to ensure that specific models exist in the database for testing.
+
+ You can specify the model name and optional attributes to create the model.
+
+ The assertModelExistsInTheDatabase method checks that a specified model exists in the database.
+ This is useful for assertions in your tests to ensure that the expected models are present.
+
+ The thereAreModelsInTheDatabase method ensures that a specified number of instances of a model
+ exist in the database. This is useful for setting up scenarios where multiple instances of a model are required.
+
+ The theModelHasMany method verifies that a model has a "has many" relationship with another model.
+ This ensures that the relationship methods are correctly defined.
+
+ The theModelBelongsTo method verifies that a model has a "belongs to" relationship with another
+ model. This ensures that the relationship methods are correctly defined.
+
+ The theModelHasOne method verifies that a model has a "has one" relationship with another model.
+ This ensures that the relationship methods are correctly defined.
+
+ The theModelBelongsToMany method verifies that a model has a "belongs to many" relationship with
+ another model. This ensures that the relationship methods are correctly defined.
+
+ The theModelHasExpectedNumberOfRelated method verifies that a model has a specified number of
+ related models. This ensures that the relationships are correctly established with the expected number of
+ related models.
+
+ Use
+ Blumilk\BLT\Features\Environment context
+ or add
+ Blumilk\BLT\Features\Traits\Environment trait to test your application's
+ environment features.
+
+ In the development and testing of Laravel applications, the environment + configuration plays a crucial role. The environment settings determine how + your application behaves under different conditions and scenarios. By + configuring the environment appropriately, you can simulate production, + development, and testing setups to ensure your application is robust and + reliable. +
++ This chapter covers various aspects of environment configuration in Laravel, + including how to change configuration values dynamically during testing with + Behat. You will learn how to set up different environments, modify + configuration settings for specific test scenarios, and leverage these + configurations to catch potential issues early in the development cycle. + Understanding and managing environment configurations effectively will help + you create more resilient and adaptable applications. +
++ When working with Laravel applications, you might need to change + configuration values during your tests to simulate different environments or + settings. This is particularly useful in Behat testing to ensure your + application behaves correctly under various configurations. +
++ The following examples demonstrate how to modify configuration values for + your Laravel application during Behat tests. By setting different + configuration parameters, you can test specific scenarios and edge cases + more effectively. +
++ In this example, the application is configured to run in the 'local' + environment. This setting is ideal for development and testing purposes. By + ensuring that 'app.env' is set to 'local', you can simulate the behavior of + your application as it would run on a developer's machine. +
++ Adjusting the environment configuration helps in identifying issues that + might not be apparent in production but could affect development or testing + environments. +
++ Here, we enable Laravel Telescope, a debugging assistant for Laravel. + Enabling Telescope during tests can help you monitor and debug the actions + that your application performs during a Behat scenario. +
++ By enabling or disabling certain features like Telescope, you can ensure + that your application behaves correctly with different toolsets and + configurations, leading to more robust and reliable software. +
+Here are some of the most frequently asked questions about using the BLT and their answers.
+Q: What is this package?
+A: BLT, Behat + Laravel Toolbox, is a toolkit designed to facilitate the testing of Laravel applications using Behat. It provides many features and traits that simplify the integration and testing process, making it easier to write and maintain robust tests.
+Q: How do I install BLT?
+A: You can install BLT via Composer by running the command:
+composer require blumilksoftware/blt
Q: How do I configure BLT?
+A: BLT configuration can be customized in the config/blt.php file. You can set namespaces, endpoints, and other settings as per your requirements.
Q: How do I mock services in my tests?
+A: You can use the Application trait to mock services. It allows you to replace actual services with mock implementations for isolated testing.
+Q: I have a question, how can I contact you?
+A: You can contact us interns directly or write to the contact page at Blumilk.
+Emails:
+jakub.kermes@studenci.collegiumwitelona.pl
+piotr.fedak@studenci.collegiumwitelona.pl
+Website: https://www.blumilk.pl/contact
+Q: What does BLT stand for?
+A: BLT is a humorous acronym referring to the classic sandwich, Bacon, Lettuce, and Tomato. However, in our context, it represents "Behat + Laravel Toolbox," a toolkit for testing Laravel applications with Behat.
+Q: I found a bug, can I report it?
+A: Of course, please contact us or you can write an issue on GitHub.
+To report a bug, you can create an issue on our GitHub repository:
+https://github.com/blumilksoftware/blt/issues
+Alternatively, you can also contact us via email:
+jakub.kermes@studenci.collegiumwitelona.pl
+piotr.fedak@studenci.collegiumwitelona.pl
+We have a few helpers in use that, if you want, you can replace with your own to better suit your use case.
+ +If you want to use Your helper, just change namespaces in config file at config/blt.php.
Your replacement helpers should be inheriting after ours though, ensuring compatibility
+ +ArrayHelper.php
+BooleanHelper.php
+NullableHelper.php
+ClassHelper.php
+UserHelper.php
+Hooks are special methods that run at specified points in your test suite's lifecycle. They allow you to execute + code before and after certain events, providing a powerful mechanism to manage your test environment and ensure + consistency across your tests.
+ +The Blumilk\BLT\Features\Hooks\RebootAfterFeature hook is designed to ensure that the system under test is reset to a clean state after each
+ feature is executed.
+ The Blumilk\BLT\Features\Hooks\RefreshDatabaseBeforeScenario hook is designed to reset the database to a known state before each scenario
+ is executed. This ensures that each test scenario runs with a fresh and consistent database, which is crucial
+ for maintaining the integrity and reliability of your test results.
+
To use hooks simply include them in your feature context
+ +
+ Use
+ Blumilk\BLT\Features\Http context
+ or add
+ Blumilk\BLT\Features\Traits\Http trait to test your application's
+ http features.
+
Blumilk\BLT\Features\Traits\HttpRequest
+ Blumilk\BLT\Features\Traits\HttpResponse
+ to include only one of them.
+
+ The HttpRequest trait provides several methods to handle HTTP requests within your Laravel
+ application. These methods help ensure that your application's request handling and response mechanisms are
+ functioning as expected.
+
+ This snippet creates a new HTTP request to the specified URL using the specified method. It allows you to
+ simulate different types of requests to test your application's endpoints.
+
+ You can specify the request method (GET, POST, etc.) and the endpoint URL.
+
+ The requestBodyContainsKeyValuePair method sets a key-value pair in the request body. This is
+ useful for testing scenarios where the request body needs specific data.
+
+ The requestBodyContains method sets multiple key-value pairs in the request body using a table.
+ This is useful for testing scenarios where the request body needs multiple specific data points.
+
+ The requestHeadersContainsKeyValuePair method sets a key-value pair in the request headers. This is
+ useful for testing scenarios where specific headers need to be included in the request.
+
+ The requestHeadersContains method sets multiple key-value pairs in the request headers using a
+ table. This is useful for testing scenarios where multiple specific headers need to be included in the request.
+
+ The thereAreValuesInFormParams method sets multiple key-value pairs in the form parameters of the
+ request using a table. This is useful for testing form submissions with specific data.
+
+ The requestQueryParamsContains method sets multiple key-value pairs in the query parameters of the
+ request using a table. This is useful for testing URL query parameters with specific data.
+
+ The requestCookiesContains method sets multiple key-value pairs in the cookies of the request using
+ a table. This is useful for testing scenarios where specific cookies need to be included in the request.
+
+ The requestServerParamsContains method sets multiple key-value pairs in the server parameters of
+ the request using a table. This is useful for testing scenarios where specific server parameters need to be
+ included in the request.
+
+ The requestHasBearerToken method sets the Authorization header to a Bearer token. This is useful
+ for testing scenarios where authentication via Bearer token is required.
+
+ The requestHasAcceptLanguage method sets the Accept-Language header. This is useful for testing
+ scenarios where the request needs to specify a preferred language.
+
+ The requestHasContentType method sets the Content-Type header. This is useful for testing scenarios
+ where the request needs to specify the type of content being sent.
+
+ The requestHasUserAgent method sets the User-Agent header. This is useful for testing scenarios
+ where the request needs to specify the client making the request.
+
+ The requestHasHost method sets the Host header. This is useful for testing scenarios where the
+ request needs to specify the host.
+
+ Use
+ Blumilk\BLT\Features\Traits\HttpResponse trait to manage and test HTTP responses
+ within your Laravel application. This trait provides methods to send requests and assert various aspects of the
+ HTTP responses received.
+
+ The HttpResponse trait provides several methods to handle HTTP responses within your Laravel
+ application. These methods help ensure that your application's response handling and status codes are
+ functioning as expected.
+
+ This snippet sends the prepared request and captures the response. It is useful for testing scenarios where you + need to verify the response from a specific request. +
+
+ The aResponseStatusCodeShouldBe method verifies that the response status code matches the expected
+ status. This is useful for ensuring that the correct status code is returned.
+
+ The aResponseHTMLShouldContainPhrase method verifies that the response HTML contains a specified
+ phrase. This is useful for ensuring that certain content is present in the response body.
+
+ The aResponseHTMLShouldContainCSRFToken method verifies that the response HTML contains a CSRF
+ token. This is useful for ensuring that CSRF protection is included in forms.
+
+ The aResponseShouldBeJson method verifies that the response content is in JSON format. This is
+ useful for ensuring that the response type is correct for API endpoints.
+
+ The aResponseShouldContainJson method verifies that the response JSON contains specified key-value
+ pairs. This is useful for ensuring that the response data includes expected values.
+
+ The aResponseShouldHaveCookie method verifies that the response contains a specified cookie. This
+ is useful for ensuring that cookies are set correctly in the response.
+
+ The aResponseShouldHaveHeader method verifies that the response contains a specified header. This
+ is useful for ensuring that specific headers are included in the response.
+
+ The aResponseShouldHaveHeaderEqualTo method verifies that a response header has a specific value.
+ This is useful for ensuring that headers contain the correct values.
+
+ The aResponseShouldHaveStatus method verifies that the response status is equal to desired one. This is
+ useful for ensuring that the request has desired code.
+
+ The aResponseStatusShouldBeOk method verifies that the response status is HTTP 200 OK. This is
+ useful for ensuring that the request was successful.
+
+ The aResponseStatusShouldBeCreated method verifies that the response status is HTTP 201 Created.
+ This is useful for ensuring that a resource was successfully created.
+
+ The aResponseStatusShouldBeNoContent method verifies that the response status is HTTP 204 No
+ Content. This is useful for ensuring that the request was successful but no content is returned.
+
+ The aResponseStatusShouldBeBadRequest method verifies that the response status is HTTP 400 Bad
+ Request. This is useful for ensuring that the request was invalid.
+
+ The aResponseStatusShouldBeUnauthorized method verifies that the response status is HTTP 401
+ Unauthorized. This is useful for ensuring that the request requires authentication.
+
+ The aResponseStatusShouldBeForbidden method verifies that the response status is HTTP 403
+ Forbidden. This is useful for ensuring that the request is not allowed.
+
+ The aResponse
+
+ StatusShouldBeNotFound method verifies that the response status is HTTP 404 Not Found. This is useful for
+ ensuring that the requested resource does not exist.
+
+ The aResponseStatusShouldBeConflict method verifies that the response status is HTTP 409 Conflict.
+ This is useful for ensuring that there is a conflict with the request.
+
+ The aResponseStatusShouldBeUnprocessable method verifies that the response status is HTTP 422
+ Unprocessable Entity. This is useful for ensuring that the request contains invalid data.
+
+ The aResponseStatusShouldBeTooManyRequests method verifies that the response status is HTTP 429 Too
+ Many Requests. This is useful for ensuring that the rate limit has been exceeded.
+
+ The aResponseStatusShouldBeGone method verifies that the response status is HTTP 410 Gone. This is
+ useful for ensuring that the requested resource is no longer available.
+
+ The aResponseStatusShouldBeServiceUnavailable method verifies that the response status is HTTP 503
+ Service Unavailable. This is useful for ensuring that the service is temporarily unavailable.
+
+ The aResponseStatusShouldBeFound method verifies that the response status is HTTP 302 Found. This
+ is useful for ensuring that the resource was found and the request was redirected.
+
+ The aResponseShouldBeRedirectedTo method verifies that the response is a redirect to the specified
+ URL. This is useful for ensuring that the request was redirected to the correct location.
+
+ The aResponseShouldHaveHeaderContaining method verifies that a response header contains a specified
+ value. This is useful for ensuring that headers contain expected values.
+
+ The aResponseShouldHaveNoContent method verifies that the response content is empty. This is useful
+ for ensuring that no content is returned in the response.
+
To start using a package if you don't already have Behat initialized in your project:
+Or if you want to do that manually:
+Use Composer to get the package from the Packagist repository:
+Create .env.behat file in your project root directory and set up your environment variables for Behat.
+Initialize Behat in your project:
+To learn more about Behat visit Behat documentation.
+
+ Use
+ Blumilk\BLT\Features\Middleware context
+ or add
+ Blumilk\BLT\Features\Traits\Middleware trait to test your application's
+ middleware features.
+
+ The Middleware trait provides several methods to handle middleware within your Laravel application.
+ These methods help ensure that your application's middleware is functioning as expected and can be enabled or
+ disabled for specific test scenarios.
+
+ This snippet disables a specified middleware. It allows you to test scenarios where certain middleware should be
+ bypassed.
+
+ You can specify the middleware class to disable it.
+
+ The disableMiddlewares method disables multiple middlewares specified in a table. This is useful
+ for scenarios where you need to disable several middlewares at once.
+
+ The disableThrottling method disables the throttling middleware. This is useful for testing
+ scenarios where rate limiting should be bypassed.
+
+ The disableCsrfProtection method disables the CSRF protection middleware. This is useful for
+ testing scenarios where CSRF protection should be bypassed.
+
+ The enableMiddleware method enables a specified middleware. This is useful for scenarios where you
+ need to ensure that a particular middleware is active.
+
+ The requestShouldHaveUuidInField method verifies that a specified field in the request contains a
+ valid UUID. This is useful for ensuring that UUIDs are correctly generated and included in the request.
+
+ The middlewareShouldBeAppliedToRequest method verifies that a specified middleware has been applied
+ to the request. This is useful for ensuring that the middleware is correctly modifying the request as expected.
+
+ Use
+ Blumilk\BLT\Features\Notification context
+ or add
+ Blumilk\BLT\Features\Traits\Notification trait to test your application's
+ notification features.
+
+ The Notification trait provides several methods to handle notifications within your Laravel application. These methods help ensure that your application's notification system is functioning as expected and can be tested effectively.
+
+ This snippet fakes notifications, allowing you to test scenarios where notifications are sent without actually sending them. It is useful for capturing and asserting notifications during tests. +
+
+ The sendNotification method sends a specified notification to an object identified by a value in a specified field. This is useful for testing scenarios where notifications need to be sent to specific users or objects.
+
+ The assertNotificationSent method verifies that a specified notification was sent a certain number of times. This is useful for ensuring that notifications are sent the expected number of times.
+
+ The assertNotificationSentToUser method verifies that a specified notification was sent to an object identified by a value in a specified field. This is useful for ensuring that notifications are sent to the correct users or objects.
+
+ The assertNotificationNotSent method verifies that a specified notification was not sent to an object identified by a value in a specified field. This is useful for ensuring that notifications are not sent when they shouldn't be.
+
+ The assertNothingWasSent method verifies that no notifications were sent. This is useful for ensuring that no notifications are sent when they shouldn't be.
+
This package is meant to streamline testing Laravel apps with Behat. It provides ready to use code snippets and + contexts for testing Laravel applications.
+ ++ Our goal is to provide a set of tools that will help you write tests faster and more efficiently. We want to + make sure that you can focus on writing tests that matter, rather than spending time on boilerplate code. + We would love to make it so no other code is needed for testing, but we are not there yet. We are constantly + working on improving the package and adding new features. +
+ + + + +And for additional packages:
+
+ Use
+ Blumilk\BLT\Features\Session context
+ or add
+ Blumilk\BLT\Features\Traits\Session trait to test your application's
+ session features.
+
+ The Session trait provides several methods to handle session data within your Laravel application.
+ These methods help ensure that your application's session management is functioning as expected.
+
+ This snippet verifies that the session contains the specified errors. It checks if the session flash data has + the expected error messages. +
+
+ The aSessionFlashesNoErrors method verifies that the session does not contain any errors. This is
+ useful for ensuring that the session is clear of errors.
+
+ The theSessionHasTheFollowingData method sets multiple key-value pairs in the session. This is
+ useful for populating the session with specific data for testing scenarios.
+
+ The theSessionShouldHaveTheFollowingData method verifies that the session contains the specified
+ key-value pairs. This is useful for asserting that the session has the expected data.
+
+ The theSessionIsRevoked method invalidates the session. This is useful for scenarios where the
+ session needs to be cleared or reset.
+
+ The theSessionHasNoData method clears all data from the session. This is useful for ensuring that
+ the session starts with no data.
+
+ The theSessionFlashesTheFollowingData method sets multiple key-value pairs in the session as flash
+ data. This is useful for testing scenarios where session flash data needs to be set.
+
+ The theSessionShouldFlashTheFollowingData method verifies that the session contains the specified
+ flash data. This is useful for asserting that the session flash data has the expected values.
+
+ The theSessionShouldHaveKey method verifies that the session contains a specified key. This is
+ useful for asserting the presence of specific session keys.
+
+ The theSessionShouldNotHaveKey method verifies that the session does not contain a specified key.
+ This is useful for asserting the absence of specific session keys.
+
+ The theSessionShouldHaveKeyWithValue method verifies that a session key contains a specified value.
+ This is useful for asserting that session keys have the expected values.
+
+ The theSessionForgetsKey method removes a specified key from the session. This is useful for
+ scenarios where specific session keys need to be cleared.
+
+ Use
+ Blumilk\BLT\Features\SpatiePermission context
+
or add
+ Blumilk\BLT\Features\Traits\SpatiePermission trait to test your application's
+ roles and permissions.
+
+ The SpatiePermission trait provides several methods to check and manipulate roles and permissions
+ for various objects within your Laravel application. These methods ensure that your application's security
+ features are functioning as expected.
+
+ This snippet checks if a given object can have roles by verifying that the object uses the Spatie\Permission\Traits\HasRoles
+ trait. This is useful for ensuring that your objects are correctly configured to handle roles.
+
+ You can insert any model name here instead of user.
+
+ The assignRoleTo method assigns a specified role to an object identified by a value in a specified
+ field. This helps in setting up your test scenarios where specific roles need to be assigned to users or other
+ objects.
+
+ The givePermissionTo method assigns a specified permission to an object. This is essential for
+ setting up scenarios where certain permissions need to be granted dynamically.
+
+ The assertHasRole method checks if an object has a specified role. This is useful for assertions in
+ your tests to verify that roles are correctly assigned.
+
+ The assertHasPermission method checks if an object has a specified permission. This helps ensure
+ that your permission settings are correctly applied and verified during testing.
+
+ The assertHas method allows for a table of key-value pairs to be checked against an object. This is
+ particularly useful for verifying multiple roles and permissions in a single test scenario.
+
+ The revokePermissionTo method revokes a specified permission from an object. This is useful for
+ testing scenarios where permissions need to be dynamically removed.
+
+ The revokeRoleTo method removes a specified role from an object. This is particularly useful for
+ scenarios where you need to test the behavior of your application when roles are removed.
+
+ Use
+ Blumilk\BLT\Features\Testing context
+ or add
+ Blumilk\BLT\Features\Traits\Testing trait to test your application's
+ testing features.
+
+ The Testing trait provides a mechanism to call PHPUnit assertions dynamically within your test scenarios. This trait helps ensure that your test assertions are concise and easy to use.
+
+ This function demonstrates the dynamic method call for PHPUnit assertions. It allows you to call any PHPUnit assertion method using the trait. +
+
+ The __call method intercepts calls to undefined methods and dynamically calls the corresponding PHPUnit assertion method. This makes it easier to write and maintain test assertions.
+
+ Use
+ Blumilk\BLT\Features\Translations context
+ or add
+ Blumilk\BLT\Features\Traits\Translations trait to test your application's
+ translations features.
+
+ The Translations trait provides several methods to handle translations within your Laravel
+ application. These methods help ensure that your application's localization and translation features are
+ functioning as expected.
+
+ This snippet sets the application's locale to the specified language. It allows you to test scenarios where
+ different locales need to be set.
+
+ You can specify the locale code (e.g., 'en', 'fr', 'es') to change the application's language.
+
+ The askToTranslate method sets the input phrase to be translated. This is useful for scenarios
+ where you need to test the translation of specific phrases.
+
+ The assertTranslationMatches method verifies that the translations match the expected phrases. This
+ is useful for ensuring that the translations are correct for different locales.
+
+ The assertEndpointTranslationMatches method verifies that the response from an endpoint matches the
+ expected translations for different locales. This is useful for ensuring that API responses are correctly
+ translated.
+ You'll need to run
+
+ Use
+ Blumilk\BLT\Features\View context
+ or add
+ Blumilk\BLT\Features\Traits\View trait to test your application's
+ view features.
+
+ The View trait provides several methods to handle views within your Laravel application. These methods help ensure that your application's views are rendered correctly and contain the expected data.
+
+ This snippet sets the view that the user is looking at, with optional parameters. It allows you to test scenarios where specific views need to be rendered with given parameters.
+
+ You can specify the view name and optionally pass a table of parameters to the view.
+
+ The theViewContains method verifies that the view contains the specified data. This is useful for ensuring that the view has the expected data passed to it.
+
+ The viewResponseContains method verifies that the response view contains the specified data.
+ This is useful for ensuring that the response includes the expected view data.
+
Requires running
+before in your test scenario.
+${gherkinText}${phpText}${content}