<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Oleksandr Romanov on Medium]]></title>
        <description><![CDATA[Stories by Oleksandr Romanov on Medium]]></description>
        <link>https://medium.com/@al8xr?source=rss-3c7d81fe980e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Jt08U1yz3U8U6vokO3cw4g.jpeg</url>
            <title>Stories by Oleksandr Romanov on Medium</title>
            <link>https://medium.com/@al8xr?source=rss-3c7d81fe980e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:37:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@al8xr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How do we learn over time?]]></title>
            <link>https://medium.com/@al8xr/how-do-we-learn-over-time-e3f7a981af37?source=rss-3c7d81fe980e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3f7a981af37</guid>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Oleksandr Romanov]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 10:25:57 GMT</pubDate>
            <atom:updated>2025-06-27T10:25:57.317Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, I want to share with you an obvious yet insightful concept: how our learning evolves with our experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ss4HwFuqaG83kda6" /></figure><p>Let’s look at that graph. The red line represents the speed of learning, while the blue line illustrates the amount of new information we receive.</p><p>The graph shows that when we just start to learn a new skill or specialization (like testing), we are learning at a slower pace. But at the same time, the amount of new information we encounter is huge!</p><p>As time passes, we gain experience, and the rate of learning slows down. The filter for new information becomes smaller. When we start a new course or a new book, we quickly realize that out of 300 pages, we get only 10–20 pages with new and insightful knowledge. The rest of the book we have already seen before (maybe even multiple times).</p><p>❓ What’s the point?</p><p>✍ When you are a beginner, it is normal to learn at a slow pace when you have just started.</p><p>✍ However, when you are an experienced person in a certain topic, it is also completely normal to skip the content and concentrate only on the knowledge that is new to you. Also, you’ll need to spend more time finding connections between the knowledge you already have and the new one. That’s where the insights lie.</p><p>🕶️ P.S. That might be a reason why some people can read many professional books per year.</p><p>🕶️ P.P.S. I am talking here about an actual reading by yourself, not just reading an AI-generated excerpt from a book.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3f7a981af37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where to practice in SQL?]]></title>
            <link>https://medium.com/@al8xr/where-to-train-in-sql-36951d020bcf?source=rss-3c7d81fe980e------2</link>
            <guid isPermaLink="false">https://medium.com/p/36951d020bcf</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[sql]]></category>
            <dc:creator><![CDATA[Oleksandr Romanov]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 10:24:52 GMT</pubDate>
            <atom:updated>2025-06-27T11:22:16.130Z</atom:updated>
            <content:encoded><![CDATA[<p>Should a (test) engineer know SQL? It depends on the specific project’s needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ls3U3Nq1ci-iQpog" /><figcaption>Image is AI-generated from Chat GPT</figcaption></figure><p>But if you want to practice SQL skills, here is the list of resources to do it in a fun way:</p><p>👉 SQL Noir (<a href="https://www.sqlnoir.com/">https://www.sqlnoir.com/</a>) — 6 cases for a “real” detective<br>👉 SQL Murder Mystery (<a href="https://lnkd.in/ePmcFvA6">https://lnkd.in/ePmcFvA6</a>) — solve a “murder case” by searching the database<br>👉 SQL PD (<a href="https://sqlpd.com/">https://sqlpd.com/</a>) — join a police department to find a criminal … with SQL<br>👉 SQL Island (<a href="https://lnkd.in/eWKJTie8">https://lnkd.in/eWKJTie8</a>) — a set of exercises for beginners<br>👉 SQL Zoo (<a href="https://lnkd.in/eWPZk3R4">https://lnkd.in/eWPZk3R4</a>) — standard cases for practice<br>👉 HackerRank SQL (<a href="https://lnkd.in/eBd8aMqc">https://lnkd.in/eBd8aMqc</a>) — a set of questions with automatic evaluation<br>👉 SQL Game by DataLemur (<a href="https://lnkd.in/ePYur8TG">https://lnkd.in/ePYur8TG</a>) — play a Squid Game … with SQL<br>👉 SQL Interview Questions (<a href="https://lnkd.in/eKVmVCHG">https://lnkd.in/eKVmVCHG</a>) — a set of real-world interview questions<br>👉 Advent of SQL (<a href="https://adventofsql.com/">https://adventofsql.com/</a>) — open an advent calendar of SQL exercises — one at a time<br>👉 Database questions at Leetcode (<a href="https://lnkd.in/eDt7yUGE">https://lnkd.in/eDt7yUGE</a>) — serious problem sets</p><p>What are you using to practice SQL?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36951d020bcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why do we fail at interviews?]]></title>
            <link>https://medium.com/@al8xr/why-do-we-fail-at-interviews-9aa7ab92e63e?source=rss-3c7d81fe980e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9aa7ab92e63e</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[Oleksandr Romanov]]></dc:creator>
            <pubDate>Thu, 27 Mar 2025 13:23:19 GMT</pubDate>
            <atom:updated>2025-03-27T13:24:07.590Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Disclaimer: Yes, I know every company has a unique interview process, but let’s talk about averages.</strong></p><p>No matter how many years of experience you have — it is always hard to pass interviews. Why?</p><p>I have been thinking about this question for a while now. I worked as an external technical interviewer and also helped testers prepare for interviews. In this blog post, I wanted to share my view on this problem and a possible steps we can do to make interviews less painful.</p><h3>Knowledge: yours and theirs</h3><p>Every person has a unique knowledge, background, and experience. It can be big or small. The more you work in an industry — the wider this circle of knowledge becomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g9MaYxq7nPfkkA2J.png" /></figure><p>It includes a set of fundamental knowledge of computer science, testing principles, approaches, and tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/0*_NXMx2JUwW7Eo1-Z.png" /></figure><p>It also includes domain knowledge from past projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/0*wnUYNtSOcsRI8AWZ.png" /></figure><blockquote><em>But we do not use all of our knowledge daily at work. At any given moment, we use only a subset of it.</em></blockquote><p>For example, we pull-push from the git repository, use a few terminal commands to run some tests, and use a few clicks here and there to understand logs or monitor results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/0*fr029jf5EI46VTnS.png" /></figure><p>So, you get to an interview. The company (or a given project) has its requirements for a position. Requirements may be adequate. But requirements also may include all possible “may be’s” that the manager plan to have in a years from now. (<em>The candidate need to have testing, automation, coding, performance, security, usability, management, devops skills…</em>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/0*VX1AmFAGIwRy2mOl.png" /></figure><p>An interviewer (a technical or a manager) may or may not have knowledge that covers all these requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/0*2XM0EBpkAd9PlQcU.png" /></figure><p>However, to pass an interview, you and your interviewer also need to have a <strong>special kind of knowledge of how to do a job interview</strong>. It includes special knowledge like STAR methodology, fundamental knowledge (like algorithms, data structures, etc.), system design, and behavioral questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/0*Bim-xaO3SO9W0rgn.png" /></figure><h3>So why is it hard to pass an interview?</h3><blockquote><em>The main reason we generally fail at interviews without preparation is that our knowledge for interviews has very little overlap with what we use at work (in most cases).</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bl_m83D570YDi16a.png" /></figure><blockquote><em>Passing interviews is an entirely different set of skills that may not show how you actually work.</em></blockquote><p>An interviewer uses interview knowledge to find an overlap between the position requirements and the candidate’s experience and expertise. An additional challenge is to see this overlap in an hour or so.</p><h3>What can we do about it?</h3><p><strong>Our main goal as a candidate is to get interviewing skills and to show this match for requirements as clearly and fast as possible.</strong> We can get those skills by preparation or trial and failure at multiple interviews.</p><ul><li>The more experience in the interviews you have, the better you will be at it. (But only if you carefully reflect after each failure)</li><li>Request feedback after an interview. Write down your impressions and questions you missed answering just after the interview ends. Learn the missing parts and practice them.</li><li>Think about your experience and how it matches the requirements. Prepare clear examples that highlight your strengths.</li><li>Be honest if you do not know something. (It is not possible to know everything). Admit it, but think about where you possibly can get missing information and try to find similar cases from your own experience.</li></ul><p><strong>Remember:</strong> each time we go to an interview, the requirements and the interviewer’s background also change. Your task is to mix fundamental knowledge, current knowledge, and experience from past projects, add a drip of interviewing skills on top, and show the value you can bring to a company as a specialist.</p><p>You may find that it is not possible to find an overlap — that’s totally okay. Requirements may not be adequate. The interviewer may lack the skills to conduct an interview (and desire to prove that you do not deserve a job). The job may not fit your needs.</p><blockquote><strong><em>Do not forget:</em></strong><em> there are many companies on the market. There is always another company that will help you to succeed</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9aa7ab92e63e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On test engineer’s maturity]]></title>
            <link>https://medium.com/@al8xr/on-test-engineers-maturity-dfe9bfa90a3a?source=rss-3c7d81fe980e------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfe9bfa90a3a</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Oleksandr Romanov]]></dc:creator>
            <pubDate>Tue, 20 Dec 2022 12:42:13 GMT</pubDate>
            <atom:updated>2022-12-20T12:42:13.743Z</atom:updated>
            <content:encoded><![CDATA[<h3>Questions</h3><p>From time to time, similar questions arise in various tester chats and forums:</p><ul><li>Do I know enough as a junior or trainee?</li><li>What should the middle engineer know?</li><li>When to understand that you are a senior?</li><li>How to get the position of lead or manager?</li></ul><p>I have also asked myself and other people such questions. But unfortunately, he still needs to receive comprehensive answers.<br>After all, there is no single correct answer to such questions. Everything depends on the context: you, the company, and the market.</p><h3>Test Engineer Maturity</h3><p>Instead of looking for complex answers, I suggest paying attention to what questions we ask ourselves at each stage of our career development. Each company has its own stages of career development, but I see the following: Junior =&gt; Middle =&gt; Senior =&gt; Lead =&gt; Manager =&gt; Consultant =&gt; “Guru”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*P6jhZPlhaJwQdxFo0osKxw.png" /></figure><h3>Junior</h3><ul><li>How to test this feature or application?</li><li>Which test design technique is best?</li><li>What is Git, and why is it needed?</li><li>Which programming language to choose for automation (to get a bigger salary)?</li><li>What is the best testing tool?</li></ul><h3>Middle</h3><ul><li>How to properly configure the CICD pipeline?</li><li>How to fix all flaky tests?</li><li>What are design patterns, and how to apply them?</li><li>Why do we need to write clean code and follow coding conventions?</li><li>How to run tests in multiple threads somewhere on Selenoid?</li></ul><h3>Senior</h3><ul><li>How to improve the testability of a particular feature or service?</li><li>What are the problems with the system architecture? What will happen if “this individual component” on the diagram stops working correctly?</li><li>How much business value do self-tests bring?</li><li>How to encourage the entire team, from developers to managers, to use test results?</li><li>Which tests are better to do manually rather than spend time on automation?</li><li>How quickly and safely does this or that component work? But how does one component’s bad performance affect the system’s performance as a whole?</li></ul><h3>Lead</h3><ul><li>How to properly organize testing processes in a team?</li><li>How to ensure that the team achieves business goals?</li><li>How to create a culture of shared responsibility for quality in the team?</li><li>How to collect metrics, work with priorities, and communicate with different teams?</li></ul><h3>Manager</h3><ul><li>How does testing help minimize business risks?</li><li>How to motivate test engineers to grow and develop?</li><li>How to create the testing vision for the company?</li><li>How to set up processes and engineering culture at the company level?</li><li>How to communicate test results to senior management (in their language)?</li></ul><h3>Consultant</h3><ul><li>How to create a better testing strategy for a specific company in a particular context?</li><li>How to convince the client that this tool or approach is better?</li><li>How to quickly make a Proof-of-Concept of an automation solution and get feedback?</li><li>How do you train engineers or managers on a chosen concept, approach, or tool?</li></ul><h3>“Guru”</h3><ul><li>Why do we test?</li><li>How does testing differ from verification?</li><li>How can we tell if our expected results are correct?</li><li>How do we know what we know?</li><li>How do we learn?</li><li>Are there universal approaches and heuristics for testing?</li><li>How to measure or change people’s perception of quality?</li></ul><h3>Conclusions</h3><p>Of course, if you are at the same stage, no one forbids you to ask any other questions from different levels.</p><p>But the effectiveness of your work and the answers to questions will depend on your skill level and the scope of work.</p><h3>And what questions do YOU ask yourself on the project?</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfe9bfa90a3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On choosing and changing languages for test automation]]></title>
            <link>https://medium.com/@al8xr/on-choosing-and-changing-languages-for-test-automation-527a6b66859c?source=rss-3c7d81fe980e------2</link>
            <guid isPermaLink="false">https://medium.com/p/527a6b66859c</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[test-automation]]></category>
            <dc:creator><![CDATA[Oleksandr Romanov]]></dc:creator>
            <pubDate>Fri, 16 Dec 2022 11:07:04 GMT</pubDate>
            <atom:updated>2022-12-16T11:07:04.192Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>You are at the beginning of your testing career…</strong> You see that in many job descriptions, they ask about test automation skills. Or you heard that by working in automation, you could earn more money (which depends). <strong>Which programming language to choose? Which language and tech stack is best of the best? Is there a single choice for it?</strong></p><p>It can happen to anybody. You can be frustrated in your current job. You can feel that you are doing the simple things, and your progression is stopped. You also desire more salary or more significant responsibilities. So the call or message notification on Linkedin about a <strong>new and fancy job opportunity is coming</strong> just in time. <strong>But the issue here is that this new job is in a completely different tech stack or programming language. What can you do with it?</strong></p><p>Today I want to share my thoughts on choosing the first programming language. Also — we will think together whether it is worth changing between language and tech stack — and how to make such a process beneficial for you and your manager.</p><h3>My story</h3><p>I had various jobs and titles in my 10+ years of IT industry journey. I was a Test Automation Specialist, a QA &amp; Testing Analyst, an SDET, a QA Automation Engineer, and even a Software Engineer.</p><p>It<strong> is not about how fancy is your position’s name.</strong> <strong>It is all about your responsibilities and your influence on the team</strong> or department level.</p><p>Over the years, I’ve changed automation languages ​​several times:</p><ul><li>at my first job, I wrote UI autotests in C# + Specflow;</li><li>then — wrote API tests on Groovy DSL (SoapUI) and simply on “pure” Java;</li><li>then it was the Ui web test automation with C# again;</li><li>then it was a big project, and tests on Scala.</li><li>Then it was Java, Spring Boot, and a software engineering job.</li><li>Right now, I am writing my tests and tools mainly in Scala.</li></ul><h3>Questions to consider before choosing a language</h3><p>Before choosing the programming language for automation, you need to ask yourself a set of questions.</p><h4>Project-related:</h4><ul><li>Technological stack and architecture.</li><li>Testing processes. Are there testing processes on the project? How do you plan to use automation testing? Who will be responsible for such tests — testers, developers, or a separate team of engineers?</li><li>Test automation strategy. Is there an ultimate goal of automation? What types of automation tests do you plan to write? When will such tests be executed? How do you use the test reports?</li><li>Programming and automation experience. Do you have programming experience? Did you write automation tests at all?</li></ul><h4>Language-related:</h4><ul><li>How many vacancies are currently on the market for this language</li><li>How deeply do you plan to learn this language? What is your technical background?</li><li>Is the language and the infrastructure around it mature enough? Do stable frameworks and tools exist that will allow you to write the necessary solutions quickly?</li><li>How do you plan to improve your career by learning a language?</li></ul><h3>On environment</h3><p>Your work environment matters. Depending on the team, its skills, and you personally — the choices for language can be different. Let me show you a few cases and possible solutions for automation.</p><h4>One tester. A small team. No prior automation experience.</h4><p>Options:</p><ul><li>Invite a short-term automation consultant. They will help develop an automation strategy and initial Proof-of-Concept for automation tests.</li><li>Choose the same programming language for automation that the developers in your team use. They will be able to advise and help you with the tests. The downside of this approach is that developers can write complex programming languages ​​that are not very efficient for writing simple end-to-end tests. (Or course, you also can write Selenium tests in Haskell.)</li><li>Find a mentor (inside your company or elsewhere) to help and guide you in learning automation.</li></ul><h4>One tester. A small team. Some automation experience</h4><p>Options:</p><ul><li>Choose the language you know best. Also, consider how many automation tools and libraries exist for the language. It may happen that many tools will have to be written: “from scratch.”</li><li>Alternatively, you can choose the language and stack identical to what the developers use. Learning a new programming language to create several UI autotests is relatively easy (if you already have some background).</li></ul><h4>A team of testers. No automation experience. You’re the lead</h4><p>Options:</p><ul><li>Select an individual tester from the team and train him or her in test automation.</li><li>Hire a dedicated automation engineer who will later train all testers in automation.</li><li>Train developers to implement automation tests by themselves. (Difficulty level: HARD).</li></ul><h3>On choosing languages</h3><p>There are many programming languages. Some languages are harder to learn. But such languages can give a boost to writing tools.</p><ul><li>If you like the world of front-end — then your choice is <strong>Javascript or Typescript</strong> and its army of frameworks. This world of tools and libraries is a very dynamic one. You will always have a job!</li><li>If you’re more into network stuff, hacking, data science, or other back-end stuff (or just like simple and friendly code) — look towards <strong>Python</strong>.</li><li>For those who want enterprise-level stability, consider <strong>Java</strong> or <strong>C#</strong>.</li><li>Those who want to work with blockchain — can learn smart-contract languages like <strong>Solidity</strong>, <strong>Plutus</strong>, and other platform-specific ones. You need to learn <strong>Haskell</strong>, <strong>Rust</strong>, and <strong>C++</strong> for more low-level things in the blockchain world.</li></ul><h4>About new languages</h4><p>If you choose a programming language that is new or not mainstream, then be prepared to learn it deeply and then look for a job for a longer time. As a side effect, the salaries may be slightly higher. But it may NOT be.</p><p>Additionally, if the language is new, you will need to write a lot of the functionality of the frameworks of other languages ​​by yourself. On the one hand, it’s an opportunity to improve your technical skills. On the other hand, it requires time and effort (which may not be available to you).</p><h4>On changing languages and tech stacks</h4><ul><li><strong>If you are a Junior or Middle automation engineer.</strong> Changing the programming language and stacks at this level is relatively simple. If the new project has an established framework and/or senior engineer to mentor you — you can switch without fear. You will need to learn a lot — but a good mentor can make this learning process as quick and painless as possible.</li><li><strong>If you are a Senior engineer.</strong> If you join the new company as the first engineer in the team, you will need time to learn new things and write proofs-of-concept that might only work on the first try. On the other hand — if you join a well-established team, your onboarding process will be more straightforward.</li><li><strong>Switching between statically typed languages</strong> ​​(Java, C#, and C-like languages ​​in general) is quite simple. It will be a little more challenging to transition from statically typed to dynamically typed languages, such as JS, Python, Groovy, Ruby, etc. (or vice versa). Plan more time for learning new concepts.</li><li><strong>Few words about functional programming languages</strong> ​​(Scala, Closure, Haskell, and others). It is possible to write in OOP style on some of them (particularly Scala). For tests, it will be enough. But functional programming will still need to be mastered to get the most out of the language. And it takes even more time than the languages ​​from the previous point. Plus, you can only write in a functional style in languages like Haskell or Closure.</li><li><strong>About working at FAANG and other western startups.</strong> They all hire engineers who can master one or another language in a short period (not instantly, of course) and write production or test code with it. But do not worry. In most cases, such companies will have a lot of experienced engineers who will help with code reviews and feedback. So what matters here — is your basic technical knowledge and problem-solving experience. Programming language — is only one thing among your tools.</li></ul><h3>On skills</h3><p><strong>Programming language is only a tiny part of what a test engineer or SDET should be able to do in automated testing.</strong></p><p>In addition to the language, there are also basic approaches to testing and automation. There is the technical knowledge of various systems’ architecture and how to test them.</p><p>There are many additional tools for writing and running tests — build tools, automation frameworks, various libraries for logging, parallel runs, reporting, and CICD tools. And also — design patterns and the ability to write clean and understandable code.</p><p><strong>Most of the automation skills do not depend on the programming language.</strong> You can find analogs for most of the tools in the selected technology stack. If such tools do not exist in the chosen technology, why not build it yourself?</p><p><strong>The main job of an engineer is to solve a business problem most efficiently. Effectiveness here lies primarily in how fast, scalable, and understandable the tool or approach is to other engineers and managers.</strong></p><h3>Conclusion</h3><p>Choosing a programming language for automation — is a tricky thing. Especially if you are a single tester in a small team, each language has its pros and cons. Each language brings an ecosystem with it. But <strong>asking good questions BEFORE making such a choice</strong> — <strong>can decrease the amount of “headache”</strong> in the future.</p><p>Changing languages and stacks later in your career also have its own implications. You can be a <strong>generalist</strong> and scratch the surface of many languages. Or you can be a <strong>specialist</strong> in one language — but do technically complex things and optimizations. <strong>It’s up to you to decide which engineer you wanna be.</strong></p><p>In the end, I want to state a few general things that you should never forget when you work with test automation:</p><ul><li><strong>A few stable and fast tests are better than a “super framework.”</strong> If you plan to create only a Smoke suite from a pair of end-to-end tests “for every day, “ you can do it with almost any tool. Just make sure that the tests are fast and stable. Such tests will bring benefits to the whole team.</li><li><strong>Automation can take many forms.</strong> It can be a UI or API test for the most critical features, deployment scripts, or database migration. A small script that automates daily routine tasks can bring more value to the team than many simple UI tests.</li><li><strong>Automation strategy is the first step.</strong> If you plan to create automation tests at different levels, think about test coverage, launch on various platforms, then first create and communicate the automation strategy to management. Without a clear understanding of the “end” point, you will not be able to tell whether you are moving in the right direction.</li><li><strong>Learn programming and the technology stack.</strong> Writing a large project for automation requires the same knowledge and programming skills as writing feature code. Therefore, constantly improve your level of expertise.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=527a6b66859c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>