@webship-js/magento-steps 0.0.0-stage → 2.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (31) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +405 -2
  3. package/package.json +66 -4
  4. package/scripts/build-site.sh +190 -0
  5. package/scripts/site-accounts.php +119 -0
  6. package/tests/features/01-admin-session.feature +35 -0
  7. package/tests/features/02-admin-menu-pages.feature +54 -0
  8. package/tests/features/03-admin-permissions.feature +51 -0
  9. package/tests/features/04-admin-grids.feature +97 -0
  10. package/tests/features/05-admin-products.feature +87 -0
  11. package/tests/features/06-admin-categories.feature +44 -0
  12. package/tests/features/07-admin-orders.feature +95 -0
  13. package/tests/features/08-admin-customers.feature +55 -0
  14. package/tests/features/09-admin-cart-price-rules.feature +49 -0
  15. package/tests/features/10-admin-content.feature +63 -0
  16. package/tests/features/11-admin-configuration-cache.feature +46 -0
  17. package/tests/features/12-admin-reviews-newsletter.feature +66 -0
  18. package/tests/features/20-storefront-catalog.feature +64 -0
  19. package/tests/features/21-storefront-search.feature +40 -0
  20. package/tests/features/22-storefront-product-cart.feature +68 -0
  21. package/tests/features/23-storefront-checkout.feature +65 -0
  22. package/tests/features/24-storefront-customer.feature +93 -0
  23. package/tests/features/25-storefront-wishlist-compare-contact.feature +50 -0
  24. package/tests/features/90-assertions-must-fail.feature +165 -0
  25. package/tests/fixtures/pixel.png +0 -0
  26. package/tests/step-definitions/README.md +36 -0
  27. package/tests/step-definitions/magento-admin-content.steps.js +818 -0
  28. package/tests/step-definitions/magento-admin.steps.js +856 -0
  29. package/tests/step-definitions/magento-helpers.js +992 -0
  30. package/tests/step-definitions/magento-storefront.steps.js +1797 -0
  31. package/tests/step-definitions/magento.steps.js +158 -0
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Webship.co
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,3 +1,406 @@
1
- # Temporary Holding Version
1
+ <p align="center"><img src="https://raw.githubusercontent.com/webship/magento-steps/2.0.x/assets/logo.svg" alt="Magento logo" width="96"></p>
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ # magento-steps
4
+
5
+ Cucumber step definitions for testing Magento Open Source stores with
6
+ [webship-js](https://webship.co/docs/webship-js/2.0.x), a BDD browser automation
7
+ harness built on Playwright and Cucumber-js.
8
+
9
+ `@webship-js/magento-steps` covers the admin panel (log in by account handle,
10
+ the menu and the pages, the grids, the forms, products, categories, orders from
11
+ the invoice to the credit memo, customers, cart price rules, pages and blocks,
12
+ the configuration, the cache and index state, what a restricted role may open)
13
+ and the storefront of the default theme (the menu, categories with layered
14
+ navigation, sorting and paging, search and its suggestions, the product page
15
+ with its options, the mini cart, the cart, the checkout through to the order
16
+ number, the customer account, the wish list, the comparison list, reviews, the
17
+ newsletter, field errors).
18
+
19
+ Every step was written from a round of testing the real pages in a browser, and
20
+ the whole suite runs against a real store: CI builds Magento Open Source 2.4.9
21
+ with its sample data in [DDEV](https://ddev.com) on every push and pull request;
22
+ see [`.github/workflows/test.yml`](.github/workflows/test.yml). No step phrase
23
+ carries the name of the platform.
24
+
25
+ The pack is for **Magento Open Source**, the community edition. It needs no
26
+ account, no access key and no paid or external service.
27
+
28
+ ## Requirements
29
+
30
+ - Node.js 20 or later
31
+ - A webship-js 2.0 test project (`webship-js` 2.0.10 or later)
32
+ - A Magento Open Source 2.4 store to test, with the default storefront theme
33
+ and the default admin theme, in English
34
+
35
+ ## Install
36
+
37
+ ```bash
38
+ npm install --save-dev @webship-js/magento-steps
39
+ ```
40
+
41
+ ## Quick start
42
+
43
+ 1. Add the step files to the `require` list of your webship-js `cucumber.js`:
44
+
45
+ ```javascript
46
+ require: [
47
+ 'node_modules/webship-js/tests/step-definitions/**/*.js',
48
+ 'node_modules/@webship-js/magento-steps/tests/step-definitions/*.js',
49
+ 'tests/step-definitions/**/*.js',
50
+ ],
51
+ ```
52
+
53
+ 2. Point `launchUrl` at the store, give the admin path and name the accounts
54
+ the suite logs in with (see [Accounts](#accounts)):
55
+
56
+ ```javascript
57
+ worldParameters: {
58
+ launchUrl: process.env.LAUNCH_URL || 'https://your-store.example',
59
+ adminPath: 'admin',
60
+ users: {
61
+ admin: { username: 'admin', password: process.env.ADMIN_PASSWORD },
62
+ customer: { email: 'customer@example.com', password: process.env.CUSTOMER_PASSWORD, name: 'Casey Customer' },
63
+ },
64
+ },
65
+ ```
66
+
67
+ 3. Copy a feature file from [`tests/features/`](tests/features/) into your
68
+ project and adjust the products, categories and texts to your catalog.
69
+
70
+ 4. Run the suite:
71
+
72
+ ```bash
73
+ npx cucumber-js
74
+ ```
75
+
76
+ ## What is included
77
+
78
+ | Path | Purpose |
79
+ | --- | --- |
80
+ | `tests/step-definitions/magento-admin.steps.js` | Admin panel: session, named pages, page title, menu, access denied, page buttons, grids, forms, tabs. |
81
+ | `tests/step-definitions/magento-admin-content.steps.js` | Admin content: products, the category tree, orders, customers, configuration, cache and index, clean-up. |
82
+ | `tests/step-definitions/magento-storefront.steps.js` | Storefront: customer session, menu, breadcrumbs, product list, search, product page, mini cart, cart, checkout, account, wish list, compare, reviews, newsletter, field errors. |
83
+ | `tests/step-definitions/magento.steps.js` | Both sides: messages, confirmation dialogs, the settled wait. |
84
+ | `tests/step-definitions/magento-helpers.js` | Shared plumbing. It registers no step. |
85
+ | `tests/features/*.feature` | Reference features for a store with the sample data. |
86
+ | `tests/features/90-assertions-must-fail.feature` | Scenarios that state something false: `npm run test:must-fail` passes only when every one of them fails with a helpful message. |
87
+ | `scripts/build-site.sh`, `scripts/site-accounts.php` | Build the test store with DDEV and create the test accounts. |
88
+ | `tests/check-examples.js` | Checks every `Example #n:` line and every feature step against the step patterns. |
89
+
90
+ ## Steps
91
+
92
+ 128 step definitions. The JSDoc block above each one holds five examples.
93
+
94
+ ### Admin panel: session, pages, menu
95
+
96
+ ```gherkin
97
+ Given I am logged in to the admin panel as "admin"
98
+ When I log in to the admin panel with the username "admin" and the password "wrong-password"
99
+ When I log out of the admin panel
100
+ Given I am not logged in to the admin panel
101
+ Then I should be logged in to the admin panel as "sales"
102
+ When I go to the "products" admin page
103
+ Then the admin page title should be "Products"
104
+ Then I should see the "Sales > Orders" admin menu
105
+ When I open the "Catalog > Products" admin menu item
106
+ Then I should see the access denied page
107
+ When I click the "Add New Page" page action
108
+ ```
109
+
110
+ Named pages: dashboard, orders, invoices, shipments, credit memos, products, new
111
+ product, categories, customers, customer groups, cart price rules, new cart
112
+ price rule, catalog price rules, newsletter subscribers, reviews, pending
113
+ reviews, pages, new page, blocks, configuration, cache management, index
114
+ management, users, roles, product attributes, order statuses, my account; or a
115
+ route such as `sales/order`.
116
+
117
+ ### Admin panel: grids
118
+
119
+ ```gherkin
120
+ When I search the grid for "Joust Duffle Bag"
121
+ When I filter the grid by "Type" with "Configurable Product"
122
+ When I clear the grid filters
123
+ Then the grid should show 19 records
124
+ Then the grid should have 20 rows
125
+ Then I should see the "Joust Duffle Bag" grid row
126
+ Then the "Status" column of the "Joust Duffle Bag" grid row should be "Enabled"
127
+ When I sort the grid by "Name" ascending
128
+ Then the grid should be sorted by "Name" ascending
129
+ When I go to the next page of the grid
130
+ Then the grid should be on page 2
131
+ When I show 50 grid rows per page
132
+ When I select the "WS-TEST-BAG" grid row
133
+ When I run the "Change status > Disable" grid action
134
+ When I open the "Home Page" grid row
135
+ ```
136
+
137
+ The steps work on both kinds of grid of the admin panel: the listing with a
138
+ keyword search and a Filters panel (products, orders, customers, pages) and the
139
+ older grid with a filter row (cart price rules, reviews, newsletter
140
+ subscribers, cache, index).
141
+
142
+ ### Admin panel: forms
143
+
144
+ ```gherkin
145
+ When I set the "Product Name" form field to "Test Bag"
146
+ When I set the "Visibility" form field to "Catalog, Search"
147
+ When I turn the "Enable Product" form switch off
148
+ Then the "SKU" form field should be "TEST-SKU-1"
149
+ When I choose "Bags" in the "Categories" form field
150
+ When I open the "Images And Videos" form section
151
+ When I open the "Account Information" admin tab
152
+ Then I should see the form error "This is a required field." for the "Product Name" field
153
+ When I save the form
154
+ ```
155
+
156
+ ### Admin panel: catalog, orders, customers, settings
157
+
158
+ ```gherkin
159
+ When I open the product "24-MB01" in the admin panel
160
+ When I add the image "pixel.png" to the product gallery
161
+ Then the product gallery should have 1 image
162
+ When I select the "Gear" category in the tree
163
+ Then I should see the "Bags" category in the tree
164
+ When I open the last placed order in the admin panel
165
+ Then I should see the last placed order in the orders grid
166
+ Then the order status should be "Pending"
167
+ When I add the order comment "Checked by the test suite"
168
+ When I put the order on hold
169
+ When I invoice the order
170
+ When I ship the order
171
+ When I refund the order
172
+ When I cancel the order
173
+ When I open the customer "customer@example.com" in the admin panel
174
+ When I go to the "general" configuration section
175
+ When I set the "Store Name" configuration field of "Store Information" to "Test Store"
176
+ Then some cache types should be invalidated
177
+ When I flush the cache
178
+ Then no cache type should be invalidated
179
+ When I rebuild the invalid indexes
180
+ Then every index should be ready
181
+ Given there is no product "TEST-SKU-1"
182
+ Given there is no category "Test Category"
183
+ ```
184
+
185
+ `there is no …` deletes what it finds, through the admin panel: a product, a
186
+ customer, a page, a block, a cart price rule, a review, a newsletter subscriber
187
+ or a category. It is how a scenario removes what it created.
188
+
189
+ ### Storefront
190
+
191
+ ```gherkin
192
+ Given I am logged in as the customer "customer"
193
+ When I log out of the store
194
+ Then I should be logged in to the store as "Casey Customer"
195
+ When I open the "Gear > Bags" store menu item
196
+ Then the breadcrumbs should be "Home > Gear > Bags"
197
+ Then the product list should have 14 products
198
+ When I filter the product list by "Activity" with "Yoga"
199
+ When I sort the product list by "Price"
200
+ When I set the product list direction to descending
201
+ Then the product list should be ordered by price descending
202
+ When I view the product list as a list
203
+ When I go to the next page of the product list
204
+ When I search the store for "yoga"
205
+ When I type "yog" in the store search
206
+ Then I should see the search suggestion "yoga"
207
+ When I choose the "Size" option "M"
208
+ When I set the product quantity to 2
209
+ When I add the product to the cart
210
+ When I open the "Reviews" product tab
211
+ Then the mini cart should show 2 items
212
+ When I go to the cart
213
+ When I change the cart quantity of "Joust Duffle Bag" to 3
214
+ Then the cart order total should be "$117.00"
215
+ When I apply the coupon "TEST10"
216
+ When I estimate shipping to "United States", "Texas", "78701"
217
+ When I choose the "Flat Rate" shipping method
218
+ When I go to the checkout
219
+ When I fill in the checkout email with "guest@example.com"
220
+ When I fill in the shipping address:
221
+ When I continue to the payment step
222
+ When I choose the "Check / Money order" payment method
223
+ When I place the order
224
+ Then I should see the order confirmation
225
+ Then my order history should list the last placed order as "Pending"
226
+ When I add the address:
227
+ Then my address book should contain "9 Test Road"
228
+ When I add the product to my wish list
229
+ When I add the product to the comparison list
230
+ When I review the product with 4 stars, the summary "Good bag" and the text "It holds everything."
231
+ When I subscribe "reader@example.com" to the newsletter
232
+ When I fill in the "Password" store field with "Secret123456789!"
233
+ When I press the "Create an Account" store button
234
+ Then I should see the field error "This is a required field." for "First Name"
235
+ ```
236
+
237
+ Every store page also holds a hidden sign-in popup with an "Email" and a
238
+ "Password" of its own, and the header repeats the texts of several buttons: the
239
+ two `store field` and `store button` steps take the field and the button of
240
+ the form a person sees.
241
+
242
+ `I place the order` remembers the order number of the success page: "the last
243
+ placed order" is then found in the orders grid of the admin panel and in the
244
+ order history of the customer, in the same scenario.
245
+
246
+ ### Both sides
247
+
248
+ ```gherkin
249
+ Then I should see the success message "You saved the product."
250
+ Then I should not see an error message
251
+ Then I should see the confirmation "Are you sure you want to delete this category?"
252
+ When I confirm the action
253
+ When I dismiss the confirmation
254
+ When I wait for the page to settle
255
+ ```
256
+
257
+ ## Accounts
258
+
259
+ The accounts are configuration, not test data. They are named in
260
+ `worldParameters.users` of `cucumber.js` and created once on the site; a
261
+ feature never creates or deletes one of them.
262
+
263
+ | Handle | Kind | What it is |
264
+ | --- | --- | --- |
265
+ | `admin` | admin user (`username`) | An administrator with every resource. |
266
+ | `sales` | admin user (`username`) | An admin user with a role that allows Sales only. |
267
+ | `customer` | customer (`email`) | A customer with a default billing and shipping address. |
268
+ | `shopper` | customer (`email`) | A second customer with an address. |
269
+
270
+ A customer that a scenario registers is content: the scenario removes it
271
+ (`Given there is no customer "…"`). Orders cannot be deleted in the admin
272
+ panel: every run leaves its orders behind, closed or cancelled.
273
+
274
+ ## The test store
275
+
276
+ `scripts/build-site.sh` builds the store the suite runs against, without a
277
+ question asked, in one DDEV project (`magentosteps`,
278
+ `https://magentosteps.ddev.site`):
279
+
280
+ ```bash
281
+ scripts/build-site.sh # the site goes to ../magento-site, or to $SITE_DIR
282
+ npm test
283
+ ```
284
+
285
+ - **Edition.** Magento Open Source 2.4.9 (`magento/project-community-edition`),
286
+ PHP 8.4, MariaDB 11.4, OpenSearch 3 through the `ddev/ddev-opensearch` add-on
287
+ (its dashboards service is left out), the sample data.
288
+ - **Where the packages come from.** The build uses the public Mage-OS mirror of
289
+ the Magento Open Source packages, `https://mirror.mage-os.org/`. It serves
290
+ the same releases as the vendor's repository without access keys, so the
291
+ build needs no account anywhere. `MIRROR_URL` points it at another Composer
292
+ repository.
293
+ - **Mode.** Production mode with the static content deployed: the pages answer
294
+ fast and the same way every time, which a test suite needs. On this
295
+ hardware compiling and deploying takes about 30 seconds.
296
+ - **Two-factor authentication is off.** The build installs without the modules
297
+ `Magento_TwoFactorAuth` and `Magento_AdminAdobeImsTwoFactorAuth`, the
298
+ supported way to log in to a local test site without a second factor. Never
299
+ do this on a site that is on the internet.
300
+ - **Nothing calls out.** The admin notification feed, the usage-data question
301
+ and the release notification are left out (`Magento_AdminNotification`,
302
+ `Magento_AdminAnalytics`, `Magento_ReleaseNotification`), as are the CAPTCHAs.
303
+ With the notification module off the admin panel has no system message bar:
304
+ the suite reads the cache and index state on Cache Management and Index
305
+ Management instead.
306
+ - **The bundled gateway extensions are off.** The edition ships payment gateway
307
+ and data-export extensions (`PayPal_Braintree*`, `Magento_PaymentServices*`,
308
+ `Magento_ServiceProxy`, `Magento_Services*`, `Magento_SaaSCommon`,
309
+ `Magento_*DataExporter`). Not configured, they still made every storefront
310
+ page load two scripts from the gateway's servers and the checkout an asset of
311
+ the payment provider (seen in the browser round). The build leaves them out
312
+ at install time (`setup:install --disable-modules`; disabling them later
313
+ leaves their database triggers behind and orders fail): the storefront, the
314
+ checkout and the admin pages the suite opens then request nothing outside
315
+ the site. One admin page still does, Stores >
316
+ Configuration > Sales > Payment Methods (a core module); the suite never
317
+ opens it.
318
+ - **Deterministic sign-in.** The admin session lasts, the secret key in admin
319
+ addresses is off (`admin/security/use_form_key`), one admin account may be
320
+ used from two browsers (`admin/security/admin_account_sharing`), no account is
321
+ locked after failed sign-ins.
322
+ - **Indexes.** The indexers run on "Update on Save": a product a scenario saves
323
+ is in the store at once and no cron is needed. Cron is run once by the build
324
+ and is not left running.
325
+ - **Methods.** Check / Money order, Flat Rate, Free Shipping and the table rate
326
+ of the sample data: the offline methods the edition ships with. No payment
327
+ gateway, no carrier API.
328
+ - **Mail** goes to DDEV's Mailpit.
329
+
330
+ Footprint, measured: about 1.9 GB of memory for the three containers (web 550
331
+ to 700 MB, database 260 to 310 MB, search 1 GB), 1.4 GB for the project folder,
332
+ 3.5 GB of container images. The build takes about three minutes once the
333
+ packages are downloaded (four more for the first download) and under six
334
+ minutes on a GitHub runner; one run of the suite takes about 16 minutes locally
335
+ and 19 minutes on the runner.
336
+
337
+ ## What the pages really do
338
+
339
+ Things the browser round showed, which the steps are built on:
340
+
341
+ - A page is "loaded" long before it works. `document.readyState` is `complete`
342
+ about 60 ms in, while RequireJS still loads 20 to 130 modules and the init
343
+ blocks are unprocessed; a "Sort By" change made then is swallowed. The steps
344
+ wait for the settled signal instead: no requested RequireJS module pending,
345
+ no `text/x-magento-init` block left, no request in flight, no loading mask,
346
+ three readings in a row.
347
+ - The admin forms are KnockoutJS models that read an input on its `change`
348
+ event. A value typed with Playwright's `fill()` shows in the field while the
349
+ form still holds nothing, and Save answers "This is a required field.". The
350
+ form steps fill, dispatch `change` and read the value back.
351
+ - Labels are not always the accessible name. Several admin selects carry
352
+ `aria-label="notice-…"`; on the customer sign-in page the "Password" label
353
+ points at the field of a hidden popup. The steps find a field by the label
354
+ text of its wrapper.
355
+ - An admin grid keeps a hidden copy of its header first in the DOM, remembers
356
+ its filters, sorting and page size for the admin user, and saves them two
357
+ seconds after a change. A grid opened by name starts unfiltered; the steps
358
+ that set what must not leak wait for the save.
359
+ - The checkout shows its fields under a loading mask for a second; the star
360
+ labels of the review form lie on top of each other; the "Remove item" link of
361
+ the wish list shows on hover only; the store redirects to the home page five
362
+ seconds after a customer logs out.
363
+
364
+ ## Checks
365
+
366
+ ```bash
367
+ npm test # the whole suite (not the @must-fail scenarios)
368
+ npm run test:admin # the admin panel lane
369
+ npm run test:storefront # the storefront lane
370
+ npm run test:must-fail # every false statement must fail with a helpful message
371
+ npm run test:examples # the JSDoc examples and the feature steps against the patterns
372
+ npm run test:dry # undefined and ambiguous steps
373
+ ```
374
+
375
+ The suite leaves the site as it found it, apart from the orders: run it twice
376
+ in a row.
377
+
378
+ `BROWSER=firefox npm test` runs the suite in Firefox (`npx playwright install
379
+ firefox` once). Use it on a machine where other container projects start and
380
+ stop while the suite runs: Chromium aborts every request in flight with
381
+ `net::ERR_NETWORK_CHANGED` when a container network comes or goes, and Firefox
382
+ is started here with `network.notify.changed` off. `CUCUMBER_RETRY=1` runs a
383
+ failed scenario once more.
384
+
385
+ ## What is not covered
386
+
387
+ - The paid edition and its features, B2B, marketplace extensions, payment gateways and
388
+ carrier services: this pack is for the community edition and its offline
389
+ methods.
390
+ - The Page Builder stage (drag and drop): a page is created with its title,
391
+ heading and URL key; its body is not edited.
392
+ - The cookie restriction notice (off in a default installation), multiple
393
+ websites, stores and currencies, other languages than English, other themes
394
+ than the default ones, the mobile menu.
395
+ - The "Comments History" tab of an order: it stays empty in 2.4.9; the suite
396
+ reads the notes on the Information tab.
397
+ - Moving a category in the tree, bundle, grouped, virtual and downloadable
398
+ products, creating an order in the admin panel, tax rules.
399
+
400
+ ## License
401
+
402
+ MIT
403
+
404
+ ## Logo
405
+
406
+ The Magento logo in this README comes from Simple Icons 16.37.0 (CC0-1.0), filled with the colour the set lists for the brand. The Magento name and logo are trademarks of their owner; this pack is not affiliated with or endorsed by them.
package/package.json CHANGED
@@ -1,6 +1,68 @@
1
1
  {
2
2
  "name": "@webship-js/magento-steps",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
3
+ "version": "2.0.1",
4
+ "description": "Cucumber step definitions for testing Magento Open Source stores with webship-js: the admin panel (session, menu, grids, forms, catalog, orders, customers, cart price rules, content, configuration, cache and index, permissions) and the storefront (catalog, layered navigation, search, product page, cart, checkout, customer account, wish list, compare, reviews, newsletter).",
5
+ "main": "tests/step-definitions/magento.steps.js",
6
+ "files": [
7
+ "tests/step-definitions/*.js",
8
+ "tests/step-definitions/README.md",
9
+ "tests/features",
10
+ "tests/fixtures",
11
+ "scripts",
12
+ "README.md",
13
+ "LICENSE"
14
+ ],
15
+ "scripts": {
16
+ "test": "cucumber-js --config cucumber.js",
17
+ "test:dry": "cucumber-js --config cucumber.js --dry-run",
18
+ "test:admin": "CUCUMBER_TAGS='@admin and not @wip and not @must-fail' cucumber-js --config cucumber.js",
19
+ "test:storefront": "CUCUMBER_TAGS='@storefront and not @wip and not @must-fail' cucumber-js --config cucumber.js",
20
+ "test:must-fail": "node tests/check-must-fail.js",
21
+ "test:chromium": "BROWSER=chromium cucumber-js --config cucumber.js",
22
+ "test:firefox": "BROWSER=firefox cucumber-js --config cucumber.js",
23
+ "test:webkit": "BROWSER=webkit cucumber-js --config cucumber.js",
24
+ "test:headed": "HEADLESS=false cucumber-js --config cucumber.js",
25
+ "test:examples": "node tests/check-examples.js",
26
+ "generate-reports": "generate-reports"
27
+ },
28
+ "keywords": [
29
+ "magento",
30
+ "magento2",
31
+ "magento-open-source",
32
+ "e-commerce",
33
+ "webship-js",
34
+ "cucumber",
35
+ "cucumber-js",
36
+ "playwright",
37
+ "bdd",
38
+ "testing",
39
+ "e2e",
40
+ "gherkin"
41
+ ],
42
+ "author": "Webship.co",
43
+ "license": "MIT",
44
+ "repository": {
45
+ "type": "git",
46
+ "url": "git+https://github.com/webship/magento-steps.git"
47
+ },
48
+ "bugs": {
49
+ "url": "https://github.com/webship/magento-steps/issues"
50
+ },
51
+ "homepage": "https://github.com/webship/magento-steps#readme",
52
+ "publishConfig": {
53
+ "access": "public"
54
+ },
55
+ "engines": {
56
+ "node": ">= 20.0"
57
+ },
58
+ "peerDependencies": {
59
+ "webship-js": "^2.0.10"
60
+ },
61
+ "devDependencies": {
62
+ "tsx": "^4.23.0",
63
+ "webship-js": "^2.0.10"
64
+ },
65
+ "overrides": {
66
+ "@cucumber/cucumber": "^12"
67
+ }
68
+ }