Most Read This Week
Eight Software Testing Buzzwords You Should Know
The industry’s jargon can be hard to decipher at times, especially when trying to explain these buzzwords to co-workers
By: Tim Hinds
May. 17, 2014 02:00 PM
The industry's jargon can be hard to decipher at times, especially when trying to explain these buzzwords to fellow co-workers within your organization who don't really have a clue what you are talking about. Buzzwords are unavoidable, however there needs to be a clear understanding of what a buzzword is and the testing buzzwords you should know.
What Is a Buzzword?
Basically, it comes down to the word being so overused it loses its original meaning and begins to confuse people within the industry. Think of the words like "visibility" or "enterprise" you have probably heard over and over again but each person has a different meaning for the word.
Top Eight Testing Buzzwords
1. Crowdsourced testing
Without mass coordination and planning, crowdsourced testing is not as effective as using a testing tool - which will get you better, more reliable, and more predictable results.
2. Testing as a Service (TaaS)
While some TaaS providers operate with heavy automation out of a well-equipped lab, you'll also find TaaS providers that use crowdsourced testing to achieve results for their clients.
3. Smoke testing
The meaning of smoke testing as it relates to performance testing still refers to an early check, but luckily no smoke is involved. It is used as a gatekeeper - telling the tester if it is alright to initiate the long, intensive battery of performance tests that will follow. The last thing anyone wants to do is kick off a long series of tests before heading home for the night, only to come in the next day and see that the system crashed five minutes after you walked out the door.
4. Sanity check
5. Regression testing
Mike Kelly, an expert in regression testing explains, "When I think about regression testing, I think about any testing that involves the reuse of tests (manual or automated) or test ideas (regression charters for example -- a regression test does not necessarily need to be the exact same test) to manage the risks of change. This could include testing for bug fixes, testing to make sure a bug fix didn't break something else."
6. Automated testing
Software quality underwent a paradigm shift when automated testing systems were introduced. Instead of hiring an army of people to test a few functions on a few systems, it was suddenly possible to develop and run thousands of tests across many different real and virtual systems every day.
7. Continuous integration
8. Exploratory testing
Kaner now defines the term as "a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his or her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run parallel throughout the project."
Don't Let These Buzzwords Fool You
Reader Feedback: Page 1 of 1
Subscribe to the World's Most Powerful Newsletters
Today's Top Reads