Merge pull request #3 from ui-testing-academy/main

Sync main branch

.gitignore

@@ -6,6 +6,7 @@ _site
 Gemfile.lock
 vendor
 /docs/
+_draft
 
 ### Gulp ###
 package.json

Gemfile

@@ -9,23 +9,22 @@ ruby RUBY_VERSION
 #
 # This will help ensure the proper Jekyll version is running.
 # Happy Jekylling!
-gem "jekyll", "3.8.5"
+gem "jekyll", "4.1.1"
 
 # This is the default theme for new Jekyll sites. You may change this to anything you like.
 # gem "minima", "~> 2.0"
 
 # If you want to use GitHub Pages, remove the "gem "jekyll"" above and
 # uncomment the line below. To upgrade, run `bundle update github-pages`.
 # gem "github-pages", group: :jekyll_plugins
-gem "github-pages","~> 202" , group: :jekyll_plugins
 
 # If you have any plugins, put them here!
 group :jekyll_plugins do
-   gem "jekyll-feed", "~> 0.11.0"
-   gem "jekyll-paginate-v2", "2.0.0"
-   gem 'jekyll-seo-tag'
-   gem 'jekyll-gist'
-   gem 'jekyll-avatar'
+   gem "jekyll-feed", "~> 0.15.1"
+   gem "jekyll-paginate-v2", "3.0.0"
+   gem "jekyll-seo-tag", "2.7.1"
+   gem "jekyll-gist", "1.5.0"
+   gem "jekyll-avatar", "0.7.0"
 end
 
 # Windows does not include zoneinfo files, so bundle the tzinfo-data gem

_posts/2020-09-06-all-test-cases-should-be-independent.md → _articles/2020-09-06-all-test-cases-should-be-independent.md

@@ -1,7 +1,9 @@
 ---
+layout: article
 title: 'All test cases should be independent'
 description: 'We will explore why independent tests is a good practice and how to achieve this.'
-categories: [general, good-practices]
+categories: [ good-practices]
+permalink:  /:categories/:title/
 author: alex_zhukovich
 ---
 

_posts/2020-09-06-approaches-of-ui-testing.md → _articles/2020-09-06-approaches-of-ui-testing.md

@@ -1,7 +1,9 @@
 ---
+layout: article
 title: 'Approaches of UI testing'
 description: 'Different ways of UI testing can be done: manual testing, record-and-replay testing, and model-based testing. We will explore the pros and cons of each approach.'
-categories: [general, ui-testing]
+permalink:  /:categories/:title/
+categories: [ general-information ]
 author: alex_zhukovich
 ---
 

_posts/2020-09-06-naming-conventions-for-test-cases.md → _articles/2020-09-06-naming-conventions-for-test-cases.md

@@ -1,7 +1,9 @@
 ---
+layout: article
 title: 'Naming conventions for test cases'
 description: 'We will explore different naming conventions for test cases.'
-categories: [general, naming]
+permalink:  /:categories/:title/
+categories: [ naming]
 author: alex_zhukovich
 ---
 A name is an essential part of a test suite and each test scenario. When analyzing test reports, all you see are the names of the test cases. The right name of the test case provides information about the scenario, and often, it's enough information for understanding the main idea.

_posts/2020-09-19-separate-your-tests-from-the-test-automation-framework.md → _articles/2020-09-19-separate-your-tests-from-the-test-automation-framework.md

@@ -1,7 +1,9 @@
 ---
+layout: article
 title: 'Separate your tests from the test automation framework'
 description: 'We will explore reasons for separating test cases from the test automation framework.'
-categories: [general, good-practices]
+permalink:  /:categories/:title/
+categories: [ good-practices]
 author: alex_zhukovich
 ---
 The testing framework has a significant impact on the test cases in a project because each framework has its own approach for handling similar situations and issues. Even if you are happy with the framework, chances are that you will change it in the future.

_posts/2020-09-20-never-use-sleep-in-test-code.md → _articles/2020-09-20-never-use-sleep-in-test-code.md

@@ -1,7 +1,9 @@
 ---
+layout: article
 title: 'Never use sleep in test code'
 description: 'We will explore approaches for replacing a sleep method in test cases.'
