Functional automation testing :
The purpose of functional testing is to ensure that the application and all of its individual functions work as they should in the real world and meet all requirements and specifications,
Whenever any changes done in any functionality of project it would required to test that particular functionality along with dependent functionality as well. in terms of manual testing it will take very much time to test whole system. To minimize the time and perform regression testing again and again test automation will come into the picture
Test automation further helps us to automate test cases and features that are constantly regressing.
This way QA’s have more time in testing other parts of the application. Moreover, this helps in ensuring the quality of the product in application releases.
As a result, we get products that are more effectively and stable, and its help to streamline QA process.
Through automation testing, it will help to lower the cost of bug fixing and also help us to improve the quality of application as well as process.
Objective of functional testing to cover application system and mainly focus on main functions, basic usability, accessibility and error conditions.
Mostly used functional testing tools:
- Selenium: Selenium web driver is the most popular open source automation tool currently to automate any web-application.
- QTP: This tool is user-friendly Functional Test tool by HP
- JUnit: Used mainly for Java applications and this can be used in Unit and System Testing
- SoapUI: This is an open source functional testing tool, mainly used for Web service testing. Its supports protocols such HTTP, SOAP and JDBC.
- Watir: This is a tool that helps with conducting functional testing for web applications. It supports tests executed at the web browser and uses ruby scripting language
- Appium: This open source tools used for mobile automation testing
Functional testing should be prepare based on the below key points:
- Preparation of test data based on the specifications of functions
- Business requirements are the inputs to functional testing
- Based on functional specifications find out of output of the functions
- The execution of test cases
- Observe the actual and expected outputs
With the help of functional automation testing we can cover below testing as well:
Unit Testing: A unit can be almost anything you want it to be - small amount of code, a method, or a class. All the small tests give you overview of application.
Smoke testing: Smoke testing, in the case of software development, is a series of test cases that are run before the initiation of more rigorous tests. The goal of smoke testing is to verify that an application's main features work as per the given application specification.
Integration Testing: The goal of integration testing is to check the functional, performance, and reliability between the modules that are integrated properly or not.
Interface Testing: Interface Testing is performed to recognize whether frameworks or segments pass information and control accurately to each other. It is to check if every one of the connections between these modules are working appropriately and mistakes are taken care of legitimately..
System Testing: System testing of the application is done on entire application programming to check the general consistence of the item with the practical necessities.
Regression Testing: Regression testing a testing procedure that comprises of re-executing those tests that are affected by the code changes.
UAT: UAT, a testing process where the clients/end users involved in testing the product to validate the product against their requirements.
Localization: The purpose of localization testing is to explore the defects and gaps in the software, which can impact the proper functioning of the user interface, linguistic translation, time-format, currency, font-scripting, resource translation, content & UI, functionality and features of a local version of the software product, for a particular country/location.
Globalization: Globalization testing ensures that the product is functioning properly with every possible kind of international input that there is. It ensures that without breaking functionality the code can handle all international support
Non-Functional automation testing :
Non-functional testing is a type of testing to check non-functional area of application in terms of performance, usability, reliability, efficiency,etc
In a cross-channel and multi-tier environment, one of the biggest challenges faced by client is that the live systems need to come up to the expectations of the customers in terms of performance, security, and usability.
To fulfill client desires output, applications should be versatile. But, certain problems like data theft, low response time, and poor speed make it difficult to explore and engage with the applications.
We'll offer a complete array of non-functional testing services that assist with proactive and early identification of defects in the lifecycle for various digital platforms including mobile, web, cloud, etc.
Objective to perform Non-functional testing:
- Non-functional testing should improve usefulness, portability, efficacy, and maintainability of the application.
- Minimize the production costs and risks related to the non-functional features of the application.
- Collect metrics data to perform internal research and application performance analysis.
- Verify product behavior and technologies used.
Key parameters of Non-functional testing.
Security: in the security testing perform the testing to prevent a range of different threats. These include denial of service attacks and other cyber-attacks, and data breaches or data theft situations.
Reliability: its ensure that the software is performing and functioning consistently in the given environmental conditions as well as in a specified period of time.
Recovery: Recovery testing is a kind of non-functional testing method performed so as to decide how rapidly the system can get back after it has a system crash or any hardware of the server or system failure. In recovery testing, the software is made to fail forcibly to verify if the system or application is able to recover successfully along with all the data.
Stability: Stability Testing checks the product’s capability to keep functioning properly, without any failure, over time and throughout its complete range of usage potential.
Usability: Usability testing is done from the point of view of an end-user to ensure that the system is easy to use.
Key parameter to perform usability testing is:
- Comprehend who will be using the system.
- Comprehend what their business requirements are.
- Try to replicate their behavior.
- Do you know role-playing? If not, start to learn.
Scalability: Scalability Testing measured in terms of its ability to increasing or decreasing the number of user requests or other such performance measure characteristic. In the scalability measured the parameters are Response time, Throughput, Number of User for performance test, Threshold load, CPU usage, Memory usage, Network usage, Web server request vs response.
Efficiency: efficiency testing test the line of code and testing resources required by a program to perform a particular function. Software Test Efficiency is total number of test cases executed divided by total number of hour used to perform operation, mostly its measure by per hour.
Portability: Portability testing procedure of testing effortlessly with which the product or item can be moved starting with one condition then onto the next. It is estimated regarding most extreme measure of exertion required to exchange starting with one framework then onto the other environment.
Mostly used Non-functional Testing Tools:
- Load Complete
- Webserver Stress Tool
- WebLoad Professional