From decades, one of the key goals for organizations is how to reduce time to market, decrease time taken by value streams and ensure quick handovers in assembly lines. 

When we speak of overall assembly line or Road to production in software development context, having minimal and yet strong check and balances is a desired milestone to achieve, this has been articulated as implementation of Test Pyramid, reducing dependency on mundane, manual or long list of integration test (even automated) and Shifting Left.

This conversation is going to be focused on one such implementation example where I will try to elaborate

  • A proposed approach to SHIFT LEFT and implementation of test pyramid model for automated tests, This will involve "identify, prioritize and automate" way with core emphasis on API tests and how we can de congest regression/ integration tests.
  • Identifying a good starting point for teams (as per their different maturity) and how they can navigate and ensure progress 
  • How the test environment evolve to achieve this stage. 

Outline/Structure of the Case Study

  • This presentation proposes approaches  to shift left and implement true test Pyramid. - 7 mins
  • It elaborates how to identify different levels of tests and then push them in right layers in test pyramid. -7 mins
  • Emphasis on role of API tests in the overall scheme of things. - 5 mins
  • Shape shifting of test pyramid from very start to end. - 5 mins
  • Outlines a level wise plan (maturity based) where teams can identify, classify and shift automation from UI to other layers and achieving true Shift Left. - 7 mins
  • Elaboration on test environment : how they look like and evolve during this journey. - 7 min
  • Q & A - 7 Mins 

Learning Outcome

  • Clear understanding of shift left and its impact on overall scheme of things.
  • How complex tests can be executed on lower environments. 
  • Impact of testing early (shifting left) to reduce late integration mess. 
  • How overall cycle time to production reduces due to testing early.

Target Audience

Scrum masters, SDETs, Engineering Managers, Test Engineers, Test Managers

Prerequisites for Attendees

Basic understanding of following:

  • Agile principles
  • Test Pyramid
  • DORA
  • Value stream mapping
  • Shift left.



schedule Submitted 10 months ago

  • Neha Gupta

    Neha Gupta / Shubham Jain - Record-Replay API Test Cases and Data Mocks without writing code

    45 Mins

    Application testing is one of the biggest barriers to achieving truly Continuous Deployments because it's use-case specific. Developers often avoid writing test cases because its time consuming, needs to be maintained for every change and metrics like coverage don't necessarily guarantee quality. In this session, we'll talk about how we could capture test cases from traffic data, how all infrastructure can be mocked automatically and how application writes could be safely replayed.

    Keploy is an open-source no-code API Testing Platform that generates test cases and data mocks from API calls.

    We'll walk through examples of how keploy can work alongside existing testing frameworks and capture test cases quickly and mock infrastructure without needing to write Unit API test cases. We'll also cover how these test cases would evolve as the application grows. The core contributors to Keploy will provide an overview of its features and capabilities, and how it is used at scale covering use-cases across microservices across various programming languages.