Mukesh Sharma
Member for
12 years 8 monthsAs founder and CEO of QA InfoTech Worldwide, Mukesh is responsible for the company's vision and leads the organization's worldwide operations, marketing, sales, and development efforts. He founded QA InfoTech with a vision to provide unbiased Quality Assurance (QA) testing solutions and has grown the organization to four Centers of Excellence globally.
Mukesh has a passion for excellence, an eye for detail, and commitment toward customers, and he blends it with an execution style that has the maturity of an established organization with the nimbleness of a startup. These together have enabled QA InfoTech to stand apart in the exceedingly competitive software testing industry. Under his guidance, the company has contributed to various innovative quality assurance and test-automation solutions.
Mukesh continues to actively evangelize software testing as a career and its indispensable aspects in today’s world of software engineering. He has authored three books in these areas to benefit testers and engineers at all levels: Are You Smart Enough To Be A Tester?, Leverage The Wisdom of the Crowd in Software Testing, and Software Testing 2020: Preparing for New Roles.
Mukesh holds a Master of Science and Technology in Information Systems from Birla Institute of Technology and Science (BITS), Pilani, India, as well as a Master of Engineering in Engineering Management from University of Colorado, Boulder, USA. Mukesh is an avid reader, golfer and cricket player, as well as a philanthropist who takes a personal interest in the organization’s CSR initiatives.
All Articles by Mukesh Sharma
All Stories by Mukesh Sharma
|
Linguistic Testing: Setting Up Your Software for Global QualityGlobalization is an important step in ensuring your product is ready for worldwide markets, and linguistic testing is a crucial piece of the puzzle. This article looks at what linguistic testing is, product examples, and how locale-specific cultures play an important part in enabling linguistic support. Here’s how to design the best strategy for implementing a linguistic test effort. |
|
Setting Priorities Differentiates the Great Testers from the Rest When it comes to being a successful software tester, there is one important trait that makes all the difference: understanding what needs to be done now and what can be delayed. The ability to prioritize becomes an important attribute for success at a people level, at a process level, at an activity level, and at a communication level. |
|
Testing Usability for Mobile Applications Mobile usability goes a long way in enhancing end-user app acceptance. But usability starts with the user, and users differ in terms of knowledge, interests, goals, and so on. This article discusses some core usability characteristics that matter to customers, and how test engineers can understand and achieve them. |
|
Time-Tested Practices for a Successful Test EffortTesting in software development is changing incredibly quickly. Test effort varies across projects, teams, and organizations, each having its unique identity in delivering a quality product. However, certain core testing practices never change and continue to drive successful test efforts. Mukesh Sharma details some that he sees standing the test of time. |
|
Is Code Coverage a Silver Bullet? While code coverage is a good number to look at in terms of reach achieved in a testing cycle, is it foolproof? Is this metric a silver bullet for understanding the team’s coverage and vouching for testing scope? In short, no. But it is a vital step on the way to solving your testing coverage issues. |
|
When Testers Should Stand Up and Say No Testers often find themselves in predicaments where they may be asked to compromise on quality standards—whether it's pressure to sign off on a product before it's ready, getting involved in numbers games that value metrics above all else, or facing harassment to take on work that isn't theirs. Knowing when, how, and why to say no can improve your situation and gain respect for testers everywhere. |
|
Consider Rendering Times While Measuring End-User Performance Mukesh Sharma writes that if you want to build an effective performance test strategy involving smart devices, you need to consider rendering times. It’s no longer OK to simply measure the response times on desktop web applications like we did in the past. For mobile, the rendering time can make all the difference between a good and a bad user experience. |
| When to Say No to Exploratory Testing Mukesh Sharma writes that there are some situations in which exploratory testing does not work. Understanding these limitations is important in devising a holistic test strategy for the team. |
|
| Are You Too Obsessed with Objectivity in Quality? Objectivity is undoubtedly important when striving for quality. But it is possible to focus too much on the numbers and not enough on collecting data that will actually help you ship a high-quality product. These nine practices can help you devise an objective quality strategy that is actually useful to you and your team. |
|
|
Time to Think about an Open Source Automated Testing Ecosystem In our modern world of software development, software testing is increasing in importance as well as complexity. Today’s multitude of desktop and mobile operating systems, browsers, and devices, while on one hand, offer a great set of options for the end-user, also make it challenging for testers to ensure application and device compatibility. |
| Achieving Corporate Social Responsibility in Creative Ways The term “corporate social responsibility” (CSR) is becoming very common in the software industry, with many IT companies trying to implement it through varied programs of different scales. Mukesh Sharma explains an approach to promoting an organization’s CSR that is mutually enriching for software testing organizations and the academic institutions that they associate themselves with. |