Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

MythBusters: Functional Testing Edition

DZone's Guide to

MythBusters: Functional Testing Edition

Functional testing is on the busting block in this article that dispels some of the myths regarding its importance and differentiation from other testing types.

· Performance Zone ·
Free Resource

xMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.

The other day I was looking for more information on functional testing, so of course I went to the go-to spot for testers and developers to ask their questions—Stack Overflow. Crawling through the posts that were tagged with "functional testing," I noticed there was a lot of confusion around this subject including some questions I had.

The next step seemed obvious to me—embrace my inner Adam & Jamie to bust some myths around functional testing.

Myth 1: Functional Testing and End-to-End Testing are the Same Thing.

Functional testing and end-to-end testing are not the same thing. Functional testing looks to make sure that each function of an application is in conformance with specified requirements.

End-to-end testing is a testing methodology used to test whether the flow of an application is performing as intended from start to finish.

So, what's the difference? First of all, functional testing should be conducted before end-to-end testing. The point of end-to-end testing is to simulate a real user experience. With end-to-end testing you are required to have built out all components of an application that have a dependency including real databases, networks, third party systems, etc.

With functional testing, you can use in-memory implementations of your application to check whether the functionality meets the requirements.

Myth 2: System Testing Is a Component of Functional Testing.

This myth is backwards—in fact, functional testing is a component of system testing. System testing is the testing of a fully integrated software product. It is a type of black box test which is completed to verify:

  • End-to-end testing scenarios
  • User's experience with an application
  • Fully integrated applications

There are over 50 types of system testing which range from functional testing to hardware/software testing and usability testing. Functional testing does not incorporate the other types of testing such as load testing and regression testing that is included for system testing. This is why it's important to start with functional testing where you start testing for functional completeness before moving on to system testing.

Myth 3: Functional Testing Includes performance testing.

Functional testing and performance testing are in two different categories: functional testing and non-functional testing.

As defined above, functional testing is used to ensure that the functionality of an application meets specified requirements. Non-functional testing checks the "readiness" of a system by examining the performance, security, reliability, scalability, and other non-functional aspects of the software system. While non-functional testing includes performance testing, it also includes many other types of testing. Some examples may include:

  • : How many people can your application support using full-functionality at one time?
  • Security Testing: Is the system safeguarded against attacks? Both internal and external sources?

Myth 4: All Functional Testing Should Be Automated.

There is a common misunderstanding that manual testing will soon be obsolete because of automation, however this is not the case. It's important to find the balance between automated and manual tests, because as long as humans are interacting with applications, manual testing will always be around.

In general, you should use manual testing when you need to mimic real-world user interactions with an application. Common manual testing practices, that should remain manual and not automated, are exploratory testing, usability testing, and ad-hoc testing. These may include when you need to run complex tests, adhere to strict regulations, create robust documentation, or working with legacy applications that are not built to support automation.

Additionally, manual testing can be useful when you are looking to test for an improved customer experience as you can only collect this feedback through manual, not automated testing.

Fact: Functional Testing Matters.

You must make sure your application is functioning as you intend for it to-otherwise you risk providing a poor user experience, or no experience at all.

But there is some good news! There are plenty of functional testing tools out there to make your life easier. Whether testing the front-end, back-end, or both of your applications, SmartBear has the most powerful, yet easy-to-use functional testing solutions. With our solutions, we help software teams create great software, faster than ever.

Follow the author @Bria_Grangard

This article was first published on the SmartBear blog.

Discovering, responding to, and resolving incidents is a complex endeavor. Read this narrative to learn how you can do it quickly and effectively by connecting AppDynamics, Moogsoft and xMatters to create a monitoring toolchain.

Topics:
performance ,performance myths ,mythbusters ,system testing ,functional testing

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}