Skip to content

Commit 6c01008

Browse files
Merge pull request #3 from ui-testing-academy/main
Sync main branch
2 parents e759638 + 98aae23 commit 6c01008

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

55 files changed

+362
-626
lines changed

.gitignore

+1
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ _site
66
Gemfile.lock
77
vendor
88
/docs/
9+
_draft
910

1011
### Gulp ###
1112
package.json

404.html

-25
This file was deleted.

Gemfile

+6-7
Original file line numberDiff line numberDiff line change
@@ -9,23 +9,22 @@ ruby RUBY_VERSION
99
#
1010
# This will help ensure the proper Jekyll version is running.
1111
# Happy Jekylling!
12-
gem "jekyll", "3.8.5"
12+
gem "jekyll", "4.1.1"
1313

1414
# This is the default theme for new Jekyll sites. You may change this to anything you like.
1515
# gem "minima", "~> 2.0"
1616

1717
# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
1818
# uncomment the line below. To upgrade, run `bundle update github-pages`.
1919
# gem "github-pages", group: :jekyll_plugins
20-
gem "github-pages","~> 202" , group: :jekyll_plugins
2120

2221
# If you have any plugins, put them here!
2322
group :jekyll_plugins do
24-
gem "jekyll-feed", "~> 0.11.0"
25-
gem "jekyll-paginate-v2", "2.0.0"
26-
gem 'jekyll-seo-tag'
27-
gem 'jekyll-gist'
28-
gem 'jekyll-avatar'
23+
gem "jekyll-feed", "~> 0.15.1"
24+
gem "jekyll-paginate-v2", "3.0.0"
25+
gem "jekyll-seo-tag", "2.7.1"
26+
gem "jekyll-gist", "1.5.0"
27+
gem "jekyll-avatar", "0.7.0"
2928
end
3029

3130
# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
File renamed without changes.

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

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
2+
layout: article
23
title: 'All test cases should be independent'
34
description: 'We will explore why independent tests is a good practice and how to achieve this.'
4-
categories: [general, good-practices]
5+
categories: [ good-practices]
6+
permalink: /:categories/:title/
57
author: alex_zhukovich
68
---
79

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

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
2+
layout: article
23
title: 'Approaches of UI testing'
34
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.'
4-
categories: [general, ui-testing]
5+
permalink: /:categories/:title/
6+
categories: [ general-information ]
57
author: alex_zhukovich
68
---
79

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

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
2+
layout: article
23
title: 'Naming conventions for test cases'
34
description: 'We will explore different naming conventions for test cases.'
4-
categories: [general, naming]
5+
permalink: /:categories/:title/
6+
categories: [ naming]
57
author: alex_zhukovich
68
---
79
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 renamed to _articles/2020-09-19-separate-your-tests-from-the-test-automation-framework.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
2+
layout: article
23
title: 'Separate your tests from the test automation framework'
34
description: 'We will explore reasons for separating test cases from the test automation framework.'
4-
categories: [general, good-practices]
5+
permalink: /:categories/:title/
6+
categories: [ good-practices]
57
author: alex_zhukovich
68
---
79
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 renamed to _articles/2020-09-20-never-use-sleep-in-test-code.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
2+
layout: article
23
title: 'Never use sleep in test code'
34
description: 'We will explore approaches for replacing a sleep method in test cases.'
4-
categories: [general, good-practices]
5+
permalink: /:categories/:title/
6+
categories: [good-practices]
57
author: alex_zhukovich
68
---
79
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
2628
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.
2729

2830
Note: Many frameworks already have such functions.
29-
+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: General information
3+
layout: node
4+
description: General topics connected with UI testing.
5+
icon: file-text
6+
categories: [ general-information ]
7+
permalink: "/:categories/"
8+
---
9+

_articles/nodes/good-practices.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: Good Practices
3+
layout: node
4+
description: Good practices which can be applied to UI testing.
5+
icon: star
6+
categories: [ good-practices]
7+
permalink: "/:categories/"
8+
---
9+

_articles/nodes/naming.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: Naming
3+
layout: node
4+
description: Naming conventions for test cases.
5+
icon: bold
6+
categories: [ naming]
7+
permalink: "/:categories/"
8+
---
9+

_config.yml

+12-7
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,13 @@ description: UI Testing related content
1010
lang: en
1111

1212
# Site subpath, e.g. /blog
13-
baseurl: ""
13+
baseurl:
1414

1515
# Permalink URLs structure, for permalink style options see: https://jekyllrb.com/docs/permalinks/
1616
permalink: /:categories/:title/
1717

1818
# Site base hostname & protocol, e.g. http://example.com
19-
url: "https://ui-testing.academy"
19+
url:
2020

2121
# Site logo # e.g. logo.png, upload logo image file to /uploads/ folder
2222
logo: logo.svg
@@ -88,23 +88,25 @@ disqus:
8888
google_analytics:
8989

9090
# Pagination Settings
91-
pagination:
92-
enabled: true
93-
per_page: 10
91+
# pagination:
92+
# enabled: true
93+
# per_page: 6
9494
# permalink: '/page/:num/'
9595
# title_suffix: ' - page :num'
9696
# limit: 0
9797
# sort_field: 'date'
9898
# sort_reverse: true
9999

100+
101+
100102
# Path to post content assets directory i.e post images, pdfs etc
101103
uploads: /uploads/
102104

103105
# Build settings
104106
markdown: kramdown
105107
highlighter: rouge
106-
107-
gems:
108+
node_grid: true
109+
plugins:
108110
- jekyll-feed
109111
- jekyll-seo-tag
110112
- jekyll-gist
@@ -123,6 +125,9 @@ collections:
123125
output: false
124126
changelogs:
125127
output: false
128+
articles:
129+
output: true
130+
layout: article
126131

127132
# Defaults
128133
defaults:

_data/android_categories.yml

-85
This file was deleted.

_data/home_categories.yml

-36
This file was deleted.
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: How to send a bug report/improvement proposal/request a topic?
3-
categories: [faq]
3+
categories: [ faq]
44
---
55

66
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/android_categories.html

-38
This file was deleted.

_includes/breadcrumbs.html

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
<ul id="breadcrumbs" class="uk-breadcrumb">
2+
{% assign crumbs = page.url | remove:'/index.html' | split: '/' %}
3+
<li><a href="{{site.baseurl}}/">Home</a></li>
4+
{% for crumb in crumbs offset: 1 %}
5+
{% if forloop.last %}
6+
7+
{% else %}
8+
<li><a
9+
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>
10+
{% endif %}
11+
{% endfor %}
12+
</ul>

0 commit comments

Comments
 (0)