🧪 Deploy with Deploy

Author: AlexZhukovich

docs/feed.xml

@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="https://ui-testing.academy/feed.xml" rel="self" type="application/atom+xml" /><link href="https://ui-testing.academy/" rel="alternate" type="text/html" hreflang="en" /><updated>2020-09-20T19:16:53+00:00</updated><id>https://ui-testing.academy/feed.xml</id><title type="html">UI Testing Academy</title><subtitle>UI Testing related content</subtitle><author><name>Alex Zhukovich</name></author><entry><title type="html">Never use sleep in test code</title><link href="https://ui-testing.academy/general/good-practices/never-use-sleep-in-test-code/" rel="alternate" type="text/html" title="Never use sleep in test code" /><published>2020-09-20T00:00:00+00:00</published><updated>2020-09-20T00:00:00+00:00</updated><id>https://ui-testing.academy/general/good-practices/never-use-sleep-in-test-code</id><content type="html" xml:base="https://ui-testing.academy/general/good-practices/never-use-sleep-in-test-code/">&lt;p&gt;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:&lt;/p&gt;
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="https://ui-testing.academy/feed.xml" rel="self" type="application/atom+xml" /><link href="https://ui-testing.academy/" rel="alternate" type="text/html" hreflang="en" /><updated>2020-09-20T20:08:38+00:00</updated><id>https://ui-testing.academy/feed.xml</id><title type="html">UI Testing Academy</title><subtitle>UI Testing related content</subtitle><author><name>Alex Zhukovich</name></author><entry><title type="html">Never use sleep in test code</title><link href="https://ui-testing.academy/general/good-practices/never-use-sleep-in-test-code/" rel="alternate" type="text/html" title="Never use sleep in test code" /><published>2020-09-20T00:00:00+00:00</published><updated>2020-09-20T00:00:00+00:00</updated><id>https://ui-testing.academy/general/good-practices/never-use-sleep-in-test-code</id><content type="html" xml:base="https://ui-testing.academy/general/good-practices/never-use-sleep-in-test-code/">&lt;p&gt;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:&lt;/p&gt;
 &lt;ul&gt;
   &lt;li&gt;interaction with the back-end&lt;/li&gt;
   &lt;li&gt;interaction with the database (especially when we load a lot of data)&lt;/li&gt;