-categories: [general, good-practices]
+permalink:  /:categories/:title/
+categories: [good-practices]
 author: alex_zhukovich
 ---
 Almost every application performs long-running operations, and automated UI test cases should wait until this operation is finished. Often we should wait in the following scenarios:
@@ -26,4 +28,3 @@ Sometimes we can face a different approach, when we have to integrate a test fra
 As you can see, we have more efficient approaches for replacing `sleep` in the test code, and reduce execution time. I recommend you verify conditions multiple times and don't wait until the timeout is over.
 
 Note: Many frameworks already have such functions.
-

_articles/nodes/general-information.md

@@ -0,0 +1,9 @@
+---
+title: General information
+layout: node
+description: General topics connected with UI testing.
+icon: file-text
+categories: [ general-information ]
+permalink: "/:categories/"
+---
+

_articles/nodes/good-practices.md

@@ -0,0 +1,9 @@
+---
+title: Good Practices
+layout: node
+description: Good practices which can be applied to UI testing.
+icon: star
+categories: [ good-practices]
+permalink: "/:categories/"
+---
+

_articles/nodes/naming.md

@@ -0,0 +1,9 @@
+---
+title: Naming
+layout: node
+description: Naming conventions for test cases.
+icon: bold
+categories: [ naming]
+permalink: "/:categories/"
+---
+

_config.yml

@@ -10,13 +10,13 @@ description:        UI Testing related content
 lang:               en
 
 # Site subpath, e.g. /blog
-baseurl:            ""
+baseurl:  
 
 # Permalink URLs structure, for permalink style options see: https://jekyllrb.com/docs/permalinks/
 permalink:          /:categories/:title/
 
 # Site base hostname & protocol, e.g. http://example.com
-url:                "https://ui-testing.academy"
+url:                
 
 # Site logo # e.g. logo.png, upload logo image file to /uploads/ folder
 logo: logo.svg    
@@ -88,23 +88,25 @@ disqus:
 google_analytics:
 
 # Pagination Settings
-pagination:
-  enabled:          true
-  per_page:         10
+# pagination:
+#  enabled:          true
+#  per_page:         6
   # permalink: '/page/:num/'
   # title_suffix: ' - page :num'
   # limit: 0
   # sort_field: 'date'
   # sort_reverse: true
 
+
+
 # Path to post content assets directory i.e post images, pdfs etc
 uploads:            /uploads/
 
 # Build settings
 markdown:           kramdown
 highlighter:        rouge
-
-gems:
+node_grid:          true
+plugins:
   - jekyll-feed
   - jekyll-seo-tag
   - jekyll-gist
@@ -123,6 +125,9 @@ collections:
     output:         false
   changelogs:
     output:         false
+  articles:
+    output:         true
+    layout:         article
 
 # Defaults
 defaults:

_faqs/bug-repost-propose-improvement-request-topic.md

@@ -1,6 +1,6 @@
 ---
 title: How to send a bug report/improvement proposal/request a topic?
-categories: [faq]
+categories: [ faq]
 ---
 
 We want to grow and improve the project. If you found any issue in our project and you know how to improve the project, or you want to see more topic, please share your feedback with us via [GitHub issues](https://github.com/AlexZhukovich/ui-testing.academy/issues/){:target="_blank"} or [Contact form](/contact/).

_includes/breadcrumbs.html

@@ -0,0 +1,12 @@
+<ul id="breadcrumbs" class="uk-breadcrumb">
+  {% assign crumbs = page.url | remove:'/index.html' | split: '/' %}
+  <li><a href="{{site.baseurl}}/">Home</a></li>
+  {% for crumb in crumbs offset: 1 %}
+  {% if forloop.last %}
+
+  {% else %}
+   <li><a
+    href="{{site.baseurl}}{% assign crumb_limit = forloop.index | plus: 1 %}{% for crumb in crumbs limit: crumb_limit %}{{ crumb | append: '/' | replace:'without-plugin/','without-plugins/' }}{% endfor %}">{{ crumb | replace:'-',' ' | remove:'.html' | capitalize }}</a></li>
+  {% endif %}
+  {% endfor %}
+</ul>