In my talk, I want to share several approaches that help to improve automation testing in your company.

Do you want to spend less time developing UI automated tests? Maybe you want to reduce boilerplate code in UI tests? Or you think it is time to improve Page Object pattern that has been used for more than 8 years?

My first point will be about how the interface can help us to represent a new vision of Page Object and what benefits we could get from it.

The second - modern methods for coverage measuring are good only for development. However, the amount of useful information from coverage reports is extremely small.

It will a journey about autotest coverage. Imagine, that your project manager asks you - Do we have autotests for these buttons (forms, pages) or what autotests cover these Rest APIs with 'special' query parameters? I will show you two simple solutions that allow you to evaluate the coverage of tests written by test automation specialists.

a) API tests. There is a swagger and during his execution, we also collect a swagger. We count coverage as a diff of two swaggers. We can see what is covered, what is not and what data used.

b) Web tests. During the execution of tests, we collect information about elements, pages, and actions. As a result, we have such a format: page -> elements -> actions -> tests. All information representing in Chrome Plugin, that I will share with you.

And last, I am going to consider what cons have current TMS (QA time management systems) and what to do if you want to make an automation-first strategy on your project? Moreover, you look for one TMS for developers and QAs/or you want to save the Allure report of all autotests in one place?

Here you are! Allure Server has already released. I will overview the most important features and how to start using it from scratch.

If you have an interest in the above themes come to my talk.

 
 

Outline/Structure of the Case Study

Slides (Demo):

1) Title of Presentation

2) How am I (About my experience)

3) Agenda

= 3 Minutes

4) The first point of our journey - describe the issues which we have in UI automation:

5) Duplication of elements. Example of code

6) No parameterization for elements. Example of code

7) Boilerplate code. Example of code

8) How will be represented POM on an interface? - Show example

9) What benefits could we get from using of interface?

10) Parameterization of web elements. Example of Code

11) Multiple Inheritances. Example of Code

12) End of the first part. Describing how you can do this by yourself in other programming languages and where the current realization exists. Show GitHub Link and gits (https://github.com/qameta/atlas).

= 10 Minutes

13) The second point of our journey - describe the issues with code coverage and test coverage.

14) API Coverage - if we have Rest API tests.

15) Swagger (a few words about Swagger), about OpenAPI.

16) How we can make a diff (delta of Rest APIs) of our SUT (system under test) and our autotest?

17) Example of Code (Rest Assured filter) to collect all Rest APIs from our autotests. (https://github.com/viclovsky/swagger-coverage)

18) Swagger Coverage

19) WEB Coverage - What is the main point in web coverage?

20) Considering the approach (Using Graph of pages -> elements). Describing the mechanism of web site map locators.

21) Overview of Chrome Plugin for Web Coverage (https://github.com/kurau/locators-hotspots-chrome-plugin + examples).

22) The third point of our journey - current issues with TMS nowtime.

= 10 Minutes

23) Allure Report - a few words.

24) Allure Server - What is it?

25) The architecture of Allure Server

26) Setup.

27) Automation first strategy with Allure Server.

28) Other cool features.

28) Pros and Cons.

= 10 Minutes

29) Takeaways.

= 2 Minutes

30) QA section.

= 10 Minutes

Learning Outcome

As a result, you will understand what benefits make Page Object based on interfaces and how you can implement it in your custom automation frameworks.

On the other side, you will know:
1) What have your API/UI tests covered and what haven't?
2) How it was covered (just clicked or checked the text).
3) What tests go through the page.
4) Which elements are most commonly used? In general, we should avoid it because it's a potential point of failure.

And last, you will conclude whether to use Allure Server or skip it.

Target Audience

AutoQA/QA Test Engineers, Project Managers, Technical Leads, Test Managers

Prerequisites for Attendees

One year of experience in the automation testing area.

