PHPackages spryker/robotframework-suite-tests - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Testing & Quality](/categories/testing) 4. / 5. spryker/robotframework-suite-tests ActiveLibrary[Testing & Quality](/categories/testing) spryker/robotframework-suite-tests ================================== Automated tests for the Robot Framework 1293.0k↓30.2%6[4 PRs](https://github.com/spryker/robotframework-suite-tests/pulls)9RobotFrameworkCI passing Since Jul 20Pushed 2mo ago14 watchersCompare [ Source](https://github.com/spryker/robotframework-suite-tests)[ Packagist](https://packagist.org/packages/spryker/robotframework-suite-tests)[ RSS](/packages/spryker-robotframework-suite-tests/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependenciesVersions (37)Used By (9) Description ----------- [](#description) This repository contains sets of API and UI tests, built on the Robot Framework. API tests use the RequestsLibrary in conjunction with Robot Framework, while UI tests rely on the Browser library (powered by Playwright). Installation ------------ [](#installation) ### Prerequisites [](#prerequisites) [Robot Framework](https://robotframework.org/) is implemented using [Python](https://www.python.org/), and a precondition to install it is having Python or its alternative implementation [PyPy](https://www.pypy.org/) installed. Another recommended precondition is having the [pip](https://pip.pypa.io/en/stable/) package manager available. Robot Framework requires Python 3.6 or newer. 1. Install [Robot Framework](https://github.com/robotframework/robotframework/blob/master/INSTALL.rst) ``` ./install.sh ``` ### Installation for UI tests [](#installation-for-ui-tests) ##### For UI testing installation requires Robot Framework, [RequestsLibrary](https://github.com/MarketSquare/robotframework-requests), [DatabaseLibrary](https://github.com/franz-see/Robotframework-Database-Library) and [Browser library](https://robotframework-browser.org/) powered by Playwright. [](#for-ui-testing-installation-requires-robot-framework-requestslibrary-databaselibrary-and-browser-library-powered-by-playwright) If you installed everything from the [prerequisites](#Prerequisites), all you need to install is Node.js and the Browser binaries. 1. Install [Node.js®](https://nodejs.org/en/download) 2. Install [Browser library](https://robotframework-browser.org/#installation) 3. Initialize the Browser library ``` rfbrowser init chromium ``` ### Installation for API tests [](#installation-for-api-tests) ##### For API testing installation requires Robot Framework, [RequestsLibrary](https://github.com/MarketSquare/robotframework-requests), [JSONLibrary](https://github.com/robotframework-thailand/robotframework-jsonlibrary) and [DatabaseLibrary](https://github.com/franz-see/Robotframework-Database-Library). [](#for-api-testing-installation-requires-robot-framework-requestslibrary-jsonlibrary-and-databaselibrary) You do not need to install anything additionally to be able to run API tests, if you already installed everything from the [prerequisites](#Prerequisites). How to run tests ---------------- [](#how-to-run-tests) Robot Framework test cases are executed from the command line, and the end result is, by default, an output file in XML format and an HTML report and log. After the execution, output files can be combined and otherwise post-processed with the Rebot tool. > **Note**: If you prefer to run test using the default configuration of your local environment, you can navigate to the **[Helper](#Helper)** section > **Note** 2: If you use locally installed internal Spryker `suite` project (with the help of [DockerSDK](https://github.com/spryker/docker-sdk)), you can use automated runner that will take care of installing dependencies and running tests with proper parameters. > > ``` > ./bin/run-robot-suite-tests.sh api > ./bin/run-robot-suite-tests.sh ui > ``` > **Note** 3: Narrow down the test to be executed with the path option. > > ``` > ./bin/run-robot-suite-tests.sh api tests/api/b2b > ./bin/run-robot-suite-tests.sh api tests/api/b2b/glue/access_token_endpoints > ``` Synopsis ``` robot [options] data python -m robot [options] data python path/to/robot/ [options] data ``` Execution is normally started using the `robot` command created as part of installation. Alternatively it is possible to execute the installed robot module using the selected Python interpreter. This is especially convenient if Robot Framework has been installed under multiple Python versions. Finally, if you know where the installed robot directory exists, it can be executed using Python as well. Regardless of execution approach, the path (or paths) to the test data to be executed is given as an argument after the command. Additionally, different [command line options](https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#using-command-line-options) can be used to alter the test execution or generated outputs in many ways. **Basic usage example:**`robot -v env:{ENVIRONMENT} {PATH}` ### Supported CLI Parameters [](#supported-cli-parameters) ParameterCommentExampleRequired`-v env:{env}`Environment variable. Demo data, locators and hosts in tests depend on this variable value. **It's crucial to pass the env variable as tests fully depend on it.** Supported parameters are: `api_b2b`, `api_b2c`, `api_mp_b2b`, `api_mp_b2c`, `api_suite`, `ui_b2b`, `ui_b2c`, `ui_mp_b2b`, `ui_mp_b2c`, `ui_suite``robot -v env:api_b2b -s '*'.tests.api.b2b.glue .` / `robot -v env:ui_b2c tests/ui/e2e/b2c.robot`**yes**`-v db_engine:{engine}`Depending on your system setup, you can run tests against MySQL or PostgreSQL. Possible values: `mysql` or `postgresql`. **Default:** `mysql``robot -v env:api_b2b -v db_engine:postgresql -s '*'.tests.api.b2b.glue .`optional`-v db_host:{host}`Depending on your system setup, you can specify db\_host if it differs from the default one. **Default:** `127.0.0.1``robot -v env:api_b2b -v db_host:127.2.3.4 -s '*'.tests.api.b2b.glue .`optional`-v db_port:{port}`Depending on your system setup, you can specify db\_port if it differs from the default one. **Default MariaDB:** `3306` / **Default PostgreSQL:** `5432``robot -v env:api_b2b -v db_port:3390 -s '*'.tests.api.b2b.glue .`optional`-v db_user:{user}`Depending on your system setup, you can specify db\_user if it differs from the default one. **Default:** `spryker``robot -v env:api_b2b -v db_user:fake_user -s '*'.tests.api.b2b.glue .`optional`-v db_password:{pwd}`Depending on your system setup, you can specify db\_password if it differs from the default one. **Default:** `secret``robot -v env:api_b2b -v db_password:fake_password -s '*'.tests.api.b2b.glue .`optional`-v db_name:{name}`Depending on your system setup, you can specify db\_name if it differs from the default one. **Default:** `eu-docker``robot -v env:api_b2b -v db_name:fake_name -s '*'.tests.api.b2b.glue .`optional`-d {PATH}`Path to the folder to store the run report. Like `results``robot -v env:api_b2b -d results tests/.../example.robot`optional`-s test_suite_name`Test suite name is the name of any subfolder in tests folder (without path) or filename (without extension). If specified, tests from that folder/file folder will be executed.`robot -v env:api_b2b -s '*'.tests.api.b2b.glue .` / `robot -v env:api_mp_b2b -s '*'.tests.api.mp_b2b.glue .`optional`-v yves_env:{URL}`You can specify Yves URL if you would like to run your tests on cloud environment`robot -v env:ui_b2c -v yves_env:http://example.com tests/ui/e2e/b2c.robot`optional`-v yves_at_env:{URL}`You can specify Yves AT store URL if you would like to run your tests on cloud environment`robot -v env:ui_b2c -v yves_env:http://example.com -v yves_at_env:http://at.example.com tests/ui/e2e/b2c.robot`optional`-v zed_env:{URL}`You can specify Zed URL if you would like to run your tests on cloud environment`robot -v env:ui_b2c -v yves_env:http://example.com -v zed_env:http://bo.example.com tests/ui/e2e/b2c.robot`optional`-v glue_env:{URL}`You can specify Glue URL if you would like to run your tests on cloud environment`robot -v env:api_b2c -v glue_env:http://glue.example.com -s '*'.tests.api.b2c.glue .`optional`-v bapi_env:{URL}`You can specify BAPI URL if you would like to run your tests on cloud environment`robot -v env:api_b2c -v glue_env:http://glue.example.com -v bapi_env:http://bapi.example.com -s '*'.tests.api.b2c.bapi .`optional`-v sapi_env:{URL}`You can specify SAPI URL if you would like to run your tests on cloud environment`robot -v env:api_b2c -v glue_env:http://glue.example.com -v sapi_env:http://sapi.example.com -s '*'.tests.api.b2c.sapi .`optional`-v mp_env:{URL}`You can specify Merchant Portal URL if you would like to run your tests on cloud environment`robot -v env:ui_mp_b2c -v yves_env:http://example.com -v zed_env:http://bo.example.com -v mp_env:http://mp.example.com tests/ui/e2e/mp_b2c.robot`optional`-v browser:{browser}`Defines in which browser run tests. Possible values: `chromium`,`firefox`, `webkit`. **Default:** `chromium``robot -v env:ui_mp_b2c -v browser:firefox tests/ui/e2e/mp_b2c.robot`For UI tests only. optional`-v headless:{headless}`Defines if the browser should be launched in the headless mode. Possible values: `true`,`false`. **Default:** `true``robot -v env:ui_mp_b2c -v headless:false tests/ui/e2e/mp_b2c.robot`For UI tests only. optional`-v browser_timeout:{timeout}`Default time for Implicit wait in UI tests. **Default:** `60s``robot -v env:ui_mp_b2c -v browser_timeout:30s tests/ui/e2e/mp_b2c.robot`For UI tests only. optional`-v api_timeout:${timeout}`Default time for Implicit wait of the response in API tests. **Default:** `60s``robot -v env:api_b2c -v api_timeout:30s -s '*'.tests.api.b2c.glue .`For API tests only. optional`-v verify_ssl:bool`Enables/Disables SSL verification in API and UI tests. **Default:** `false``robot -v env:api_b2c -v verify_ssl:true -s '*'.tests.api.b2c.glue .`optional`-v docker:bool`Enables/Disables Docker compatibility. **Default:** `false``robot -v env:api_b2c -v docker:True -s '*'.tests.api.b2c.glue .`**yes for running tests via docker/sdk**`-v ignore_console:bool`Enables/Disables docker/sdk commands during test execution, such as 'trigger oms' or 'trigger p&s'. **Default:** `true`, meaning console commands are **not** executed`robot -v env:ui_b2c -v ignore_console:False tests/ui/e2e/mp_b2c.robot`optional. If `-v docker:true` - this parameter is set to `False` by default, meaning docker/sdk commands are executable`-v project_location:${absolute_path}`Absolute project/application **root** folder location for docker/sdk cli commands`robot -v env:ui_b2c -v ignore_console:True -v project_location:/Users/your_user/projects/b2c tests/ui/e2e/mp_b2c.robot`optional. If `-v docker:true` - this parameter is ignored`{PATH}`Path to the **file** to execute`robot -v env:api_b2b tests/api/b2b/glue/cart_endpoints/carts/positive.robot` / `robot -v env:ui_b2c tests/ui/e2e/b2c.robot` **where** `tests/ui/e2e/b2c.robot` and `tests/api/b2b/glue/cart_endpoints/carts/positive.robot` is a `{PATH}`**yes for UI tests**`-v dms:bool`Enables/Disables Dynamic Multistore tests. Indicating that all tests are run on the regular shop by default. If you need to run all tests on the dynamic multistore, you should set True value. **Default:** `false``robot -v env:ui_b2c -v dms:true tests/ui/e2e/b2c.robot`optional. If -v dms:false - this parameter is ignored`-v is_ssp:bool`Enables/Disables SSP mode. If you need to run all tests in SSP mode, you should set True value. **Default:** `false``robot -v env:ui_b2c -v dms:true tests/ui/e2e/b2c.robot`optional. If -v dms:false - this parameter is ignored#### CLI Examples [](#cli-examples) - Execute all tests (positive and negative) in api/suite folder (all glue, bapi and sapi API tests that exist) via docker/sdk. ``` docker/sdk exec robot-framework robot -v docker:True -v env:api_suite -d results -s '*'.tests.api.suite . ``` - Execute all tests in api/b2b folder (all glue, bapi and sapi API tests that exist). ``` robot -v env:api_b2b -d results -s '*'.tests.api.b2b . ``` - Execute all tests in a specific folder (all API tests that exist inside the folder and sub-folders). ``` robot -v env:api_b2b -d results -s '*'.tests.api.b2b.glue.access_token_endpoints . ``` - Execute only positive tests in api folder (all positive API tests that exist, from all folders). ``` robot -v env:api_suite -d results -s positive . ``` - Execute all positive and negative API tests in tests/api/suite/glue/abstract\_product\_endpoints folder. Subfolders (other endpoints) will be executed as well. ``` robot -v env:api_suite -d results -s '*'.tests.api.suite.glue.abstract_product_endpoints . ``` - Execute all positive and negative API tests in tests/api/suite/glue/abstract\_product\_endpoints/abstract\_products ``` robot -v env:api_suite -d results -s '*'.tests.api.suite.glue.abstract_product_endpoints.abstract_products . ``` - Execute all E2E UI tests for MP-B2B on specific cloud environment. ``` robot -v env:ui_mp_b2b -v yves_env:http://yves.example.com -v zed_env:http://zed.example.com -v mp_env:http://mp.example.com -d results tests/ui/e2e/mp_b2b.robot ``` - Execute all API tests for B2B on specific cloud environment with custom DB configuration. ``` robot -v env:api_b2b -v db_engine:postgresql -v db_host:124.1.2.3 -v db_port:5336 -v db_user:fake_user -v db_password:fake_password -v db_name:fake_name -s '*'.tests.api.b2b.glue . ``` --- ### [Supported Browsers in UI tests](https://marketsquare.github.io/robotframework-browser/Browser.html#SupportedBrowsers) [](#supported-browsers-in-ui-tests) Since [Playwright](https://github.com/microsoft/playwright) comes with a pack of builtin binaries for all browsers, no additional drivers e.g. geckodriver are needed. All these browsers that cover more than 85% of the world wide used browsers, can be tested on Windows, Linux and MacOS. Theres is not need for dedicated machines anymore. BrowserBrowser with this enginechromiumGoogle Chrome, Microsoft Edge (since 2020), OperafirefoxMozilla FirefoxwebkitApple Safari, Mail, AppStore on MacOS and iOS--- ### Helper [](#helper) For local testing, all tests are commonly executed against default hosts. To avoid typos in execution commands, you can use the [Makefile](https://makefiletutorial.com/) helper to quickly start your runs. **Note:** no installation is required on macOS and Linux systems. The `make` command is included in most Linux distributions by default. To run Makefile on Windows, you need to install a program called "make". ##### Supported Helper commands [](#supported-helper-commands) CommandCommentOptional arguments`make test_api_b2b`Run all API tests for B2B on default local environment`glue_env=` / `bapi_env=` / `sapi_env=` / `docker=` / `ignore_console=` / `project_location=``make test_api_b2c`Run all API tests for B2C on default local environment`glue_env=` / `bapi_env=` / `sapi_env=` / `docker=` / `ignore_console=` / `project_location=``make test_api_mp_b2b`Run all API tests for MP-B2B on default local environment`glue_env=` / `bapi_env=` / `sapi_env=` / `docker=` / `ignore_console=` / `project_location=``make test_api_mp_b2c`Run all API tests for MP-B2C on default local environment`glue_env=` / `bapi_env=` / `sapi_env=` / `docker=` / `ignore_console=` / `project_location=``make test_api_suite`Run all API tests for Suite on default local environment`glue_env=` / `bapi_env=` / `sapi_env=` / `docker=` / `ignore_console=` / `project_location=``make test_ui_suite`Run all UI tests for Suite on default local environment`glue_env=` / `bapi_env=` / `yves_env=` / `yves_at_env=` / `zed_env=` / `mp_env=`/ `docker=` / `ignore_console=` / `project_location=``make test_ui_b2b`Run all UI tests for B2B on default local environment`glue_env=` / `bapi_env=` / `yves_env=` / `yves_at_env=` / `zed_env=` / `mp_env=` / `docker=` / `ignore_console=` / `project_location=``make test_ui_b2c`Run all UI tests for B2C on default local environment`glue_env=` / `bapi_env=` / `yves_env=` / `yves_at_env=` / `zed_env=` / `mp_env=` / `docker=` / `ignore_console=` / `project_location=``make test_ui_mp_b2b`Run all UI tests for MP-B2B on default local environment`glue_env=` / `bapi_env=` / `yves_env=` / `yves_at_env=` / `zed_env=` / `mp_env=` / `docker=` / `ignore_console=` / `project_location=``make test_ui_mp_b2c`Run all UI tests for MP-B2C on default local environment`glue_env=` / `bapi_env=` / `yves_env=` / `yves_at_env=` / `zed_env=` / `mp_env=` / `docker=` / `ignore_console=` / `project_location=`##### Helper Examples [](#helper-examples) - Run all API tests for B2B on local environment ``` make test_api_b2b ``` - Run all UI tests for MP-B2C on local environment with disabled docker/sdk commands ``` make test_ui_mp_b2c ignore_console=true ``` - Run all UI tests for MP-B2C on local environment with enabled docker/sdk commands and specify your application location ``` make test_ui_mp_b2c ignore_console=false project_location=/Users/your_user/projects/mp-b2b ``` - Run all API tests for B2B on cloud environment ``` make test_api_b2c glue_env=http://glue.example.com bapi_env=http://bapi.example.com sapi_env=http://sapi.example.com ``` --- [Built-in libraries](https://robotframework.org/?tab=builtin#resources) ----------------------------------------------------------------------- [](#built-in-libraries) NameDescriptionKeywords documentationBuiltinProvides a set of often needed generic keywords. Always automatically available without imports.[Documentation](https://robotframework.org/robotframework/latest/libraries/BuiltIn.html)CollectionsProvides a set of keywords for handling Python lists and dictionaries.[Documentation](https://robotframework.org/robotframework/latest/libraries/Collections.html)DateTimeLibrary for date and time conversions.[Documentation](https://robotframework.org/robotframework/latest/libraries/DateTime.html)DialogsProvides means for pausing the execution and getting input from users.[Documentation](https://robotframework.org/robotframework/latest/libraries/Dialogs.html)OperatingSystemEnables various operating system related tasks to be performed in the system where Robot Framework is running.[Documentation](https://robotframework.org/robotframework/latest/libraries/OperatingSystem.html)ProcessLibrary for running processes in the system.[Documentation](https://robotframework.org/robotframework/latest/libraries/Process.html)ScreenshotProvides keywords to capture screenshots of the desktop.[Documentation](https://robotframework.org/robotframework/latest/libraries/Screenshot.html)StringLibrary for generating, modifying and verifying strings.[Documentation](https://robotframework.org/robotframework/latest/libraries/String.html)--- ### External libraries that can be installed based on your needs [](#external-libraries-that-can-be-installed-based-on-your-needs) The full list can be found on the [official website](https://robotframework.org/?tab=libraries#resources) NameDescriptionKeywords documentationBrowserA modern web testing library powered by Playwright. Aiming for speed, reliability and visibility. **Note: Already installed**[Documentation](https://marketsquare.github.io/robotframework-browser/Browser.html)RequestsLibraryLibrary for sending and API requests and receiving the responses.[Documentation](https://marketsquare.github.io/robotframework-requests/doc/RequestsLibrary.html)JSONLibraryLibrary for parsing JSONs that come in API responses.[Documentation](https://robotframework-thailand.github.io/robotframework-jsonlibrary/JSONLibrary.html)--- Automatically re-executing failed tests --------------------------------------- [](#automatically-re-executing-failed-tests) There is often a need to re-execute a subset of tests, for example, after fixing a bug in the system under test or in the tests themselves. This can be accomplished by selecting test cases by names (--test and --suite options), tags (--include and --exclude), or by previous status (--rerunfailed or --rerunfailedsuites). Combining re-execution results with the original results using the default combining outputs approach does not work too well. The main problem is that you get separate test suites and possibly already fixed failures are also shown. In this situation it is better to use --merge (-R) option to tell Rebot to merge the results instead. In practice this means that tests from the latter test runs replace tests in the original. CommandDescription`robot -v env:ui_suite -d results tests/ui/e2e/suite.robot`first execute all tests`robot -v env:ui_suite -d results/rerun --runemptysuite --rerunfailed results/output.xml --output rerun.xml tests/ui/e2e/suite.robot`then re-execute failing`rebot -d results --merge results/output.xml results/rerun/rerun.xml`finally merge results`robot -v env:ui_suite -d results tests/ui/e2e/suite.robot; robot -v env:ui_suite -d results/rerun --runemptysuite --rerunfailed results/output.xml --output rerun.xml tests/ui/e2e/suite.robot; rebot -d results --merge results/output.xml results/rerun/rerun.xml`All in oneThe message of the merged tests contains a note that results have been replaced. The message also shows the old status and message of the test. Merged results must always have same top-level test suite. Tests and suites in merged outputs that are not found from the original output are added into the resulting output. --- Viewing and Generating Keyword Documentation -------------------------------------------- [](#viewing-and-generating-keyword-documentation) Keywords used in the tests can and should be documented. If you add any new keyword into the files inside the 'common' folder, they should have \[Documentation\] tag in them that describes what the keyword does, what parameters mean and gives an example of the usage. Documentation can be generated by these tags. For now only common\_api.robot has documentation generated. If you added new keywords, you should re-generate the documentation and commit it together with the other changes you made. To generate the documentation for api, bapi and sapi tests use this command: `libdoc resources/common/common_api.robot API_Keyword_Documentation.html` To view the documentation just open the generated html file in any browser. --- Output files ------------ [](#output-files) Several output files are created when tests are executed, and all of them are somehow related to test results. **Log** files contain details about the executed test cases in HTML format. They have a hierarchical structure showing test suite, test case and keyword details. Log files are needed nearly every time when test results are to be investigated in detail. Even though log files also have statistics, reports are better for getting an higher-level overview. The command line option `--log (-l)` determines where log files are created. Unless the special value NONE is used, log files are always created and their default name is log.html. --- Test Tagging ------------ [](#test-tagging) When adding a new test or extending the coverage of an existing test (UI or API) - add the tag for the covered feature. The tag should be named the same as the corresponding feature in the Release App. E.g. if you create a new test that touches Marketplace Agent Assist feature, you should add tags `marketplace-agent-assist` and `marketplace-merchantportal-core`. ### Health Score 43 — FairBetter than 91% of packages Maintenance58 Moderate activity, may be stable Popularity40 Moderate usage in the ecosystem Community37 Small or concentrated contributor base Maturity35 Early-stage or recently created project Bus Factor2 2 contributors hold 50%+ of commits How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://avatars.githubusercontent.com/u/10738957?v=4)[Spryker Bot](/maintainers/spryker-bot)[@spryker-bot](https://github.com/spryker-bot) --- Top Contributors [![AntonShopin](https://avatars.githubusercontent.com/u/29924635?v=4)](https://github.com/AntonShopin "AntonShopin (1128 commits)")[![Nataliia-Popkova](https://avatars.githubusercontent.com/u/49430519?v=4)](https://github.com/Nataliia-Popkova "Nataliia-Popkova (1086 commits)")[![OKrivtsova](https://avatars.githubusercontent.com/u/50324133?v=4)](https://github.com/OKrivtsova "OKrivtsova (161 commits)")[![gorav-sharma-metacube](https://avatars.githubusercontent.com/u/102520274?v=4)](https://github.com/gorav-sharma-metacube "gorav-sharma-metacube (155 commits)")[![vadym-uskov](https://avatars.githubusercontent.com/u/97114769?v=4)](https://github.com/vadym-uskov "vadym-uskov (148 commits)")[![m-alama](https://avatars.githubusercontent.com/u/97005260?v=4)](https://github.com/m-alama "m-alama (136 commits)")[![himanshu-pal-metacube](https://avatars.githubusercontent.com/u/99314039?v=4)](https://github.com/himanshu-pal-metacube "himanshu-pal-metacube (128 commits)")[![himanshu-saxena-metacube](https://avatars.githubusercontent.com/u/61271834?v=4)](https://github.com/himanshu-saxena-metacube "himanshu-saxena-metacube (120 commits)")[![pyvovarov-s](https://avatars.githubusercontent.com/u/58219818?v=4)](https://github.com/pyvovarov-s "pyvovarov-s (78 commits)")[![annakotiuk](https://avatars.githubusercontent.com/u/79214317?v=4)](https://github.com/annakotiuk "annakotiuk (70 commits)")[![kostiantynlitvinov](https://avatars.githubusercontent.com/u/97898156?v=4)](https://github.com/kostiantynlitvinov "kostiantynlitvinov (70 commits)")[![asmarovydlo](https://avatars.githubusercontent.com/u/15832795?v=4)](https://github.com/asmarovydlo "asmarovydlo (65 commits)")[![lera-coder](https://avatars.githubusercontent.com/u/52531167?v=4)](https://github.com/lera-coder "lera-coder (58 commits)")[![shubham-khandelwal2-metacube](https://avatars.githubusercontent.com/u/100573363?v=4)](https://github.com/shubham-khandelwal2-metacube "shubham-khandelwal2-metacube (58 commits)")[![geega](https://avatars.githubusercontent.com/u/1426310?v=4)](https://github.com/geega "geega (42 commits)")[![khushal-rathore-metacube](https://avatars.githubusercontent.com/u/100358680?v=4)](https://github.com/khushal-rathore-metacube "khushal-rathore-metacube (40 commits)")[![AnastasiiaKSpryker](https://avatars.githubusercontent.com/u/81179087?v=4)](https://github.com/AnastasiiaKSpryker "AnastasiiaKSpryker (36 commits)")[![yuliia-mishchan](https://avatars.githubusercontent.com/u/46601252?v=4)](https://github.com/yuliia-mishchan "yuliia-mishchan (33 commits)")[![kkicheglovspryker](https://avatars.githubusercontent.com/u/81977971?v=4)](https://github.com/kkicheglovspryker "kkicheglovspryker (33 commits)")[![michbeck](https://avatars.githubusercontent.com/u/552911?v=4)](https://github.com/michbeck "michbeck (32 commits)") ### Embed Badge ![Health badge](/badges/spryker-robotframework-suite-tests/health.svg) ``` [![Health](https://phpackages.com/badges/spryker-robotframework-suite-tests/health.svg)](https://phpackages.com/packages/spryker-robotframework-suite-tests) ``` ### Alternatives [phpspec/prophecy Highly opinionated mocking framework for PHP 5.3+ 8.5k551.7M682](/packages/phpspec-prophecy)[brianium/paratest Parallel testing for PHP 2.5k118.8M754](/packages/brianium-paratest)[beberlei/assert Thin assertion library for input validation in business models. 2.4k96.9M570](/packages/beberlei-assert)[mikey179/vfsstream Virtual file system to mock the real file system in unit tests. 1.4k108.0M2.7k](/packages/mikey179-vfsstream)[orchestra/testbench Laravel Testing Helper for Packages Development 2.2k39.1M32.1k](/packages/orchestra-testbench)[phpspec/phpspec Specification-oriented BDD framework for PHP 7.1+ 1.9k36.7M3.1k](/packages/phpspec-phpspec) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)