Add ability to save page elements as screenshot files

Add ability to save page elements as screenshot files

Disable pytest's cacheprovider plugin

Disable pytest's cacheprovider plugin

Updates: Chrome log-level, pytest libs, Azure pipelines

Some minor updates:

• Use log-level 3 for default Chrome logging
• Use pytest-forked>=1.0.2
• Update Azure test pipeline

Update test reports

Update test reports

• Some changes to the way screenshots are saved for the reports

Allow passing a boolean value to desired capabilities

Allow passing a boolean value to desired capabilities

• All formats as of now:
  'KEY': 'VALUE'
'KEY': True
'KEY': False
caps['KEY'] = "VALUE"
caps['KEY'] = True
caps['KEY'] = False
  (Each pair must be on a separate line. You can interchange single and double quotes.)
  See https://github.com/seleniumbase/SeleniumBase/tree/master/examples/capabilities for the full ReadMe and sample capabilities files.

Refactor visual/layout testing

Refactor visual/layout testing

Add pytest-metadata to the requirements

Add pytest-metadata to the requirements

Prevent PytestDeprecationWarning

Small Fixes:

• Prevent PytestDeprecationWarning
• More efficient screenshots for logs

Fix method that finds all links on a web page

Fix method that finds all links on a web page

• Ignore parsing urls on pages that don't have :// in the url (ex: about:blank)

Automated Visual Testing

Automated Visual Testing

• Add self.check_window(name, level, baseline) method for automated visual testing
• Add methods for processing links and status codes on web pages:

self.get_unique_links()
self.get_link_status_code(link, allow_redirects=False, timeout=5)
self.assert_no_404_errors()
self.print_unique_links_with_status_codes()

• Update pytest versioning

More info on self.check_window(name="default", level=0, baseline=False)

            ***  Automated Visual Testing with SeleniumBase  ***

            The first time a test calls self.check_window() for a unique "name"
            parameter provided, it will set a visual baseline, meaning that it
            creates a folder, saves the URL to a file, saves the current window
            screenshot to a file, and creates the following three files
            with the listed data saved:
            tags_level1.txt  ->  HTML tags from the window
            tags_level2.txt  ->  HTML tags + attributes from the window
            tags_level3.txt  ->  HTML tags + attributes/values from the window

            Baseline folders are named based on the test name and the name
            parameter passed to self.check_window(). The same test can store
            multiple baseline folders.

            If the baseline is being set/reset, the "level" doesn't matter.

            After the first run of self.check_window(), it will compare the
            HTML tags of the latest window to the one from the initial run.
            Here's how the level system works:
            * level=0 ->
                DRY RUN ONLY - Will perform a comparison to the baseline, and
                               print out any differences that are found, but
                               won't fail the test even if differences exist.
            * level=1 ->
                HTML tags are compared to tags_level1.txt
            * level=2 ->
                HTML tags are compared to tags_level1.txt and
                HTML tags/attributes are compared to tags_level2.txt
            * level=3 ->
                HTML tags are compared to tags_level1.txt and
                HTML tags + attributes are compared to tags_level2.txt and
                HTML tags + attributes/values are compared to tags_level3.txt
            As shown, Level-3 is the most strict, Level-1 is the least strict.
            If the comparisons from the latest window to the existing baseline
            don't match, the current test will fail, except for Level-0 tests.

            You can reset the visual baseline on the command line by using:
                --visual_baseline
            As long as "--visual_baseline" is used on the command line while
            running tests, the self.check_window() method cannot fail because
            it will rebuild the visual baseline rather than comparing the html
            tags of the latest run to the existing baseline. If there are any
            expected layout changes to a website that you're testing, you'll
            need to reset the baseline to prevent unnecessary failures.

            self.check_window() will fail with "Page Domain Mismatch Failure"
            if the page domain doesn't match the domain of the baseline.

            If you want to use self.check_window() to compare a web page to
            a later version of itself from within the same test run, you can
            add the parameter "baseline=True" to the first time you call
            self.check_window() in a test to use that as the baseline. This
            only makes sense if you're calling self.check_window() more than
            once with the same name parameter in the same test.

            Automated Visual Testing with self.check_window() is not very
            effective for websites that have dynamic content that changes
            the layout and structure of web pages. For those, you're much
            better off using regular SeleniumBase functional testing.

            Example usage:
                self.check_window(name="testing", level=0)
                self.check_window(name="xkcd_home", level=1)
                self.check_window(name="github_page", level=2)
                self.check_window(name="wikipedia_page", level=3)