1. How U Do The Back End Testing In QTP?
Ans: First of all we have to know what back end is testing. Back end testing is nothing but checking the correctness of the Database.
With QTP we can write a script which going to connect the
Backend I mean a database of our inquiry then we can set it on the Datatable where we can compare the backend data with
The real one and determine If there is any inconsistency and so on so forth.
2. How To Do Testing For Performance Related Issues?
Ans: Testing can be done whether indexes have been created on particular table or not,as indexes are used to increase the performance.
3. What Are Pros Of Back End Testing?
1. The back end is no longer a “black box”
to testers. Many bugs can be effectively found and fixed in the early development stage. Take Forecast LRS as an example; the number of bugs in a back
end was more than 30% of total number of bugs in the project.
2. When back end bugs are fixed, the system quality is dramatically increased.
4. How To Do Functional Testing in Backend?
Ans: A back end structure is divided into number of tests
Based on application functionality. The tests focus input and output conditions but not structure or implementation.
5. How To Do Boundary Testing In Backend?
Ans: To check the boundary conditions of columns.
6. How To Do Stress Testing In Backend?
Ans: Testing database under heavy loads.
e.g.: testing the table which has large number of records
Used by number of users at the same time.
7. How Are Integration Tests Done In SQL Server?
Ans: Integration tests should be performed after the above component testing is done. It should call stored procedures intensively to select, update, insert and delete records in different tables and different sequences.
The main purpose is to see any conflicts and incompatibility.
Conflicts between schema and triggers
Conflicts between stored procedures and schema
Conflicts between stored procedures and triggers
8. What Is Benchmark Testing?
Ans: When a system does not have data problems or user interface bugs, system performance will get much attention. The bad system performance can be found in benchmark testing.
Four issues must be included:
System level performance
Major functionality (Pick up most-likely-used functions/features)
Timing and statistics (Minimal time, maximal time and average time)
Access volume (A large number of machines and sessions must be involved.)
Ans: here are several phases in back end testing. The first step is to acquire design specifications for an SQL server. The second step is test specification design. The next step is to implement the tests in this design with SQL code. The test specification design should contain information concerning component testing (individual pieces of the system), regression testing (previously known bugs), integration testing (several pieces of the system put together), and then the entire system (which will include both front and back ends).
What Are Back End Testing Phases And Database Testing Phases?
Component testing will be done early in the development cycle. Integration and system tests (including interfaces to front ends and nightly processes) are performed after the component tests pass. Regression testing will be performed continuously throughout the project until it is finished. The back end usually does not have an independent beta test, as it only exercised by the front end during the beta test period. The last step is to deliver users a quality product.
Back end test methodology
Back end test methodology has many things in common with front end testing and API testing. Many test methods can be used for back end testing. Structural testing and functional testing are more effective approaches in back end testing. They are overlapped in some test cases. However, the two methods may discover different bugs. We strongly recommend testers to do both types of testing. There are many other test methods that can be applied to back end testing. We list a few below. For other test methods, please check other test design references.
A back end can be broken down into a finite number of testable pieces based on a back end’s structure. Tests will verify each and every object in a type of structure.
A back end can be broken down into a finite number of testable pieces based on application’s functionality. The test focus is on functionality of input and output but not on the implementation and structure. Different projects may have different ways to break down.
Many columns have boundary conditions. For example, in a column for percentages, the value cannot be less than zero and cannot be greater than 100%. We should find out these types of boundary conditions and test them.
It involves subjecting a database to heavy loads. For incidence, many users heavily access the same table that has a large number of records. To simulate this situation, we need to start as many machines as possible and run the tests over and over.
Ans: here are several phases in back end testing. The first step is to acquire design specifications for an SQL server. The second step is test specification design. The next step is to implement the tests in this design with SQL code. The test sp...
10. Differences Between Back End Testing And Front End Testing?
Ans: It is not easier to understand and verify a back end than a front end because a front end usually has friendly and intuitive user interfaces.
A back end has its own objects, such as, tables, stored procedures and triggers. Data integrity and protection is critical. Performance and multi-user support are big issues. Slowness in operation can be vital to the project’s future.
There are no sufficient tools for back end testing. SQL language is mainly a testing tool. MS Access and MS Excel can be used to verify data but they are not perfect for testing. However, there are a large number of test tools available for front end testing.
To be able to do back end testing, a tester must have strong background in SQL server and SQL language. It is relatively difficult to find testers who understand both SQL server and SQL testing. This causes a shortage of back end testers.