Pavan Yadlapalli
Humana, Principal Software engineer
Actions
Solution-Oriented IT professional with a wide variety of professional Experiences in Health care, Telecom, Systems Integration, CRM, etc.. Having Over 10 Years of IT Experience in development, Design, Architecture, Enhancement and Enablement. Highly motivated in learning and working on new systems and techniques every day.. :)
How to Automate API Testing - TDD&BDD
With increased pressures on organizations to deliver faster, teams are increasingly adopting Agile practices, and delivering software in iterations spanning a short period of time. Multiple iterations require repeated testing, this often calls for the teams to explore automatic test creation, execution and reporting. With automatic test creation, teams can create tests from design artifacts, like API definitions. When the APIs get updated, the team can bring in the change with very little effort. Automatic test execution involves plugging in tests into automation tools like Jenkins, Final Builder, Azure Devops, TFS, etc..
Automation increases the speed and Quality of delivery.
Demo: with Jmeter and Postman
Metrics-Driven Development
With emergence of DevOps(CI,CD), Releasing Software to production takes matter of hours or even minutes. Everything is scaling up and down (vertically), to the right and to the left (horizontally). Therefore having a good monitoring system is a must. However, monitoring is still being implemented by OPS team only. i.e teams who dont write applications. Why is that so? How can it be changed to achive better results?
We all heard about a widely known practice TDD - test-driven development, or about the less known BDD - behaviour-driven development, or about the least known ADD. However, Metrics Driven Development (MDD) is mentioned nowhere.
So what is MDD? My definition of MDD is a practice where metrics are used to drive the entire application development. In a company which uses MDD, everything from performance and usage patterns to revenue is measured. Moreover, every single decision taken by developers, operations or even business people is based on metrics. Metrics are used to monitor team performance, solve performance bottlenecks, estimate hardware needs or to accomplish other purposes at any stage of development life-cycle.
MDD brings visibility to the whole development process, so decisions are taken quickly and accurately and mistakes are spotted as they happen and fixed immediately.MDD stacks up well with other established practices such as TDD, BDD or Scrum, by using metrics to set the goals for the sprint. Metrics also uncover problems and usage patterns (in production) which are hard to notice during acceptance testing.
In this session i will share my thoughts and experience gathered while working with DEV teams trying to makes sence of metrics and MDD
CI/CD: Faster, better software development using test Automation
Over the past few years building self healing systems has been a driving motivation for many architects, performance engineers and site reliability engineers. Many of Companies like Netflix, Google, Amazon, Microsoft, Facebook and others, baked resiliency into everything they do like. But instead of just focusing on keeping a system up & running in production through smart auto-remediation, auto-scaling, failover and high-availability…, we should focus on building reliable and resilient systems throughout your Continuous Delivery Pipeline: from Dev all the way to Ops.
This is to show how such an End-to-End Delivery Pipeline, that prevents bad code changes or bad situations in production from impacting the reliability of your system, looks like
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top