filter_list help_outline
  • Liked Parveen Khan
    keyboard_arrow_down

    Parveen Khan - Exploring a DevOps Transformation Like a Tester

    45 Mins
    Talk
    Beginner

    Just when we, as testers, got a handle on what Agile means for us, the landscape changed yet again to a DevOps culture. Words like continuous integration (CI), continuous deployment (CD), and pipelines are now ones we’re hearing on a daily basis. As a tester, I’ll admit, I had no clue of what these words meant, and how was I to change the way I tested to fit within this DevOps culture.

    Researching DevOps provided some information, but it was still fuzzy how testing fit into this process. As opposed to panicking about yet another shift in culture, I decided to approach this with a tester’s mindset and explore it just as I would a new application.

    In this talk, I’ll share my journey of illustrating models to visualize and understand CI/CD pipelines; my various phases of exploration of the DevOps culture; and the thoughtful questions that I posed at each phase to learn more about this methodology. I’ll also share how my new understanding of DevOps influenced my decisions on which automated tests should be contributed to the CI/CD pipeline and at which stages.

  • Liked Nishi Grover Garg
    keyboard_arrow_down

    Nishi Grover Garg - Layers in Test Automation– Robust Strategy for Separation and Integration

    45 Mins
    Talk
    Beginner

    Often a testing team consists of a mix of subject matter experts, some human-centric and testers with some automation experience. Writing tests in the language of the business allows all stake holders to participate and derive value out of the automation process. If you are a nervous beginner or an expert at test automation, you need to know and understand the layers of test automation and how to separate the code from the test. Let us discuss the best approaches and practices for creation of a robust automation framework with correct separation as well integration of these layers. Learn how to create automated tests that also serve as living documentation and being inclusive of everyone on the team regardless of skill sets. We will also see a demo on how to implement this with a case study.

  • Liked Nishi Grover Garg
    keyboard_arrow_down

    Nishi Grover Garg - The What, When and How of Test Automation

    45 Mins
    Talk
    Beginner

    Agile means pace and agile means change. With frequent time boxed releases and flexible requirements, test automation faces numerous challenges. Haven’t we all asked what to automate and how to go about the daily tasks with the automation cloud looming over our heads. Here we’ll discuss answers to some of these questions and try to outline a number of approaches that agile teams can take in their selection of what to automate, how to go about their automation and whom to involve, and when to schedule these tasks so that the releases are debt free and of best quality.Let us have a look at an integration of these approaches, their possible combinations and which of these combinations may or may not work.

  • Liked Sri Harsha
    keyboard_arrow_down

    Sri Harsha - Memory Leaks: The silent thieves in Web Application

    20 Mins
    Talk
    Beginner

    We’ll love browsing, it may be your blogs, visiting your pages, searching for a content and it may be an application you developed. So, have you ever observed issues like slowness in web-application while browsing, reduce in page performance over time, application quit unexpectedly, and devices stop working? And no wonder every new web technology in this era faces this issue and these applications are victim of memory leaks?

    In a world of automated system, everything is automatically managed under browser hood for a web application. Asynchronous operations, Executing instructions, Automatic garbage collection etc. But even after effective management of operations in a complex program, there is a small amount of failures happens in disposing the memory used and those are difficult to debug because they are not the application features.

    So, it is important for every web developer/tester sitting out there to understand/visualize the importance of memory leaks in an application, Because at the end we’re the one responsible to make the application to be alive

  • No more submissions exist.