location_city Online schedule Sep 24th 12:00 - 12:45 PM IST place Zoom people 14 Interested

What if the testing scope changed from usual UI or API testing? Instead, the testing scope gets diverted to the testing of docker artifacts like base images (let's say python, node) used in the Dev or QA community. What can be the overall possible quality gates for this ecosystem?

And the most important question is, why the testing scope needs to be changed? Isn't it testing UI or API alone sufficient? 'Not Always'. The exact answer lies in the kind of architecture/ecosystem projects have. But certainly, there are threats that can be avoided at the earlier stage by asserting quality gates, examples:

  1. Vulnerability Issues
  2. Performance Issues 
  3. Infrastructure Configuration Related Issues and many more.

Outline/Structure of the Demonstration

  • Basics on docker and related terminologies - 7 minutes
  • Problem statement and solution - 5 minutes
  • Levels of testing including test automation (All the testing levels followed by Demo) - 25 minutes
  • Pipelines - 5 minutes
  • Daemon and daemonless - 3 minutes

Learning Outcome

  1. What is a Docker heavy application? How does it look like?
  2. Different testing perspectives? – adding unit tests, evaluating security and performance?
  3. Test Automation
  4. Pipeline designing
  5. Answer to ‘Will the strategy remains the same for Daemonless?’

Target Audience

Open for all.

Prerequisites for Attendees

Basics of Docker and Container are required. 



schedule Submitted 1 year ago

  • Priya Malhotra

    Priya Malhotra / Usha Ramaswamy - Hello, I’m Culture…Did you forget me in your transformation journey???

    20 Mins

    Any transformation journey usually has a roadmap that focuses on process, tools, technology and people. Studies have shown that some key reasons why transformations fail are due to cultural aspects. However, culture is often ignored and we expect magic to happen quickly. Hence, a transformation needs to weave in culture shift as a critical part of the roadmap.

    We delve into…

    • What constitutes culture?
    • Why should a transformation look into culture shift?
    • A ‘culture gauge’ as a tool to calibrate the cultural aspects
    • The E3R model as a recipe to plan the culture shift journey
    • The elements of ‘thin slice’ and ‘1% improvement’ as key ingredients

    … we weave in our stories of failure, some good practices and envision how we would use the culture gauge and E3R model.

  • Varuna Srivastava

    Varuna Srivastava - Get Your Test Strategy Set

    45 Mins
    Case Study

    In this session, Varuna will share a specific case study of how an effective test strategy can get away from Push and Pray deployment to Continuous and Confident deployment to production. 


    This is a case study of the product, where the very first thing I observed was unclear roles and responsibilities within the QA of an organization. There was a low test coverage as there was no clear testing strategy to follow. Getting deployed to production was Push and Pray method which led to high risk for production. It was also causing inefficient use of QA timing. There was the pain felt throughout the organization in a smaller group and folks kind of accepted this pain. We started by noting down the pain points of producer and consumer teams within organizations and even a third-party team to come up with an effective test strategy for the product. 


    Participate in this talk to learn:

    1. How do we form a core team to define the external and internal strategy? 
    2. How did we apply recursive feedback and updated the strategy when and required after a production release?
    3. Internal Test Strategy: A strategy within a Team of the same vertical as checkout API and UI
    4. External Test Strategy: An end-to-end test strategy for a product
    5. How did it help in getting away from Push and Pray deployment to Continuous and Confident deployment to production? 


    We got the motivated QAs across the organizations and better quality products with a Test Strategy across organizations. It had also helped in mapping a QA learning curve with a test strategy within an organization