Topic: test & qa

Test & QA
Test and QA Stories

If you're a tester and you've been avoiding public speaking opportunities because you don't think it applies to your work, you don't know what you would talk about, or you're just nervous to present in front of people, you should change your mind. Public speaking has several benefits for testers.

To incorporate the user-acceptance testing function into a testing center of excellence (TCoE), the testing team must develop business-process knowledge coupled with technology and test process expertise. Here are some lessons that will aid in integrating the UAT function as part of the TCoE.

Google recently invested $300 million in an undersea cable system that helps with the transmission of Internet data from the west coast of the United States to two cities in Japan. But Google is faced with an unexpected challenge—not from its usual competitors Apple and Facebook, but from sharks.

Debates arise when people start talking about where a particular IT function should be performed. Executives can act as if testing is a necessary evil and cost is the only important factor. But in light of recent security breaches, companies should be more concerned with accurate testing than cost.

The International Software Testing Standard is implementing new internationally recommended practices for software testing collectively known as ISO 29119. However, copies of the standards are expensive, so most people haven't gotten to read them yet. Matt Heusser has, and he gives his opinions.

Most of us look at optimism and pessimism as purely black or white: Optimism is always good, and pessimism is always bad. A new angle adds another dimension, where you identify as either credulous or skeptical. Could knowing "your pair" help you better achieve your work objectives?

After you make investment decisions for homegrown, open source, or commercial tools that yield little or even negative return, those "learning experiences" reinforce the old saying—"A fool with a tool is still a fool." Here are some things to keep in mind as you reach for that next cool tool.

Command-driven testing has proven to be a good way to implement pattern tool independence. The main advantage is that you just have to develop the commands in the script language of the tool. To change tools, you only have to rewrite the keyword commands in the script language of the new tool.

Testable requirements, or acceptance criteria, are the communication of an expectation between its originator and potential stakeholders. Many testers struggle with this starting point. But once you succeed, you know the processes that can build and test a system implementing “good” requirements.

It’s easy for us as software developers and testers to dismiss intrusions on point-of-sale systems as the fault of network security professionals or inadequate network defenses. The reality is that there is a lot we should be doing as well on the software side to prevent these kinds of attacks.