Rahul Parwal


Rahul Parwal

A Jaipurite with a B.Tech. in Computer Science & Engineering. Currently, working as a Senior Software Engineer at ifm engineering pvt. ltd., Pune. Worked on Software Development, Testing & Automation projects during the 3-year tenure with Capgemini.

Presently, involved in Industrial Automation, UI, API, and Mobile App Automation Testing projects at ifm engineering pvt. ltd. Adept at Automation Solutions, i.e., Selenium, Appium, WinAppDriver using C#, and Python.

A seeker at heart; love for Indian mythology and Cricket and connecting them with real-life situations give an edge both on professional and personal fronts. A firm believer of right education and an ardent advocate of open-source mentality. A great company to be with who will ensure that every conversation turns out to be as stimulating as a cup of hot coffee.

You can check out my latest ebook, “Ultimate Productivity Toolkit” at bit.ly/rpajtoolkit

Want to know more, Check out: about.me/parwalrahul

Title: Common Testing Mistakes –Are we really evolving?

Abstract: The mistakes that we plan to cover in our talk are listed below:

1.Thinking that locating errors can be scheduled.

2.Not considering the time lost to task-switching.

3.Treating testing as a low-priority task that can be interrupted for just about any reason.

4.Demanding that testers pinpoint every failure.

5.Demanding that testers locate every fault.

6.Repairing without retesting.

7.Ignoring cross-connections.

8.Paying insufficient attention to testability.

9.Insisting that all bugs be "reproducible".

10.Confusing testing with "creating and executing test cases".

11.Demanding process overhaul in your company.

For each of the above-mentioned mistakes, we are planning to cover the common traps, and ignored reality that leads to such traps. We will also share tips on how to avoid these common pitfalls. Understanding these common traps and hidden realities have helped us to avoid many of the common testing mistakes and succeed as a professional tester. We hope that this could help and benefit others too in someway.  As we were reading the mantra for this conference, i.e. “To test better we need to know better”. We feel that making our community aware of these common testing mistakes would enable our fellow testers to test and grow better. Time Estimate: We feel this presentation could be wrapped up in 30-35 minutes.