Libraries tagged by scenario
paulgibbs/behat-wordpress-extension
190192 Downloads
WordHat is a Behat extension for WordPress. It provides WordPress-specific functionality for common testing scenarios specific to WordPress sites.
stateforge/scenario-core
8140 Downloads
Core library for declarative, attribute-driven scenario orchestration for reproducible test data states in PHP.
tonicforhealth/behat-parallel-scenario
357239 Downloads
Behat parallel scenario
gorghoa/scenariostate-behat-extension
607673 Downloads
Scenario shared state extension for Behat
leanphp/behat-code-coverage
361918 Downloads
Generate Code Coverage reports for Behat tests
friends-of-behat/exclude-specifications-extension
113412 Downloads
Allows to exclude features or scenarios in Behat tests.
remp/crm-scenarios-module
49954 Downloads
CRM Scenarios Module
greg-1-anderson/composer-test-scenarios
3736 Downloads
Useful scripts for testing multiple sets of Composer dependencies.
g-1-a/composer-test-scenarios
4040 Downloads
Useful scripts for testing multiple sets of Composer dependencies.
short-edition/behat-code-coverage
5943 Downloads
Generate Code Coverage reports for Behat tests
vitexsoftware/rbczpremiumapi
418 Downloads
##### API Overview - Accounts list and balance - Transaction overview (also for saving accounts) - Payments import - Statement list and download - FX rates ##### Authentication Before making a call to Premium API, you need to register your app at our _Developer portal_. This is where you get the **ClientID** that your application must send in the request as `X-IBM-Client-Id`. This is the key that grants your app access to the API. However, this may not be enough. Your application needs to use mTLS to call most operations here. Thus, you not only need _https_ but also a client certificate issued by us. The exception is two operations for FX rates that are accessible also without a client certificate. Each bank client/user can issue several certificates. Each certificate can permit different sets of operations (http methods) on different bank accounts. All this must be configured in Internet Banking first by each bank client/user (bank clients need to look under _Settings_ and do not forget to download the certificate at the last step). The certificate is downloaded in **PKCS#12** format as **\*.p12** file and protected by a password chosen by the bank client/user. Yes, your app needs the password as well to get use of the **\*p12** file for establishing mTLS connection to the bank. Client certificates issued in Internet Banking for bank clients/users have limited validity (e.g. **5 years**). However, **each year** certificates are automatically blocked and bank client/user must unblock them in Internet Banking. It is possible to do it in advance and prolong the time before the certificate is blocked. Your app should be prepared for these scenarios and it should communicate such cases to your user in advance to provide seamless service and high user-experience of your app. ##### Rate Limiting The number of requests in each API operation is limited to 10 per client per sliding second and 5000 per client per sliding day. The exception is the 'Download Statement' operation with the limits lowered to 5 per client per sliding second and 1500 per client per sliding day. This is because it transports potentially sizeable binary files. The consumer must be able to handle HTTP status 429 in case of exceeding these limits. Response headers `X-RateLimit-Limit-Second` and `X-RateLimit-Limit-Day` show the actual limits configured for the specific operation. Response headers `X-RateLimit-Remaining-Second` and `X-RateLimit-Remaining-Day` are returned to help prevent the limits from being exceeded. ##### Notes Be aware, that in certain error situations, API can return specific error structures along with 5xx status code, which is not explicitely defined below. ##### Quick Start Client Feel free to download a simple Java client that gives you quick access to our API.
spryker/cypress-tests
17288 Downloads
This repository is dedicated to housing an extensive collection of UI end-to-end tests, meticulously crafted using Cypress for Spryker applications. These tests are designed to thoroughly evaluate the user interface, ensuring that all interactions and visual elements function as intended in real-world scenarios. By leveraging Cypress's advanced browser automation capabilities, this suite provides an efficient and effective means of validating the user experience, confirming the seamless operation and aesthetic integrity of Spryker's front-end components. Our commitment to rigorous UI testing helps maintain the high standard of quality and reliability that Spryker users expect.
sourcebroker/webp
16981 Downloads
Webp converter scenarios
pudongping/hyperf-wise-locksmith
7877 Downloads
A mutex library provider for the Hyperf framework, designed to enable serialized execution of PHP code in high-concurrency scenarios.
padosoft/laravel-super-cache-invalidate
9084 Downloads
A powerful package that provides an efficient and scalable cache invalidation system for Laravel applications. It is designed to handle high-throughput cache invalidation scenarios, such as those found in e-commerce platforms, by implementing advanced techniques like event queuing, coalescing, debouncing, sharding, and partitioning.