schedule Submitted 3 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Pallavi ...
    By Pallavi ...  ~  2 months ago
    reply Reply

    Hello Artem

    So there are three segments in this talk -

    a.Web UI Management

    b. API Coverage using Swagger

    c. Reporting using Allure

    If i have captured this right, can you please segment the proposal abstract, talk structure and learning outcome segment wise and add more detail for it. 

    Also, accordingly can you edit the title for your presentation. 

    The code if any which you would be showcasing to audience will it be available in github for them to use/practice later?

    Thanks

    Pallavi

    • Artem Sokovets
      By Artem Sokovets  ~  2 months ago
      reply Reply

      Hello Pallavi,

      If i have captured this right, can you please segment the proposal abstract, talk structure and learning outcome segment wise and add more detail for it.  >> Done

      Also, accordingly can you edit the title for your presentation.  >> Done. Renamed it.

      The code if any which you would be showcasing to audience will it be available in github for them to use/practice later? >> Yep. All examples of code and projects will be on GitHub.

      Thanks!

      Rgs,

      Artem

      • Pallavi ...
        By Pallavi ...  ~  3 weeks ago
        reply Reply

        Thanks Artem

        • Artem Sokovets
          By Artem Sokovets  ~  3 weeks ago
          reply Reply

          Hi Pallavi, Can you give me feedback about my talk proposal? I din't get any response from you. Rgs, Artem.

          • Deepti Tomar
            By Deepti Tomar  ~  3 weeks ago
            reply Reply

            Hello Artem! Our Program Committee will revert shortly on this.

             

  • Robin Gupta
    By Robin Gupta  ~  3 months ago
    reply Reply

    Can you please add the below aspects to the presentation in addition to Pallavi's observations?

     1. A general outline/structure/time division of the presentation
     2. While the current content fairly describes the problem statement/solution, adding technical details such as architectural diagrams, code snippets or github repo can help the audience with implementation of the framework.
     3. Challenges/Work arounds of the approach followed here
     4. Scalability aspects, Open source alternatives (if any), content for Non-Java programmers

    5. Exact problem statement and solution set for conveying the content in a simple fashion for the audience.

    • Artem Sokovets
      By Artem Sokovets  ~  2 months ago
      reply Reply

      Hello Robin,

      1. I fixed the structure. Yep, it not finished, but in general how I see.

      2. Yep, I will have some diagrams. And code will be available on GitHub repos or Github gists. Or I need to publish it earlier? 

      3. In the first and second parts, I will consider other ways how attenders can achieve it.

      4. Yep. The same as the third answer.

      5. I have changed the title and proposal abstract.  Overviewing problems and solutions that can get attendees. 


  • Liked Shweta Sharma
    keyboard_arrow_down

    Shweta Sharma / Nikita Jain - Accessibility testing 101

    45 Mins
    Talk
    Beginner

    "This world is such a beautiful place to live in." If you can read the first sentence without any screen readers or assistance, you're privileged. As technologists, shouldn’t we be more empathetic towards differently-abled people and make all parts of our website accessible to them? In my humble opinion, the true power of technology can be identified when it reaches out to people of all kinds having different physical or psychological challenges. We not only legally bound to provide Accessibility but also it should be considered as our moral responsibility.

    As testers, we have a wonderful opportunity to contribute to Accessibility by ensuring that the site is accessible in many different ways. Although it is impossible to identify all the issues that exist around Accessibility in the world, we are lucky enough to still understand a majority of them. With this understanding, there have been many measures taken in order to make your site accessible. But, don’t forget - we are QA engineers. We got to ensure that the site is accessible as per the standards set by WCAG 2.0 (AA) by testing for accessibility using various tools and techniques.

  • Liked Ivan Krutov
    keyboard_arrow_down

    Ivan Krutov - Workshop: Efficient Selenium Infrastructure with Selenoid

    Ivan Krutov
    Ivan Krutov
    Developer
    Aerokube
    schedule 4 months ago
    Sold Out!
    480 Mins
    Workshop
    Intermediate

    Selenoid is an alternative lightning fast open-source Selenium protocol implementation running browsers and Android emulators inside Docker containers. It is distributed with a set of ready-to-use Docker images corresponding to the majority of popular browser versions, has a one-command installation utility and works slightly more efficiently than traditional Selenium Grid.

    This tutorial shows how to build efficient and scalable browser automation infrastructure using Selenoid and related tools. You will be taught why running browsers in containers is so efficient, how to easily install Selenoid and use its powerful features.

  • Liked Srinivasu gangam
    keyboard_arrow_down

    Srinivasu gangam - Zero Touch Automation using NLP (Natural language processing) & AI

    Srinivasu gangam
    Srinivasu gangam
    Sr Manager
    Cotiviti India
    schedule 5 months ago
    Sold Out!
    45 Mins
    Demonstration
    Intermediate

    Problem Statement:

    As part of SDLC process:

    1. Is your product quality impacted due to a smaller number of QA resources available in the team?
    2. Are you waiting for QA resources to certify your code every time when you deploy? Is this impacting your product lead time (Speed to Market)?
    3. Is your Product delivery timelines are impacted due to last minute defects identified?
    4. Do you have your QA resources only in one location, but you want to “follow-the-sun” approach for Software delivery across multiple locations?
    5. Do you have manual testers who are not skilled in programming, but you want them to execute automated test scripts w/o any training efforts and automation setup?
    6. Would you like your team more agile and cross functional with Delivery?
    7. Would you like to increase your QA team’s productivity while they invest more time in script development rather than script execution?

    If answer is ‘Yes’ for above questions, "Zero touch automation" is the solution for above challenges that we have been facing part of SDLC.

    Solution: Zero touch automation with cutting-edge technologies

    In this session, I will cover how we solved this problem using innovative solutions, Cutting-edge technologies like NLP (Natural language processing), AI & Cloud solutions.

    You will learn how AI, NLP integrated with core automation components to achieve Zero touch automation.

    This solution is not just revolutionary, it is paradigm shift in test automation to get results to your email with detailed analysis of failure categorization with recommended actions to users.

    I will also cover how E2E automation will be driven with decisions taken by machines based on what user is looking for . There is no manual intervention in this process. NLP and AI play key role to help machines to take decisions.

    We will also cover how we empowered developer/release manager/any team member/Manager to trigger the scripts from their cell phone and get the detailed execution report without having any automation software installed in their computer or Phone.

    We will be demonstrating how the request will be initiated from User, understand the need from user using NLP & AI , Fetching the code from bitbucket to select appropriate automation scripts , running them on Selenoid/docker server , storing results to MongoDB , receiving email with test results and Failure analysis.

    What is the value of zero touch automation?

    1. Enable speed to market: Now that Developers does not need to wait for QA resource, Changes can be certified quickly and ready to push to production. Lead time will be significantly reduced.
    2. Increase quality: Now that test automation is easy and it can run multiple times in each environment, most of the defects will be uncovered and addressed before code goes to production.
    3. Ease of test execution: Test execution will be very easy, no automation or framework setup required from user side. Test execution can be done 24*7.
    4. Productivity: Increase QA team’s Productivity to focus more on script development rather than focusing on script execution and failure analysis .
  • Liked Sameer Arora
    keyboard_arrow_down

    Sameer Arora - Triggering alerts on Slack along with screenshots in case of test case failure

    Sameer Arora
    Sameer Arora
    Senior Software Test Engineer
    Gaana
    schedule 5 months ago
    Sold Out!
    45 Mins
    Demonstration
    Beginner

    One of the biggest limitations with most of the frameworks in selenium is that we need to wait till the end to get the final test case report. Only then we can raise the alert that a particular functionality is broken. By then, it may be too late! In addition to this, in most of the frameworks, the HTML report generated is hosted on our company's private network and we need to connect to the VPN if we are outside the office to open the report and check the related screenshots to see which test case has failed and why.

    So, why not raise an alert as soon as the test case fails? And why not attach a screenshot along with that alert so that all the stakeholders can actually see what has failed in the application?

    In this session, we will learn a simple yet a really useful way of sending an alert along with the failed test case screenshot by integrating slack with selenium which will help us alert all the stakeholders as soon as an automated test case fails so that everyone can react to it immediately and the damage will be minimised.

  • Liked Prateek Sethi
    keyboard_arrow_down

    Prateek Sethi - Enhance Test Automation ROI with Docker based Selenium Environment

    Prateek Sethi
    Prateek Sethi
    QA Lead
    3PillarGlobal
    schedule 3 months ago
    Sold Out!
    90 Mins
    Workshop
    Intermediate

    Quick Description :

    To support the continuously evolving software industry, DevOps and Agile practices have established themselves as a big helping hand. With ever-increasing large scale digital transformation projects, organizations realize that the only way to shorten the product development cycles is to automate the processes involved in the delivery pipeline.

    There are many tools and technologies to establish DevOps, but one of the most important ones is containerization, which gives flexibility in application packaging and automating a number of processes involved in the delivery pipeline. Containers have all the needed configurations and dependencies, for faster delivery of committed items to the customer. Docker is an open-source solution that makes it easier to create, deploy and run applications securely using containers. Therefore, quick feedback and testing applications with different environments can be achieved using Selenium with Docker.

    My Proposal :

    We can reduce the significant effort in provisioning, maintaining, running the Test Automation on different environment setup using, Docker with Test Automation. Some of the benefits are:

    Benefits of using Docker with Selenium:

    1. Test an application on multiple browsers and their different versions without installing them on multiple machines
    2. To test multiple application builds concurrently without updating the code for different environments
    3. To test your applications on multiple devices/OS/Browser combinations on a single machine.As Selenium within Docker will make it much quicker to test different environments by using the preconfigured containers.
    4. Also, I will cover topics like how to set up the Selenium multi-environment setup using Docker concepts like Compose file, etc.

    Best practices using Selenium with Docker

    1. Common Dos and Don'ts for this setup.
    2. How to avoid over maintenance of your Test Harness.
    3. Infrastructure setup

    Increase the power of your Test Automation Setup with Kubernates:

    How to handle Selenium grid-based dockerize nodes with Kubernates.

  • Liked Khanh Do
    keyboard_arrow_down

    Khanh Do - Leveraging Artificial Intelligence to create self-healing tests

    Khanh Do
    Khanh Do
    QA Architect
    Kobiton
    schedule 5 months ago
    Sold Out!
    45 Mins
    Tutorial
    Intermediate

    A key requirement for successful test automation is to get past the brittle or fragile nature of test scripts. Any Selenium (or Appium) developer has encountered the dreaded "NoSuchElement Exception". A locator that worked yesterday may fail today. What's a test engineer to do?

    Fortunately the field of AI provides promising solutions and allows for the creation of self-healing tests. Tests that can find elements across all environments. Tests that can learn from "human-in-the-loop" intervention and work perfectly thereafter. Imagine automated tests that "just work"!

    This session will look at how to apply the latest in AI and Machine Learning technologies to improve your test scripts. With the plethora of new open source AI libraries made available by companies such as Google, the ability to leverage AI in your applications is more accessible than ever.

    This session will be a primer on AI technologies and how they can be utilized for perfect test automation.

  • Liked Nishil Patel
    keyboard_arrow_down

    Nishil Patel - Tesbo : An Awesome Test Automation Framework with Plain English Text But not BDD

    Nishil Patel
    Nishil Patel
    Founder
    QAble
    schedule 4 months ago
    Sold Out!
    45 Mins
    Demonstration
    Beginner

    Tesbo is a hybrid Test Framework built top on the Selenium which allows you to use the plain English language to define the test which helps you to reduce the development and maintenance time and efforts. sounds similar to the BDD framework (i.e. Cucumber, Specflow, Gauge, etc...) ??? But No It Isn't... It's much better than Cucumber.

    In this session, we will look into why we have developed Tesbo and how it will reduce the development and maintenance times of web and mobile test script.

    This session will focus on the

    • Introduction of Tesbo
    • Advantages of Tesbo
    • Feature description
    • Test Development and Execution demo
    • Future plans for Tesbo