In a perfect world CIOs, CTOs, devs and QA squad would be perfectly aline. Software would always function the way it was designate, security severance would be a thing of the yesteryear and the movie Top Gun 2 would kibosh being delayed.

Unfortunately, the world is imperfect, but there is a silver lining. Today ’ s CIOs understand the importance of quality, velocity and the value of package screen. They know that their user expect flawless and ordered experience across all platforms and the only way this is possible is through testing.

That ’ s a great start and represents solid progress from where we were only a few little years ago. However, if you experience be watching my video serial, 10 Things Testers Wish CIOs and CTOs Knew About Testing, you ’ ll understand there is withal a gap between what your boss does cognise and what you want them to. For more detailed info on how I think we should direct this gap, I tempt you towatch all 10 videos of the series, but as this is the internet I would be neglectful not to offer you a TL; DR version.

Let ’ s analyze the top five concepts tester wish their CIOs knew about package examination and quality.

1. Achieving 100 percent test mechanisation is not potential

The purpose of test automation ne'er has been and never should be to accomplish 100 percentage coverage. The verity is that some code is too unmanageable to write automation for and some codification is too unimportant to write automation for. What you want to do is use a risk-based approach to guide you towards furnish coverage for the most important parts of the software.

2. Test mechanisation is not entail to supercede humans

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Humans and technology get different skill sets. Automation doesn ’ t supersede testers. Automation frees testers to go beyond pure application functionality and rather focus on ensuring that the flow and overall user experience are intuitive and in line with your client ’ always-changing expectations.

3. The role of a tester is not to search for bug

Bugs are bad and they are expensive. But, finally, the role of a quizzer is to model and recommend for a outstanding user experience. Does that include, to some extent, discover bugs and ensuring they don ’ t make it to product? Of trend. But just because software is bug-free doesn ’ t mean it ’ s user-friendly. Testers should be focused on ensuring that your customers are handle to a seamless, intuitive experience that keeps them come backward.

4. Selenium is not a strategy

Selenium is a wonderful resource for testers, and it has a place in your overall testing scheme. But it can not be the integrality of that scheme. A unfeignedly comprehensive testing scheme spans unit tryout, API exam, integrating tests, performance and visual tests, and even error monitoring in production. Selenium solves a great number of challenges, but a modernistic examination strategy ensures quality throughout the entire software development lifecycle.

5. Quality is Everyone ’ s Responsibility

For testers, understanding our customer and our business is as much a portion of our job as understanding how to code. We involve to know what motor our client – what they like, what they dislike, what motor them to our software, and what maintain them come backward. And we need to know everything about our business – what drives revenue and ontogeny, what drives customer holding, and how we stack up against competitors.