feat(backend): Use Remixicons when new navbar is used #592
test.yml
on: pull_request
solidus_backend JS
32s
Matrix: solidus_admin / RSpec
Matrix: solidus_api / RSpec
Matrix: solidus_backend / RSpec
Matrix: solidus_core / RSpec
Matrix: solidus_legacy_promotions / RSpec
Matrix: solidus_promotions / RSpec
Matrix: solidus_sample / RSpec
Annotations
96 errors and 38 warnings
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage
Process completed with exit code 1.
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L48
Adjustments when the order is completed when the promotion system is configured to allow applying promotions to completed orders shows input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L57
Adjustments when the order is completed when the promotion system is configured to not allow applying promotions to completed orders does not show input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L43
Adjustments when the order is completed shows adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L74
Adjustments creating a manual adjustment creates a new adjustment
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L64
Adjustments shows the input field for applying a promotion
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L78
Promotion Categories delete allows an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L58
Promotion Categories edit allows an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L65
Promotion Categories edit shows validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage
Process completed with exit code 1.
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
legacy_promotions/spec/features/backend/orders/adjustments_spec.rb#L38
Adjustments when the order is completed admin managing adjustments shows both eligible and non-eligible adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L78
Promotion Categories delete should allow an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L65
Promotion Categories edit should show validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L58
Promotion Categories edit should allow an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage
Process completed with exit code 1.
|
|
solidus_legacy_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
legacy_promotions/spec/features/backend/orders/adjustments_spec.rb#L38
Adjustments when the order is completed admin managing adjustments shows both eligible and non-eligible adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L65
Promotion Categories edit should show validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L58
Promotion Categories edit should allow an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L78
Promotion Categories delete should allow an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_legacy_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage
Process completed with exit code 1.
|
|
solidus_legacy_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
legacy_promotions/spec/features/backend/orders/adjustments_spec.rb#L38
Adjustments when the order is completed admin managing adjustments shows both eligible and non-eligible adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L78
Promotion Categories delete should allow an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_legacy_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L65
Promotion Categories edit should show validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L58
Promotion Categories edit should allow an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage
Process completed with exit code 1.
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L58
Promotion Categories edit allows an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L65
Promotion Categories edit shows validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L78
Promotion Categories delete allows an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L57
Adjustments when the order is completed when the promotion system is configured to not allow applying promotions to completed orders does not show input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L48
Adjustments when the order is completed when the promotion system is configured to allow applying promotions to completed orders shows input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L43
Adjustments when the order is completed shows adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L74
Adjustments creating a manual adjustment creates a new adjustment
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L64
Adjustments shows the input field for applying a promotion
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage
Process completed with exit code 1.
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L48
Adjustments when the order is completed when the promotion system is configured to allow applying promotions to completed orders shows input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L57
Adjustments when the order is completed when the promotion system is configured to not allow applying promotions to completed orders does not show input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L43
Adjustments when the order is completed shows adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L74
Adjustments creating a manual adjustment creates a new adjustment
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L64
Adjustments shows the input field for applying a promotion
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L58
Promotion Categories edit allows an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L65
Promotion Categories edit shows validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L78
Promotion Categories delete allows an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage
Process completed with exit code 1.
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
legacy_promotions/spec/features/backend/orders/adjustments_spec.rb#L38
Adjustments when the order is completed admin managing adjustments shows both eligible and non-eligible adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L65
Promotion Categories edit should show validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L58
Promotion Categories edit should allow an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
legacy_promotions/spec/features/backend/promotions/promotion_categories_spec.rb#L78
Promotion Categories delete should allow an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage
Process completed with exit code 1.
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L78
Promotion Categories delete allows an admin to delete an existing promotion category
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L65
Promotion Categories edit shows validation errors
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/promotion_categories_spec.rb#L58
Promotion Categories edit allows an admin to edit an existing promotion category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L48
Adjustments when the order is completed when the promotion system is configured to allow applying promotions to completed orders shows input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L57
Adjustments when the order is completed when the promotion system is configured to not allow applying promotions to completed orders does not show input field for promotion code
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L43
Adjustments when the order is completed shows adjustments
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L74
Adjustments creating a manual adjustment creates a new adjustment
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage:
promotions/spec/system/solidus_promotions/backend/orders/adjustments_spec.rb#L64
Adjustments shows the input field for applying a promotion
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/orders/order_details_spec.rb#L511
Order Details as Admin Shipment edit page splitting to shipment receiving shipment can not backorder should not allow a shipment to split stock to itself
Failure/Error: within("tr", text: line_item.sku) { click_icon "arrows-h" }
Capybara::ElementNotFound:
Unable to find css ".fa-arrows-h" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/DIV[3]/DIV[1]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/orders/order_details_spec.rb#L521
Order Details as Admin Shipment edit page splitting to shipment receiving shipment can not backorder should split fine if more than one line_item is in the receiving shipment
Failure/Error: within("tr", text: line_item.sku) { click_icon "arrows-h" }
Capybara::ElementNotFound:
Unable to find css ".fa-arrows-h" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/DIV[3]/DIV[1]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/orders/order_details_spec.rb#L487
Order Details as Admin Shipment edit page splitting to shipment receiving shipment can not backorder should not allow a split if the receiving shipment qty plus the incoming is greater than the count_on_hand
Failure/Error: within("tr", text: line_item.sku) { click_icon "arrows-h" }
Capybara::ElementNotFound:
Unable to find css ".fa-arrows-h" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/DIV[3]/DIV[1]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/orders/order_details_spec.rb#L468
Order Details as Admin Shipment edit page splitting to shipment should delete the old shipment if enough are split off
Failure/Error: within("tr", text: line_item.sku) { click_icon "arrows-h" }
Capybara::ElementNotFound:
Unable to find css ".fa-arrows-h" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/DIV[3]/DIV[1]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/orders/order_details_spec.rb#L449
Order Details as Admin Shipment edit page removing an item removes only the one item
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash" within #<Capybara::Node::Element tag="div" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/DIV[3]/DIV[1]/DIV[1]/DIV[2]">
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/products/edit/images_spec.rb#L109
Product Images uploading, editing, and deleting an image with several variants should allow an admin to re-assign an image to another variant
Failure/Error: click_icon(:edit)
Capybara::ElementNotFound:
Unable to find css ".fa-edit"
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/products/edit/images_spec.rb#L75
Product Images uploading, editing, and deleting an image Using the drag and drop upload window should allow an admin to upload an image and edit an image for a product
Failure/Error: click_icon(:edit)
Capybara::ElementNotFound:
Unable to find css ".fa-edit"
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/products/edit/images_spec.rb#L35
Product Images uploading, editing, and deleting an image when the user cannot create images does not show links for creating images
Failure/Error: click_icon(:edit)
Capybara::ElementNotFound:
Unable to find css ".fa-edit"
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/products/edit/images_spec.rb#L94
Product Images uploading, editing, and deleting an image Using Active Storage should show a no image placeholder when images fail to download
Failure/Error: click_icon(:edit)
Capybara::ElementNotFound:
Unable to find css ".fa-edit"
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/products/edit/images_spec.rb#L44
Product Images uploading, editing, and deleting an image Using the new image link should allow an admin to upload and edit an image for a product
Failure/Error: click_icon(:edit)
Capybara::ElementNotFound:
Unable to find css ".fa-edit"
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/orders/customer_details_spec.rb#L85
Customer Details editing an order selected country has no state changes state field to text input
Failure/Error: within("table#listing_orders") { click_icon(:edit) }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="table" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/orders/customer_details_spec.rb#L156
Customer Details editing an order errors when no shipping methods are available
Failure/Error: within("table#listing_orders") { click_icon(:edit) }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="table" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/orders/customer_details_spec.rb#L137
Customer Details editing an order for an order in confirm state with a user updating order email works
Failure/Error: within("table#listing_orders") { click_icon(:edit) }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="table" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/orders/customer_details_spec.rb#L118
Customer Details editing an order should show validation errors
Failure/Error: within("table#listing_orders") { click_icon(:edit) }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="table" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/orders/customer_details_spec.rb#L100
Customer Details editing an order should be able to update customer details for an existing order
Failure/Error: within("table#listing_orders") { click_icon(:edit) }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="table" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/configuration/tax_categories_spec.rb#L48
Tax Categories admin editing a tax category should be able to update an existing tax category
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/products/pricing_spec.rb#L169
Pricing in the prices tab deleting will delete the non-default price
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/FIELDSET[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/products/pricing_spec.rb#L179
Pricing in the prices tab deleting does not break when default price is deleted
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/FIELDSET[1]/TABLE[1]/TBODY[1]/TR[2]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/products/pricing_spec.rb#L151
Pricing in the prices tab editing will not reset the currency to default
Failure/Error: click_icon :edit
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/fieldset/table/tr[1]">
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/products/pricing_spec.rb#L133
Pricing in the prices tab editing has a working edit page
Failure/Error: click_icon :edit
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/fieldset/table/tr[2]">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/products_spec.rb#L295
Products as admin user cloning a product cloning a deleted product should allow an admin to clone a deleted product
Failure/Error: click_icon :copy
Capybara::ElementNotFound:
Unable to find css ".fa-copy" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/products_spec.rb#L283
Products as admin user cloning a product should allow an admin to clone a product
Failure/Error: click_icon :copy
Capybara::ElementNotFound:
Unable to find css ".fa-copy" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/products_spec.rb#L375
Products as admin user deleting a product product details are still viewable
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash"
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/configuration/shipping_methods_spec.rb#L97
Shipping Methods update can update the existing calculator
Failure/Error: click_icon :edit
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="table" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/configuration/shipping_methods_spec.rb#L110
Shipping Methods update can change the calculator
Failure/Error: click_icon :edit
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="table" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/edit/products_spec.rb#L9
Product Details editing a product should list the product details
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/edit/products_spec.rb#L29
Product Details editing a product should handle slug changes
Failure/Error: click_icon(:edit)
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/edit/products_spec.rb#L54
Product Details when default price is deleted does not show the master price
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/edit/products_spec.rb#L80
Product Details deleting a product is still able to find the master variant
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/configuration/taxonomies_spec.rb#L51
Taxonomies edit should allow an admin to update an existing taxonomy
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/div/table/tbody/tr">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/edit/products_spec.rb#L80
Product Details deleting a product is still able to find the master variant
Failure/Error: click_icon :trash
Capybara::ElementNotFound:
Unable to find css ".fa-trash" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L115
Product Stock given a product with a variant and a stock location with stock locations that don't have stock items for variant yet can add stock items to other stock locations
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L98
Product Stock given a product with a variant and a stock location with two variants, one of which tracks inventory while the other doesn't allows modifying the count on hand only on the variant which tracks inventory
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L93
Product Stock given a product with a variant and a stock location with two variants, one of which tracks inventory while the other doesn't allows modifying backorderable only on the variant which tracks inventory
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L41
Product Stock given a product with a variant and a stock location with no stock location renders
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/table/tbody/tr">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L59
Product Stock given a product with a variant and a stock location can create a negative stock adjustment
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L47
Product Stock given a product with a variant and a stock location contains a link to recent stock movements
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L67
Product Stock given a product with a variant and a stock location can toggle backorderable
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/stock_management_spec.rb#L51
Product Stock given a product with a variant and a stock location can create a positive stock adjustment
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/HTML/BODY[1]/DIV[5]/DIV[1]/DIV[1]/TABLE[1]/TBODY[1]/TR[1]">
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/configuration/taxonomies_spec.rb#L51
Taxonomies edit should allow an admin to update an existing taxonomy
Failure/Error: within_row(1) { click_icon :edit }
Capybara::ElementNotFound:
Unable to find css ".fa-edit" within #<Capybara::Node::Element tag="tr" path="/html/body/div[5]/div/div/div/table/tbody/tr">
|
|
solidus_api / Rails 8.0, Ruby 3.4, sqlite, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_api / Rails 8.0, Ruby 3.4, sqlite, activestorage:
api/spec/requests/spree/api/checkouts_spec.rb#L87
Checkouts PUT 'update' transitioning to delivery can update addresses and transition from address to delivery
Skipped: SQLite adapter fails sometimes to provide a unique index for the convoluted chain
of ActiveRecord persistence calls that happen on
https://github.com/solidusio/solidus/blob/8b03161a1894a7d10c8d95f62c016da55027d2b0/core/app/models/spree/stock/simple_coordinator.rb#L83
|
|
solidus_api / Rails 8.0, Ruby 3.4, sqlite, activestorage:
api/spec/requests/spree/api/checkouts_spec.rb#L125
Checkouts PUT 'update' transitioning to delivery does not contain duplicate variant data in delivery return
Skipped: SQLite adapter fails sometimes to provide a unique index for the convoluted chain
of ActiveRecord persistence calls that happen on
https://github.com/solidusio/solidus/blob/8b03161a1894a7d10c8d95f62c016da55027d2b0/core/app/models/spree/stock/simple_coordinator.rb#L83
|
|
solidus_api / Rails 7.2, Ruby 3.3, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_api / Rails 8.1, Ruby 4.0, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_sample / Rails 7.2, Ruby 3.3, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_legacy_promotions / Rails 8.0, Ruby 3.4, sqlite, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_legacy_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_admin / Rails 7.2, Ruby 3.2, mysql, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_admin / Rails 7.2, Ruby 3.2, mysql, activestorage:
admin/spec/features/product_spec.rb#L105
Product option types clicking on Edit leads to option type edit page
Skipped: Temporarily skipped with xit
|
|
solidus_admin / Rails 8.1, Ruby 4.0, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_admin / Rails 8.1, Ruby 4.0, postgres, activestorage:
admin/spec/features/product_spec.rb#L105
Product option types clicking on Edit leads to option type edit page
Skipped: Temporarily skipped with xit
|
|
solidus_admin / Rails 8.0, Ruby 3.4, sqlite, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_admin / Rails 8.0, Ruby 3.4, sqlite, activestorage:
admin/spec/features/product_spec.rb#L105
Product option types clicking on Edit leads to option type edit page
Skipped: Temporarily skipped with xit
|
|
solidus_sample / Rails 8.0, Ruby 3.4, sqlite, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_sample / Rails 7.2, Ruby 3.2, mysql, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_core / Rails 7.2, Ruby 3.3, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_sample / Rails 8.1, Ruby 4.0, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_core / Rails 8.0, Ruby 3.4, sqlite, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_admin / Rails 7.2, Ruby 3.3, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_admin / Rails 7.2, Ruby 3.3, postgres, activestorage:
admin/spec/features/product_spec.rb#L105
Product option types clicking on Edit leads to option type edit page
Skipped: Temporarily skipped with xit
|
|
solidus_promotions / Rails 8.1, Ruby 4.0, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_promotions / Rails 7.2, Ruby 3.3, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_core / Rails 7.2, Ruby 3.2, mysql, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_core / Rails 8.1, Ruby 4.0, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_api / Rails 7.2, Ruby 3.2, mysql, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_legacy_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_promotions / Rails 7.2, Ruby 3.2, mysql, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_backend / Rails 8.1, Ruby 4.0, postgres, activestorage:
backend/spec/features/admin/products/edit/taxons_spec.rb#L51
Product Display Order managing display order with an XSS attempt displays the escaped HTML without executing it
Skipped: No reason given
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_backend / Rails 8.0, Ruby 3.4, sqlite, activestorage:
backend/spec/features/admin/products/edit/taxons_spec.rb#L51
Product Display Order managing display order with an XSS attempt displays the escaped HTML without executing it
Skipped: No reason given
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_backend / Rails 7.2, Ruby 3.3, postgres, activestorage:
backend/spec/features/admin/products/edit/taxons_spec.rb#L51
Product Display Order managing display order with an XSS attempt displays the escaped HTML without executing it
Skipped: No reason given
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
solidus_backend / Rails 7.2, Ruby 3.2, mysql, activestorage:
backend/spec/features/admin/products/edit/taxons_spec.rb#L51
Product Display Order managing display order with an XSS attempt displays the escaped HTML without executing it
Skipped: No reason given
|