Update mkdocs

Author: mdmintz

README.md

@@ -1,5 +1,3 @@
-<meta property="og:title" content="SeleniumBase" />
-<meta property="og:description" content="Create browser tests for web and mobile user interfaces." />
 <meta property="og:image" content="https://cdn2.hubspot.net/hubfs/100006/images/big_blue_logo_7.png" />
 <link rel="icon" href="https://seleniumbase.io/img/logo4.png">
 <h2 align="center"><a align="center" href="https://github.com/seleniumbase/SeleniumBase/"><img align="center" src="https://cdn2.hubspot.net/hubfs/100006/images/blue_logo_7.png" alt="SeleniumBase" height="170"></a></h2>

docs/img/logo4.png

@@ -1,5 +1,5 @@
 mkdocs==1.1.2
-mkdocs-material==5.0.2
+mkdocs-material==5.1.1
 mkdocs-simple-hooks==0.1.0
 mkdocs-material-extensions==1.0
 mkdocs-minify-plugin==0.3.0

docs/requirements.txt

@@ -1,4 +1,4 @@
-![](http://cdn2.hubspot.net/hubfs/100006/images/masterqa_logo-11.png "MasterQA")
+![](https://cdn2.hubspot.net/hubfs/100006/images/masterqa_logo-11.png "MasterQA")
 
 ### MasterQA combines automation with manual verification steps.
 
@@ -19,7 +19,7 @@ After each automation checkpoint, a pop-up window will ask the user questions fo
 
 When the test run completes, as seen from [this longer example](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/master_qa/masterqa_test.py), you'll reach the results page that appears after answering all the verification questions. (Failed verifications generate links to screenshots and log files.)
 
-![](http://cdn2.hubspot.net/hubfs/100006/images/hybrid_screen.png "MasterQA")
+![](https://cdn2.hubspot.net/hubfs/100006/images/hybrid_screen.png "MasterQA")
 
 You may have noticed the ``Incomplete Test Runs`` row on the results page. If the value for that is not zero, it means that one of the automated steps failed. This could happen if you tell your script to perform an action on an element that doesn't exist. Now that we're mixing automation with manual QA, it's good to tell apart the failures from each. The results_table CSV file contains a spreadsheet with the details of each failure (if any) for both manual and automated steps.
 
@@ -38,7 +38,7 @@ At the end of your test run, you'll receive a report with results, screenshots,
 
 ### Check out [masterqa_test.py](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/master_qa/masterqa_test.py) to learn how to write your own MasterQA tests:
 
-You'll notice that tests are written the same way as regular [SeleniumBase](http://seleniumbase.com) tests, with the key difference being a different import: ``from seleniumbase import MasterQA`` rather than ``from seleniumbase import BaseCase``. Now your Python test class will import ``MasterQA`` instead of ``BaseCase``.
+You'll notice that tests are written the same way as regular [SeleniumBase](https://seleniumbase.com) tests, with the key difference being a different import: ``from seleniumbase import MasterQA`` rather than ``from seleniumbase import BaseCase``. Now your Python test class will import ``MasterQA`` instead of ``BaseCase``.
 
 To add a manual verification step, use ``self.verify()`` in the code after each part of your test that needs a manual verification step. If you want to include a custom question, add text inside that call (in quotes). Example:
 
@@ -50,4 +50,4 @@ self.verify("Can you find the moon?")
 
 ---
 
-MasterQA is powered by [SeleniumBase](http://seleniumbase.com), the most advanced open-source automation framework on the [Planet](https://en.wikipedia.org/wiki/Earth).
+MasterQA is powered by [SeleniumBase](https://seleniumbase.com), the most advanced open-source automation framework on the [Planet](https://en.wikipedia.org/wiki/Earth).

examples/master_qa/ReadMe.md

@@ -19,8 +19,7 @@ markdown_extensions:
   - fontawesome_markdown
   - markdown.extensions.admonition
   - markdown.extensions.attr_list
-  - markdown.extensions.codehilite:
-      guess_lang: false
+  - markdown.extensions.codehilite
   - markdown.extensions.def_list
   - markdown.extensions.footnotes
   - markdown.extensions.meta
@@ -29,16 +28,16 @@ markdown_extensions:
 # Configuration
 theme:
   name: material
-  logo: https://seleniumbase.io/img/logo3a.png
-  favicon: img/favicon.ico
+  logo: img/logo3a.png
+  favicon: img/logo4.png
   language: en
   features:
     - tabs
 # Plugins
 plugins:
   - search
   - minify:
-      minify_html: true
+      minify_html: false
   - mkdocs-simple-hooks:
       hooks:
         on_pre_build: docs.prepare:main

mkdocs.yml

@@ -1,4 +1,4 @@
-![](http://cdn2.hubspot.net/hubfs/100006/images/masterqa_logo-11.png "MasterQA")
+![](https://cdn2.hubspot.net/hubfs/100006/images/masterqa_logo-11.png "MasterQA")
 
 ### MasterQA combines automation with manual verification steps.
 
@@ -19,7 +19,7 @@ After each automation checkpoint, a pop-up window will ask the user questions fo
 
 When the test run completes, as seen from [this longer example](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/master_qa/masterqa_test.py), you'll reach the results page that appears after answering all the verification questions. (Failed verifications generate links to screenshots and log files.)
 
-![](http://cdn2.hubspot.net/hubfs/100006/images/hybrid_screen.png "MasterQA")
+![](https://cdn2.hubspot.net/hubfs/100006/images/hybrid_screen.png "MasterQA")
 
 You may have noticed the ``Incomplete Test Runs`` row on the results page. If the value for that is not zero, it means that one of the automated steps failed. This could happen if you tell your script to perform an action on an element that doesn't exist. Now that we're mixing automation with manual QA, it's good to tell apart the failures from each. The results_table CSV file contains a spreadsheet with the details of each failure (if any) for both manual and automated steps.
 
@@ -38,7 +38,7 @@ At the end of your test run, you'll receive a report with results, screenshots,
 
 ### Check out [masterqa_test.py](https://github.com/seleniumbase/SeleniumBase/blob/master/examples/master_qa/masterqa_test.py) to learn how to write your own MasterQA tests:
 
-You'll notice that tests are written the same way as regular [SeleniumBase](http://seleniumbase.com) tests, with the key difference being a different import: ``from seleniumbase import MasterQA`` rather than ``from seleniumbase import BaseCase``. Now your Python test class will import ``MasterQA`` instead of ``BaseCase``.
+You'll notice that tests are written the same way as regular [SeleniumBase](https://seleniumbase.com) tests, with the key difference being a different import: ``from seleniumbase import MasterQA`` rather than ``from seleniumbase import BaseCase``. Now your Python test class will import ``MasterQA`` instead of ``BaseCase``.
 
 To add a manual verification step, use ``self.verify()`` in the code after each part of your test that needs a manual verification step. If you want to include a custom question, add text inside that call (in quotes). Example:
 
@@ -50,4 +50,4 @@ self.verify("Can you find the moon?")
 
 ---
 
-MasterQA is powered by [SeleniumBase](http://seleniumbase.com), the most advanced open-source automation framework on the [Planet](https://en.wikipedia.org/wiki/Earth).
+MasterQA is powered by [SeleniumBase](https://seleniumbase.com), the most advanced open-source automation framework on the [Planet](https://en.wikipedia.org/wiki/Earth).