Functional Testing : A Detailed Guide
Shreya Bose, Techical Content Writer at BrowserStack - May 11, 2021
In the simplest words, functional testing checks an application, website, or system to ensure that it is doing exactly what it is meant to.
In the planning stages, every project creates a document listing functional or requirement specifications. Essentially, it is a list of what the app/system/website is supposed to do, from a user’s perspective.
What is Functional Testing?
This article will lay out a thorough description of functional testing, its types, techniques, and examples to clarify its nuances.
Types of Functional Testing
- Unit Testing: This is performed by developers who write scripts that test if individual components/units of an application match the requirements. This usually involves writing tests that call the methods in each unit and validate them when they return values that match the requirements.
- In unit testing, code coverage is mandatory. Ensure that test cases exist to cover the following:
- Line coverage
- Code path coverage
- Method coverage
- In unit testing, code coverage is mandatory. Ensure that test cases exist to cover the following:
- Smoke Testing: This is done after the release of each build to ensure that software stability is intact and not facing any anomalies.
- Sanity Testing: Usually done after smoke testing, this is run to verify that every major functionality of an application is working perfectly, both by itself and in combination with other elements.
- Regression Testing: This test ensures that changes to the codebase (new code, debugging strategies, etc.) do not disrupt the already existing functions or trigger some instability.
- Integration Testing: If a system requires multiple functional modules to work effectively, integration testing is done to ensure that individual modules work as expected when operating in combination with each other. It validates that the end-to-end outcome of the system meets these necessary standards.
- Beta/ Usability Testing: In this stage, actual customers test the product in a production environment. This stage is necessary to gauge how comfortable a customer is with the interface. Their feedback is taken for implementing further improvements to the code.
Process Workflow for Functional Testing
The overview of a functional test includes the following steps:
- Create input values
- Execute test cases
- Compare actual and expected output
Generally, functional testing in detail follows the steps below:
- Determine which functionality of the product needs to be tested. This can vary from testing main functions, messages, error conditions and/or product usability.
- Create input data for functionalities to be tested according to specified requirements.
- Determine acceptable output parameters according to specified requirements.
- Execute test cases.
- Compare actual output from the test with the predetermined output values. This reveals if the system is working as expected.
Example: Use Case Scenario for Functional Testing
An online HRMS portal on which the user logs in with their user account and password. The login page has two text fields for username and password. It also has two buttons – Login and Cancel.
When successful, the login page directs the user to the HRMS home page. The cancel button cancels the login.
- The user id field requires a minimum of 6 characters, a maximum of 10 characters, numbers(0-9), letters(a-z, A-z), special characters (only underscore, period, hyphen allowed). It cannot be left blank. User id must begin with a number/character. It cannot include special characters.
- The password field requires a minimum of 6 characters, a maximum of 8 characters, numbers (0-9), letters (a-z, A-Z), all special characters. It cannot be blank.
The use-case scenario above can be tested through a variety of functional testing techniques.
1. End-user based/System Tests
Test the system to gauge if all components are working perfectly in combination.
In the example, this would entail testing the customer journey – HRMS application loading, entering accurate credentials, directing to the home page, performing tasks, logging out of the system. This test ensures that this workflow proceeds and completes without any errors.
2. Equivalence Tests
Test data is segregated into partitions called equivalence data cases. In this test, data in each partition must respond in the same way. Consequently, you only need to test one condition across all partitions. If the condition does not work in one partition, it won’t work in any of the others.
In the example, since the user id field can accommodate a maximum of 10 characters, it should behave the same way anytime data > 10 is entered.
3. Boundary Value Tests
These tests are used to check how the system behaves when data limits are implemented.
In the example, since the user id requires a minimum of 6 characters, this test will be used to check how the system responds when less than 6 characters are entered.
4. Decision-based Tests
These tests are initiated to check for possible system outcomes when a particular condition is met.
In the example, the following decision-based tests can be undertaken:
- If incorrect credentials are entered, the system should inform the user and reload the login page.
- If correct credentials are entered, the system should take the user to the home page UI.
- If correct credentials are entered but the user wants to cancel login, the system should not direct to the home page UI.
- Instead, it should reload the login page.
5. Ad-hoc Tests
These tests uncover discrepancies that might not have been identified in any of the other tests. Ad-hoc tests are targeted towards breaking the system and checking its response.
In the example, an ad-hoc test could be conducted to check the following:
While a user is still logged in, the administrator deletes their account – that too while the user is performing tasks. The test would check if the application responded gracefully in such a scenario.
Why automate Functional Tests?
Automation can certainly reduce time and effort in executing functional tests. Human error can also be lowered, preventing bugs from slipping past the test phase.
However, increased automation means that QAs need to develop test cases for each test. Naturally, formulating the right test case is pivotal, along with identifying the right automation tool for the purpose.
What to look for in the right automation tool?
- The tool must be easy to use, especially for all members of your QA team.
- It must be seamlessly operational across different environments.
- For example, ask yourself: Can you create test scrips on one OS and run them on another? Do you need UI automation, CLI automation, mobile app automation, or all of them?
- It must provide features specific to your team’s requirements.
- For instance, if certain team members are not comfortable with a certain scripting language, the tool should support conversion to other script languages that they may be better versed in. Similarly, if you need specific reporting and logging or automated build tests, the tool must be able to provide the same.
- In case of changes to the UI, the tool must support the reusability of test cases.
Best Practices for Functional Testing
- Pick the right test cases: It is important to intelligently select the test cases that you will automate. For tests that require some setup and configuration during or before execution, it is best not to automate. Automate the following kinds of tests:
- Tests that need to run repeatedly
- Same tests with different data
- P1, P2 test cases which consume much time and effort
- Tests that are prone to human error
- Same tests in different OS, browser, device, etc.
- Dedicated Automation Team: Automation requires time, effort and most importantly, a certain measure of specialized knowledge and skill-set. Not every member of your QA might be good at writing automation scripts or know how to handle automation tools. Before deploying automated tests, analyze the various skill and experience levels of your QAs, It is best to allocate automation tasks to those who are equipped to accomplish them.
- Data-Driven Tests: Automated test cases that require multiple data sets should be written in such a way that they are reusable. For this, the data can be written in sources such as XML files, text or property files or read from a database. Creating a structure for automation data makes the framework easier to maintain. It also enables more effective usage of existing test scripts.
- Be on the lookout for breaks in tests: Your test cases and chosen automation tool must adapt to potential UI changes. Take an example in which an earlier version of Selenium used a location to identify page elements. Now, if the UI changes and those elements are no longer at those locations, it can lead to test failures across the board. Thus, consider writing test cases that enact minimal change in the event of UI changes.
- Test frequently: Prepare a basic automation test bucket, and strategize for frequent execution of this bucket. With this, QAs can enhance the test automation framework to make it more robust. Needless to say, this practice also helps to identify more bugs.
How to perform Functional Testing with BrowserStack?
Whenever a developer submits a PR, teams must run functional tests that must execute fast enough to generate immediate feedback. Naturally, as more code is developed, it becomes more difficult to execute tests quick enough to keep the workflow efficient.
With BrowserStack, this problem is solved by offering the ability to run hundreds of Selenium and Cypress tests in parallel. This reduces overall test suite execution time from days or hours to minutes.
Additionally, functional tests can be run on more than 2000+ real browsers and devices. Device, browser, or OS fragmentation is no longer a concern, as BrowserStack facilitates testing in real user conditions on both desktop and mobile devices.
Functional Testing is an integral part of any software testing mechanism. It guarantees that a system operates exactly how it is meant to, in real-time. Given that functional testing occurs from a user’s perspective, it results in the delivery of a high-quality product that meets customers’ requirements and provides highly satisfactory user experiences. Naturally, this makes life easier for developers and business personnel alike.