Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Microservices Expo, Java IoT, Microsoft Cloud, Linux Containers, Agile Computing, @DXWorldExpo

Microservices Expo: Article

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

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?
A buzzword can be defined as, "a term of art or technical jargon that has begun to have wider use in society among non-specialists who use the term vaguely or imprecisely."

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
Crowdsourced testing is becoming a popular word to throw around, especially since the rise of crowdsourced funding (not related to testing). Crowdsourced testing is when a person with a website asks fellow testers to "attack" the server to see how much load the site can take and to try to run through many user paths. You can probably find a Redditor asking his fellow friends to join him for a "load testing party." Like this guy...

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)
TaaS is also known as on-demand testing. Basically, it is an outsourced model where a test plan is given to a service provider who then executes all that testing on the organization's behalf. Usually, due primarily to expense, a company will still do most of their testing in-house. TaaS is most suitable for specialized testing efforts that don't require a lot of in-depth knowledge of the design or the system but may require a unique environment or short-term bursts of specialized activity.

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
This buzzword has significantly changed since when it was first used. The first thing an electronics engineer would do when testing a device was to turn it on and watch for smoke. If they saw any, something was clearly wrong.

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
Sanity checks are synonymous with smoke tests. You've probably heard this one a couple times. It's a basic test to quickly evaluate whether a claim or the result of a calculation can possibly be true. In testing, a sanity check will determine whether it is possible and reasonable to continue testing.

5. Regression testing
This buzzword might bring you back to your freshman statistics class and some people confuse this test for looking for some sort of trend. It actually means you are testing changes to applications to make sure that older bugs that were previously fixed are not reintroduced with the new changes.

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
Automated testing is often thought of as being specifically for functional testing, but it can mean any type of testing that is not performed manually. Businesses can automate many tasks, including load testing, which is easier than you might think if you're already running Continuous Integration builds.

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
If you can automate your testing, why not run it with every code change? This is the concept behind continuous integration. The various developers working on a project combine their code - or check it in - to a central repository where it is built and tested automatically and continually. When a problem pops up between changes, you know about it immediately and can correct it right away.

8. Exploratory testing
You can thank Cem Kaner, the man who coined this buzzword back in 1983. Exploratory testing is sometimes confused with ad hoc testing but it's actually an approach to software testing that is concisely described as simultaneous learning.

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
Now that you have a clear understanding for these software testing buzzwords, we hope they won't fool you in the future. Go forward knowing you have a clear understanding of what each of these words actually mean.

More Stories By Tim Hinds

Tim Hinds is the Product Marketing Manager for NeoLoad at Neotys. He has a background in Agile software development, Scrum, Kanban, Continuous Integration, Continuous Delivery, and Continuous Testing practices.

Previously, Tim was Product Marketing Manager at AccuRev, a company acquired by Micro Focus, where he worked with software configuration management, issue tracking, Agile project management, continuous integration, workflow automation, and distributed version control systems.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.