1. GUI/Behavioural Coverage
GUI testing is a testing technique in which the application’s user interface is tested whether the application performs as expected with respect to user interface behaviour.
GUI Testing includes the application behaviour towards keyboard and mouse movements and how different GUI objects such as toolbars, buttons, menu bars, dialog boxes, edit fields, lists, behavior to the user input.
GUI Testing Checklist:
- Check Screen Validations
- Verify All Navigations
- Check usability Conditions
- Verify Data Integrity
- Verify the object states
- Verify the date Field and Numeric Field Formats
2. Input Domain Coverage
Domain Testing is a type of Functional Testing which tests the application by giving inputs and evaluating its appropriate outputs. It is a software testing technique in which the output of a system has to be tested with a minimum number of inputs in such a case to ensure that the system does not accept invalid and out of range input values.
One of the most important White Box Testing methods is domain testing. The main goal of the Domain testing is to check whether the system accepts the input within the acceptable range and delivers the required output. Also, it verifies the system should not accept the inputs, conditions and indices outside the specified or valid range.
Domain might involve testing of any one input variable or combination of input variables.
3. Error Handling Coverage
Error handling refers to the anticipation, detection, and resolution of programming, application, and communications errors. Specialized programs, called error handlers, are available for some applications. The best programs of this type forestall errors if possible, recover from them when they occur without terminating the application, or (if all else fails) gracefully terminate an affected application and save the error information to a log file.
In programming, a development error is one that can be prevented. Such an error can occur in syntax or logic. Syntax errors, which are typographical mistakes or improper use of special characters, are handled by rigorous proofreading. Logic errors, also called bugs, occur when executed code does not produce the expected or desired result. Logic errors are best handled by meticulous program debugging. This can be an ongoing process that involves, in addition to the traditional debugging routine, beta testing prior to official release and customer feedback after official release.
A run-time error takes place during the execution of a program, and usually happens because of adverse system parameters or invalid input data. An example is the lack of sufficient memory to run an application or a memory conflict with another program. On the Internet, run-time errors can result from electrical noise, various forms of malware or an exceptionally heavy demand on a server. Run-time errors can be resolved, or their impact minimized, by the use of error handler programs, by vigilance on the part of network and server administrators, and by reasonable security countermeasures on the part of Internet users.
Usage
- It determines the ability of applications system to process the incorrect transactions properly.
- Errors encompass all unexpected conditions.
- In some systems approx. 50% of programming effort will be devoted to handling error conditions.
Objective
- The Determined Application system recognizes all expected error conditions.
- Determine Accountability of processing errors has been assigned and procedures provide a high probability that errors will be properly corrected.
- Determined During the correction process reasonable control is maintained over errors.
4. Manipulation Coverage
The Correctness of output or outcomes. It means returning correct output values. In this testing it is checked that when a user enters the input then the output provided to the user is correct or not. Manipulation coverage can also be referred to as calculation related testing. It is very important and useful for testing. Manipulation coverage is the process of evaluating the final product to check whether the software meets the customer expectations and requirements. It reduces the chances of failures in the software application or product.
When conducting manipulation coverage, you typically need to follow a process that looks something like this:
- Determine what the expected outcome should be based on those inputs
- Use test data to identify outputs
- Run the test cases with the proper inputs
- Compare the expected results to the actual results
5. Backend coverage
Backend coverage also known as database testing. Database Testing is checking the schema, tables, triggers, etc. of the database under test. It may involve creating complex queries to load/stress test the database and check its responsiveness. It Checks data integrity and consistency.
Database testing basically include the following:
- Data validity testing: For doing data validity testing one should be good in SQL queries.
- Data Integrity testing: For data integrity testing one should know about referential integrity and different constraints.
- Performance related to database: For performance related things one should have an idea about the table structure and design.
- Testing of Procedure, triggers and functions: For testing Procedure triggers and functions one should be able to understand the same.
