This talk will cover the key aspects and tips of how we can adopt CI/CD in our testing. For those who are yearning to learn on approaching CI/CD to their QA process this talk would give a glimpse of all the main testing types and how we can build a strong QA process and keep in part of your CI/CD pipeline. I would be giving out some tips and tricks on what approaches can be taken to add not just your functional tests (with Selenium) part of your pipeline but also have performance testing, API testing and security testing also part of your CI/CD pipeline so that the system goes through a full stack testing before it gets out there. The talk will also cover a few quick demos which would help the viewers then to work upon further.


Outline/Structure of the Talk

The structure of the session would be the introduction of the CI/CD pipeline and then feature on certain key testing aspects., which will comprise of short quick demos on how we overcame those in my QA Team.

The following is the rough structure of the session.

  • Introduction to Continuous Integration, Continuous Delivery, Continuous Deployment and Continuous Testing (10mins approx)
  • Importance of incorporating Full Stack Quality Engineering to your Continuous Testing. (10mins)
  • Aspects or main features to be part of continuous testing - the importance of incorporating those to the continuous testing pipeline (each 2-3mins)
  • Demonstration on how we can accomplish the above mentioned aspects., just so that beginners can get an idea (would not have to cover all but a few as I would run out of time) (4 demos each varying from 2-4mins)
  • Finally what the audience should take back (2mins)
  • Questions (5mins)

Learning Outcome

Many people in the testing world are yearning to learn and move in CI/CD. This talk with quick demos will help the audience to get an essence on what they can focus on as testers and invest there testing skills to the CI/CD pipeline of their project. This talk would help the audience to kick start to Test Quality with CI/CD or in other words move to Continuous Testing.

Target Audience

QA Engineers or Testers who are moving into Continuous Integration or for those who have just started to work with CI/CD

Prerequisites for Attendees

The attendees need to understand important aspects of Testing as I will be showing how it can be handled in your CI/CD pipeline

schedule Submitted 3 years ago

Public Feedback

    • Diego Molina

      Diego Molina - The Holy Trinity of UI Testing

      Diego Molina
      Diego Molina
      Sr. Software Engineer
      Sauce Labs
      schedule 3 years ago
      Sold Out!
      45 Mins

      Sometimes it is hard to know what to test in a web application, and the first step before testing is defining what we want to test. This may sound trivial, but in reality this is often not done properly. We tend to oversee the obvious and we test without knowing what we want to accomplish.

      What do we want to achieve? Validate user behaviour? Check if the page design is responsive on different devices? Or maybe to know that our web application looks like we expect.

      When we know the purpose of our test, we can start planning, coding, executing and improving our tests. But most importantly, we will know what approach we can use to develop the test.

      Functional, layout and visual testing are the three pillars of the UI testing trinity. We can use these approaches to develop focused tests, tests that are asserting a specific aspect of our web application.

      But how can we identify what approach to use? When should we combine them? There is an information overflow that presents a huge variety of tools that can help us to test through any of these approaches. Sadly, this large amount of information is making us focus more on the tools instead of focusing on the testing strategy.

      The intention of this talk is to break in pieces the process of identifying how to develop a focused test, and more importantly, to understand when it makes sense to combine functional testing with layout or visual testing, and what to consider before using layout or visual testing.

      The talk will then go deeper through scenarios and code examples that show how to create layout and visual tests. It will also discuss scenarios where a functional test is not enough, or where a visual test is better than a layout test. This talk’s main goal is to offer a different perspective when testing a web application through the UI testing trinity.

      If you are interested in how to integrate layout or visual testing to your current workflow, you should attend this talk!

      Note: Thanks to the feedback I got after presenting this topic at SauceCon 2018, I have been able to make nice improvements to the content that will be helpful for the attendants.