Functional Testing

Functional testing involves testing of how an application functions or in other words functional testing verifies that each function of the software application operates in conformance with the requirement specification and it always concentrates on user’s perspective and does not consider the internal structure of application.

Functional testing is very important because it verifies that the software application is fixed for release and does what the users expect from it.

Functional testing typically involves following steps:

• Identify the requirements.
• Understands the functions.
• Identify the test inputs and derive output based on software specification.
• Execution of Test Cases.
• Comparison of Actual results with expected results.

What Sunbonn believes?

We at Sunbonn perform full functional testing efficiently including Positive functional testing which involves testing the functions of the application by using valid inputs, Negative functional testing which involves the testing the functions of the application by using invalid inputs or with some unexpected conditions.

We are always ready for any challenge to meet the user requirements, because we believe in customer’s satisfaction and in order to satisfy our customer it is necessary to meet all the requirements.

Our approach for functional testing:

• Identify requirements.
• Prepare Test plan.
• Design Test scenarios and test cases.
• Execute Test Plan.
• Identify bugs.
• Prepare Summary Reports.
• Project closure and maintenance.

Mobile Testing

Mobile application testing is the process of catching all of the functional and performance issues of your mobile application.

In highly competitive world of mobile application it is very important to ensure that the application is working perfectly well from usability and functionality point of view before the release because it is really crucial for the success of any application. It is vital to make sure that user have good experience when they use your mobile application because if they don’t have good experience they won’t come back if they won’t come back it means they will find some other similar application that will satisfy their expectations and provide them good experience.

Mobile testing have different and unique challenges such as ensuring the performance of the application across multiple operating systems, device models within each OS, and varying internet speeds across different markets limited screen sizes and memory, device fragmentation, difficulty of system integration, engaging user experience and, of course, a rapid pace of innovation.

What Sunbonn believes?

We at sunbonn believe that for quality of our mobile application, application should be tested on real devices and not only on the simulators or emulators that’s why we at sunbonn test our mobile applications not only on emulators but also on real devices. Therefore, we have vast collection of Tablets and mobile phones so that we can ensure the quality of our application because what matter for us is the quality of our application.

For successful Mobile testing we keep following key points in mind:

• Think like a Customer.
• Make strategic testing plan
• Focused non-functional and functional testing.
• Use of matric for improvement.
• Cover all required OS and screens sizes

Usability testing

Usability testing is a way to evaluate how easy it is to use the application or how easily user can learn the software/application. We can say that the purpose of usability testing is to test that whether the application is built user friendly or not and whether the application is efficient enough to satisfy the user’s expectations i.e. user feels comfortable with the application’s layout, its speed and its navigation and content. Usability relates to all kinds of software: website, mobile application, desktop application, embedded software, etc.

Usability testing involves real user and during usability testing real users are asked to perform certain tasks in order to measure the user’s ease of use and user’s perception of experience.

So it is to say that usability testing includes testing user interface (UI) and user experience (UX). One is about testing your Graphical User Interface and how it looks & behaves, while the other focuses on user experience and user behavior.

What Sunbonn believes?

We at sunbonn strongly believe in usability testing because user’s good experience is really important for us and that is why we at sunbonn, perform usability testing for our applications. We also follow the strategy of releasing our applications to pilot users and then we take review from them about their experience and ask for suggestions as well. We constantly try to make the user’s experience more better by enhancing the application after the feedback of the pilot users.

Our goals for usability testing are:

• Learnability: How easy is it for users to accomplish basic tasks the first time encounter the design?
• Efficiency: How fast can experienced users accomplish
• Memorability: When users return to the design after a period of not using it, does user remember enough to use it effectively the next time, or does the user have to start over again learning everything?
• Errors: How many errors do users make, how severe are these errors and how easily they recover from the errors?
• Satisfaction: How much does the user like using the

API/Web service Testing

What is An API?

An API (Application Programming Interface) is a collection of software functions and procedures, called API calls that can be executed by other software applications; it defines how software components

interact with each other.

What is a Web Service?

Web Services is the mechanism or the medium of communication through which two applications / machines will exchange the data irrespective of their underline architecture and the technology.

API Testing is done to make sure that the basic functional units of the software system works perfectly well. API testing is specifically the testing of API functions and it testing mainly concentrates on the business logic layer of software architecture and not on the look and feel of the application.

API testing is designed to consider the ‘full’ functionality of the system, as it will be used by the end user.

API testing requires the testing tool to interact with the API there are several tools for testing API some of which includes:

• Fiddler, Webinject, Junit, XMLUNIT, HttpUnit, ANT

What Sunbonn believes?

We at sunbonn believe that each and every functional unit of application should work perfectly well that’s why we implement API testing because by implementing API testing we can identify the smaller errors and it helps us in evaluating the strength of the build and allows the faster release with the improved test coverage. We also believe that the cost of bug fixing is drastically less in API level as compare to when those functionality bugs are found by user from application user interface.

Our approach to test any product that contains an API is:

• Understand that API Testing is a testing activity that requires some coding and is usually beyond the scope of what developers are expected to do.
• Traditional testing techniques such as equivalence classes and boundary analysis are also applicable to API Testing
• It is almost impossible to test all possible scenarios that are possible to use with your API. Hence, one should focus on the most likely scenarios, and should also apply techniques like Forced Error Testing using different data types and size to maximize the test coverage

Performance Testing

Performance testing is a non-functional testing technique performed to determine speed, effectiveness or stability of a computer, network, software program or device. Performance testing measures the quality attributes of the system, such as scalability, reliability and resource usage. This testing is the subset of performance engineering, which is focused on addressing
performance issues in the design and architecture of software product.

Performance testing does not aim to find defects in the application, it address a little more critical task of testing the benchmark and standard set for the application. Accuracy and close monitoring of the performance and results of the test is the primary characteristic of performance testing.

Why it is important?

Performance testing is very important because Non-performant (i.e., badly performing) applications generally don’t deliver their intended benefit to an organization and therefore
can’t be considered as reliable assets and the applications sent to market with poor performance metrics due to nonexistent or poor performance testing are likely to gain a bad reputation and fail to meet expected sales goals so it is very important to do performance testing before the release because it uncovers what needs to be improved before the product goes to market and if performance testing is not done before the release then software application can suffer from the issues like running slow while several users use it simultaneously, inconsistencies across different operating systems and poor usability.

There are some common problems which have wide variety of causes like

• Software configuration issues (for the Web server, database, load balancers etc.);
• Poor network configuration;
• Software code (poorly optimized, or not allowing concurrent access),
• Insufficient hardware resources.

The only way to pinpoint these performance problems before the application goes into

production is by simulating a large number of simultaneous users (load testing, stress testing).

What Sunbonn believes?

To achieve quality, reliability and speed, we at Sunbonn use a combination of Manual and Automation tool to ensure we can provide a rapid turn around and precise data set for given software on Performance front.

Our approach for performance testing:

• Collect the business requirements and identify the key elements to set up the test environment.
• Identify reasons for performance testing and define baseline values and create test plan.
• Create test scenarios and define test data.
• Execute test scenario
• Validate and record results.
• Analyze test results and make recommendations.

We use various tools to accomplish performance related tests and following are the different types of performance testing that we cover: