Skip to content

Latest commit

 

History

History
152 lines (101 loc) · 6.02 KB

UPGRADING.md

File metadata and controls

152 lines (101 loc) · 6.02 KB
Raw

Upgrading from SitePrism 4.x to 5.x

DSL name validation

The work to ban invalid DSL names has been continued and extended. This is now enabled by default.

Setting the env variable SITEPRISM_DSL_VALIDATION_DISABLED (Name has changed from v4), to anything will disable these checks from being performed during the build metaprogram phase of suite execution.

An additional piece of work to further amplify the gems logging has been done, so no additional work from the user is required to make these changes function or be diagnosable (Should something go wrong).

NB: no as a filename was erroneously banned in the early 5.0.x versions

Shadow Root

Initial work to support Shadow Root's has been added to the codebase.

You can define a shadow root by setting :shadow_root to true when defining a section or sections

Input Fragments / Raw HTML testing

SitePrism will no longer support interrogating html fragments or generating html on the fly using Capybara.string from version 6 onwards. Using it in v5 will throw a Deprecation warning.

Ideally you would use a full page object generated in the standard way. A verbose page setup correctly is not that much more effort to create and is much more manipulable and re-usable than generating a Capybara.string on the fly.

Removal of #page method for SitePrism::Page

This method has been removed, it was often used erroneously. If you want to interrogate the full page, it will now revert back to the default Capybara logic. The usage of this method on SitePrism::Section was removed in v4.

Upgrading from SitePrism 3.x to 4.x

DSL name validation

An initial attempt to start banning invalid DSL names has been introduced through a DSLValidator module.

For 4.x this will be disabled by default. We may look to switch this to a default on/toggleable state further down the road, but for now this is experimental.

Setting the env variable SITEPRISM_DSL_VALIDATION_ENABLED will then perform these checks during the build metaprogram phase of suite execution.

It is highly advisable to set full verbose logging on when using this by using SitePrism.logger.level = :DEBUG.

Passing blocks to invalid DSL items

SitePrism 3.x permitted you to create DSL items using a block in all situations. However when you created an item that was an :element, :elements or :sections the overall resultant method generation was an error method (This is because we don't permit blocks for these DSL items).

Now in 4.x we ban these creations and will hard-fail instantly.

Removal of #page method for SitePrism::Section

In SitePrism 3.x (Specifically when using capybara < 3.29), often people would want to obtain their "current" scope, either deliberately or by using a chained method. The way we used to do this was by calling #page, which would then return your scope. From later versions of capybara they implemented a #to_capybara_node method which would be called and pre-chained to ensure your scope was correct.

At SitePrism, we left in the legacy method. However in the v4 beta the method will crash with a fatal error (And this will be removed entirely in the v4 proper -> so you'll get a standard Ruby NoMethodError).

When operating on a regular SitePrism::Page object the call to #page will still work and it will still return either the Capybara::String that was passed in as a html fragment or the current Capybara::Session.

However ... This is also not advisable, and as such this is now deprecated

Instead if you want to obtain your full page scope. Use #parent_page to get to your top level page, or simply using #parent will get you to go up one level of scoping. If you're already on the SitePrism::Page instance, calling Capybara.current_session will return you in the current session scope.

Upgrading from SitePrism 2.x to 3.x

Default Load Validations

SitePrism 2.x contains 1 inbuilt load validation for any Page that is a direct descendant of SitePrism::Page. This has now been removed. If you wish to retain the previous functionality then ...

class MyPage < SitePrism::Page
end

now becomes ...

class MyPage < SitePrism::Page
  load_validation { [displayed?, "Expected #{current_url} to match #{url_matcher} but it did not."] }
end

You can also create a BasePage class if you want to retain this functionality across all your pages ...

class BasePage < SitePrism::Page
   load_validation { [displayed?, "Expected #{current_url} to match #{url_matcher} but it did not."] }
end

And then you just need to have ...

class MyPage < BasePage
end

Error Classes

The entire set of error names have been re-written. Check error.rb for previous names.

Configuration Options

Previously site_prism (As of 2.17.1), had 3 configuration options. These were ...

  SitePrism.default_load_validations = true #=> Whether the default load validation for displayed? was set 
  SitePrism.use_implicit_waits = false #=> Whether site_prism would use Capybara's implicit waiting by default
  SitePrism.raise_on_wait_fors = false #=> Whether running wait_for_<element/section> methods that failed would crash

These have all been removed with the 3.0 release. Implicit Waiting is controlled / modifiable either in-line for each method-call, or you can set the default timeout by re-configuring Capybara.default_max_wait_time.

wait_until methods

Previously wait_until methods accepted a numerical value for wait time. The wait time should now be passed using hash args like: wait: <seconds>.

For example, previously:

@page.wait_until_dialog_invisible(10)
@page.wait_until_notification_flag_visible(5, count: 3)

These now become:

@page.wait_until_dialog_invisible(wait: 10)
@page.wait_until_notification_flag_visible(wait: 5, count: 3)

Note: If after upgrading you see Unused parameters passed to Capybara::Queries::SelectorQuery : [NUMBER] this may indicate that you still need to make this change.