AO3-6807 Fix offer URL capitalisation in errors (otwcode#5235)

* AO3-6807 Fix offer URL capitalisation in errors

* Attempted flaky text fix

Author: Bilka2

config/locales/models/en.yml

@@ -16,6 +16,8 @@ en:
         support: Support
         tag_wrangling: Tag Wrangling
         translation: Translation
+      challenge_signup/offers:
+        url: Offer URL
       challenge_signup/requests:
         url: Request URL
       chapters/creatorships:
@@ -37,6 +39,8 @@ en:
         meta_tag_id: Metatag
         sub_tag: Subtag
         sub_tag_id: Subtag
+      offer:
+        url: URL
       request:
         url: URL
       role:

features/gift_exchanges/challenge_giftexchange.feature

@@ -120,7 +120,7 @@ Feature: Gift Exchange Challenge
       And I submit
     Then I should see "URL: https://example.com/url_for_prompt"
 
-  Scenario: Invalid URL is disallowed when editing a signup
+  Scenario: Invalid URL is disallowed when editing a request in a signup
     Given the gift exchange "Awesome Gift Exchange" is ready for signups
       And I edit settings for "Awesome Gift Exchange" challenge
       And I check "gift_exchange[request_restriction_attributes][url_allowed]"
@@ -132,6 +132,18 @@ Feature: Gift Exchange Challenge
       And I submit
     Then I should see "Request URL does not appear to be a valid URL."
 
+  Scenario: Invalid URL is disallowed when editing an offer in a signup
+    Given the gift exchange "Awesome Gift Exchange" is ready for signups
+      And I edit settings for "Awesome Gift Exchange" challenge
+      And I check "gift_exchange[offer_restriction_attributes][url_allowed]"
+      And I submit
+    When I am logged in as "myname1"
+      And I sign up for "Awesome Gift Exchange" with combination A
+      And I follow "Edit Sign-up"
+      And I fill in "Prompt URL:" with "i hereby offer you a bug."
+      And I submit
+    Then I should see "Offer URL does not appear to be a valid URL."
+
   Scenario: Sign-ups can be seen in the dashboard
     Given the gift exchange "Awesome Gift Exchange" is ready for signups
     When I am logged in as "myname1"

features/other_b/skin.feature

@@ -334,8 +334,8 @@ Feature: Non-public site and work skins
 
   @javascript
   Scenario: User can add a parent skin using the Custom CSS form
-    Given I am logged in
-      And I create the skin "Dad"
+    Given the skin "Dad" by "skinner"
+      And I am logged in as "skinner"
     When I go to the new skin page
     Then I should see "Advanced"
     When I follow "Show ↓"