1. What bugs are mainly come in web testing what severity and priority we are giving
The bug that mainly comes in web testing are cosmetic bugs on web pages, field validation related bugs and also the bugs related to scalability, throughput and response time for web pages.
2. What is the difference in testing a CLENT-SERVER application and a WEB application?
3. How can we write a good test case?
4. for a triangle(sum of two sides is greater than or equal to the third side),what is the minimal number of test cases required.
The answer is 3
1. Measure all sides of the triangle.
2. Add the minimum and second highest length of the triangle and store the result as Res.
3. Compare the res (re search) with the largest side of the triangle.
5. How will you check that your test cases covered all the requirements?
By using traceabiltymatrix.
Traceability matrix means the matrix showing the relationship b/w the requirements & testcases.
Warning: main(addon/adlink1.php): failed to open stream: No such file or directory in /home/qatestc/public_html/dbtesting.php on line 181
Warning: main(addon/adlink1.php): failed to open stream: No such file or directory in /home/qatestc/public_html/dbtesting.php on line 181
Warning: main(): Failed opening 'addon/adlink1.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/qatestc/public_html/dbtesting.php on line 181
6. What we normally check for in the Database Testing?
In DB testing we need to check for,
1. The field size validation
2. Check constraints.
3. Indexes are done or not (for performance related issues)
4. Stored procedures
5. The field size defined in the application is matching with that in the db.
7. What is Database testing?
Data bas testing basically include the following.
1) Data validity testing.
2) Data Integrity testing
3) Performance related to database.
4) Testing of Procedure, triggers and functions.
For doing data validity testing you should be good in SQL queries
For data integrity testing you should know about referential integrity and different constraint.
For performance related things you should have idea about the table structure and design.
for testing Procedure triggers and functions you should be able to understand the same.
8. How to Test database in Manually? Explain with an example
Ans:
Observing that operations, which are operated on front-end is effected on back-end or not.
The approach is as follows :
While adding a record thr' front-end check back-end that addition of record is effected or not.
So same for delete, update,......
Ex: Enter employee record in database thr' front-end and check if the record is added or not to the back-end(manually).