API(Application Programming Interface) testing is one of the crucial parts of product development,  API component is often developed before the UI component which allows for quick feedback, API testing is also a lot cheaper than manual E2E testing, If we start automating APIs in the early stage, it will definitely help to test the APIs quickly, also it helps to verify that any code changes won’t introduce regressions in Production, to develop the automation framework for API testing will take some time, then how to automate APIs quickly? We can automate APIs with the help of postman collections and can run those collections in CI on daily basis, We often use the Postman tool for validating the response of APIs.

In this workshop attendees will learn how to execute the collections in CI(Jenkins) and generate a beautiful  HTML report along with the below following mentioned points:

• Go through about Postman tool
• Add assertions in the postman request
• Create global variables and export collections
• Walkthrough Postman snippets & Newman
• Execute collections via command line and CI (Jenkins)
• Generate beautiful HTML report

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

Through discussion, group dynamics and knowledge sharing, Varuna Srivastava, Lead Quality Analyst of ThoughtWorks will facilitate exchanging ideas regarding, how to plan, where to start, how to build the performance script using Taurus.

This talk will walk through on optimizing performance scripts of API's using Taurus. Demo to learn how to write and run test automation using Taurus. We will walk through our journey of writing script for an enterprise application and how it helped in accounting the bottlenecks of APIs during the sprint

Participate in this workshop to learn how to put together the concepts of a wdio and typescript in a mocha framework that is scalable, robust, easy to read. We will be sharing our real-time experience of how we migrated our testing approach, design and framework when our application was migrating from javascript to a typescript architecture.

You will leave with your very own example automation framework that demonstrates advanced principles of wdio using typescript automation design. We will integrate with allure reporting.

Reference:

https://github.com/varunatester/sel-workshop

Key takeaways:

1. A robust and scalable framework with the advanced principle for ui testing.
2. A selection of design patterns for the designing framework.
3. Concepts in designing your ui automation such as modeling data within your application and componentizing page objects.
4. A framework which is responsive for web applications.