<img alt="" src="https://secure.wauk1care.com/164394.png" style="display:none;">

Functional Testing - What It Is and Why We Do It

Posted by Ben Green on 2/07/2019

So, let’s get this blog post rolling with a nice sterile quote from the internet to outline the what:

‘Functional Testing is defined as a type of testing which verifies that each function of the software application operates in conformance with the requirement specification. This testing mainly involves black box testing and it is not concerned about the source code of the application.’

Functional Testing-1
Each functionality of the system is tested by providing appropriate input, verifying the output and comparing the actual results with the expected results.

So, all clear and all so simple, why is functional testing valuable?

  1. It questions the software to help provide information about its quality
  2. Software should match the specification
  3. Items that don't meet the specification are defects, which can place business operations at risk
  4. It simulates customer interactions with the software and how it is used, which can also result in defects
  5. Test results help stakeholders to make project decisions regarding scope, time and resource
  6. Change should be tested before it is exposed to business customers
  7. IT systems are built to functional requirements and design
  8. It saves money and improves operational efficiency by carrying out effective testing early in the Application life cycle

As you can see functional testing is essential and has wide ranging essential applications for the client. It is a wide net covering many different types and interactions, to list each in detail would balloon this short blog to the point where no one will want to read all of it, so I will summarise in a handy table:

Functional Testing
Boiling down all these testing methods, what can we as testers do to deliver on the principals listed above?

  1. To find different types of defects across each layer of the software
  2. Report on defects found by functional area, severity and their status
  3. Provide known coverage by functional area that can be measured
  4. Demonstrate that testing of impacted areas is considered
  5. Produce tests that can potentially be automated and run as a regression suite for each system
  6. Gain domain knowledge of the systems functionality
  7. Give stakeholders confidence that the product meets the business need
  8. Report on test outcomes effectively to help stakeholders make decisions about whether more testing is required
  9. Provide evidence that functional testing has been carried out

Now obviously time is a strong consideration, with something that covers quite as much as functionality testing, priority must be given to the areas that cover the most relevant risks. There are real risks of performing redundant tests to ‘do everything.

As the testing is based on requirements, if those requirements are not clear or lacking specific details quite logical tests might be missed. Likewise, it does not consider other factors that are essential to a viable product, for example performance or responsiveness.

These aside, functional testing is one of the important testing processes (or collection of) as it verifies the function of a product. Arguably the most important aspect of implementing a product for a client.

A How-To Guide For Test Planning

Topics: Software Testing, Functional Testing

nFocus Blog

Welcome to the nFocus software testing blog. As thought leaders and technical innovators, we created this blog to distil our thoughts, ideas and musings on improving software quality.

Fill out the form below to receive future communications from nFocus including our latest:

  • Blog articles
  • White Papers
  • and plenty more!

Follow us

Follow us on LinkedIn to see our latest content!

Subscribe Here!

Recent Posts

Posts by Topic

see all