To connect our Tribal Qonf Speakers and Audience better, we interviewed our speakers over a few important questions. The conversations we had were just amazing. 

In this edition, we are publishing the Interview we did with Omkar Khatavkar. Omkar answered many interesting questions and we are sure you will enjoy the read.
 

Tell us a little about what inspired you to become a tester?
Omkar: When I started my career in Testing, I was not much sure about it. After I read books, blogs from James Bach I got really inspired. Exploratory Testing is one of the things which really inspired me in testing. With this kind of testing you find such bugs that you get very good appreciations from the developer itself. Some of the developers want me to test their code before they wanted to merge in Github.
 

How will your talk motivate the attendees and one lesson they will carry from the conference?
Omkar: My talk and presentation will help people to know how to build the infrastructure as code for the test environment. How they can scale and distribute it easily
 

With a continuous change in tech stack, how do you keep yourself updated?
Omkar: I usually attend new conferences, talks and mainly watch my twitter and Linkedin account where I do follow lot of interesting people from testing community to know the latest trends and tech stacks. I have a goal that every 1-2 months, I have to do some online course to help my learning.
 

If someone wants to contribute to open-source software, what tips do you have for them?
Omkar: If you want to contribute the open-source software, which you really like. then start to learn about the documentation and software. Try to use it, which help you to learn about it. If you find the defects try to file then in the issues list. Join their IRC or communication channel to tell them what was failing. If you are good enough to know about the coding and excited to run the code try to debug and give the solutions.
 

Please share about your project to analyze failures?
Omkar: This is one of the major pain points. We are currently using the tool called Report Portal which help us to gather the failures and analyze it with its AI capabilities. I have personally also written an open-source project testblame which we also use in our project which sends an email to contributors whose tests are failing.

 

According to you, what are some often neglected/missing elements in Automation Frameworks?
Omkar: Logging and Scaling a framework based on the new requirements are getting neglected and causing a cascading effect on time and efforts. One should always be effective on logging and know how we can scale the framework in the next iteration.

 


We thank Omkar: for his time and energy to do this amazing interview. Stay tuned to hear from more Speakers.  Register to Tribal Qonf happening 27-28 June 2020 here.