Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit 98aae23

Browse files
Merge pull request #35 from ui-testing-academy/change-structure
Migrated project to nested structure
2 parents e759638 + 1378c43 commit 98aae23

File tree

55 files changed

+362
-626
lines changed

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‎

Lines changed: 1 addition & 0 deletions
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‎

Lines changed: 0 additions & 25 deletions
This file was deleted.

‎Gemfile‎

Lines changed: 6 additions & 7 deletions
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‎

Lines changed: 3 additions & 1 deletion
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‎

Lines changed: 3 additions & 1 deletion
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‎

Lines changed: 3 additions & 1 deletion
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‎

Lines changed: 3 additions & 1 deletion
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‎

Lines changed: 3 additions & 2 deletions
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-
Lines changed: 9 additions & 0 deletions
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+

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /