Está en la página 1de 20

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.
What is Database testing?

Testing the backend data bases like comparing the actual results with expected results
Database testing is actually testing the procedures for locks, Imports and Exports, testing DB server which is usually done by a DBA How to Test database in Manually? Explain with an example
hi nitya,u can test DB in many ways and there are different approaches in Oracle and SQL erver 2005.Sql server is an easy approach to test ur DB. The simplest way is that You have SQL profiler in SQL server which lists down all the DB transaction done against the DB server once you are done with your application the just you can go and track down all the quires and SPs involved for your application and you can cross verify them in the quiery analizer.Or else ethere is a long process like U need to have acess to your webserver where in you can do some white box testing on the asp or jsp file and track down all the SPs or tables involved and then go to the DB manually verify all the SPs and track down where updations insertions deletions are done and then once you test ur application with test data agaian fire all the quires you tracked down you can find your data in DB. Database testing - manually, can be done with the help of SQL queries.

Now people might ask, if we have to write queries. How is it manual in any way? I say, everyone & everything has a right or wrong perspective, which one you choose is upto you. But generally DB testing is done by writing SQL queries and then validating those against the requirements. I have seen guys, checking data types manually by clicking and opening every table in SQL Server when this can be done by a simple select statement. Cheers!!!
Database testing is a process working with data that's stored in the database. If we change anything in the frontend and backend then what will the effect on the database. E.g. An table which has stored the records of students name, roll no., class and sections etc. if we delete the students name in front end then what's effect in database. Wheather we test the student name deleted or not from database.

How to test means , Through SQL quary we can test manually, how , i will tell see the below exmple with out using check point we can test.

)connect to the database db_connect("query1",DRIVER={drivername};SERVER=server_name;UID=uidname;PWD=passw ord;DBQ=database_name "); 2)Execute the query db_excecute_query("query1","write query u want to execute"); -Condition to be mentioned3)disconnect the connection db_disconnect("query");
IF any clarification let me know. Database can be tested various ways, If we are usein SQL server then opne the SQL query analyzer and write the queries to retrieve the data. Then verify whether the expected result is correct or not. IF not the data is not inserted into database. We can play with queries to insert, update and delete the data from the data base and check in the front end of the application. IF it is Oracle then open the SQL plus and follow the same procedure. Most of the time we find invalid data. Same way we can test the stored procedure in sql query analyzer and check the result.

What is way of writing testcases for database testing?


For writing test cases in Database first one should define the project name, then module,Bug number,objective,steps/action undertaken,expected result,actual result, then status, priority and severity. --------------------------------------------------------------------------------------------------------------------

How to test data loading in Data base testing


Data Loading represents Loading a data from a source table to target table based on business logic. This is also called as Extraction, Transformation and loading (ETL). For doing this there are lots of tools like Informatica, Data stage, Abinitio and so on... Now I will explain with an example:

If ur Source table has emp_id, Emp_name, Emp_salary,Emp_dept ,Emp_location. The target table has emp_id, Emp_name, Emp_salary. Business logic : you have to load the target table for those employees whose salary > 20,000 So, Now By for this we executing a have the query or to Stored test Sp procedure the check will Stored the be written procedure.. following

1. Check the number of fields the source and target table has 2. Intially before running the SP check whether the target table is empty 3. After executing SP, Check whether the records of employees whose sal>20,000 are loaded 4.Check whether the loaded records are as same as source table records. 5. Check for Null values or some junk values 6. Check the number of records loaded in the target table with COUNT keyword in Oracle Based 1) on situation before running the script, count how many record that has, after running script, count how many records it has based on difference betweeen those count, we can say, how many records were inserted

2) step 1 is not suffucient, to make conform all data is inserted. With the help of step 1, we can come to know howmany record are inserted.

we should check indivedual field in source and destination has same -------------------------------------------------------------------------------------------------------------------what SQL statements have you used in Database Testing?

I said I used select statements most of the times. So, the interviewer took it granted that I am unaware of insert, update and delete statements. Hence it is better to read out whole of the SQL as an answer to this question.
DDLDDL is Data Definition Language statements. Some examples: CREATE ALTER - DROP - TRUNCATE - COMMENT - RENAME - DMLDML is Data Manipulation Language statements. Some examples: SELECT - INSERT - UPDATE - DELETE - MERGE - UPSERT - CALL - EXPLAIN PLAN - LOCK TABLE - DCLDCL is Data Control Language statements. Some examples: GRANT REVOKE - COMMIT - SAVEPOINT - ROLLBACK - COMMIT - SET TRANSACTION - This are the Database testing commands used.thnxAnand Database Testing can use a lot of SQL statements.other than all of them that were already mentioned above, you might want to use stored procedures and triggers as well in order to create test data.Creation of test data is the most critical part of database testing, as well as identifying valid inputs.If you are testing a database service, you will have to use many SQL statements as mentioned above, but if you are testing a stored procedure or a trigger, then select, update, delete are more than enough. Obviously other than joins which are always important.
---------------------------------------------------------------------------------------------------------

what is database testing and what we test in database testing

Data bas testing basically include the following. 1)Data validity testing. 2)Data Integritity testing 3)Performance related to data base. 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 referintial integrity and different constraint. For performance related things you should have idea about the table structure and design. 3

for testing Procedure triggers and functions you should be able to understand the same. ---------------------------------------------------------------------------------------------------------How to use sql queries in WinRunner/QTP
in QTP using output databse check point and database check point , select sQL manual queries option and enter the "select" queris to retrive data in the database and compare the expected and actual

What are the different stages involved in Database Testing


verify the data in the database w.r.t frontend transactions verify the constraint (primary key,forien key ....) verify the performance of the procedures verify the triggrs (execution of triggers) verify the transactions (begin,commit,rollback) Verify wheather the fornt end values are correctly storing in the back end databse by writing the sql queries. Verify the Constraints (Primary key,foreign key, Composite key) check the performance of the Stored Procedurs check for the execution of the Triggers Verify wheather the fornt end values are correctly storing in the back end databse by writing the sql queries. Verify the Constraints (Primary key,foreign key, Composite key) check the performance of the Stored Procedurs check for the execution of the Triggers

how can we write testcases from Requirements..? Do the Requirements represent exact Functionality of AUT
Yes, Requirements should represent exact functionality of AUT.

First of all you have to analyse the requirement very throughly in terms of functionality. Then you have to think about suitable testcase design techniques (Black Box design techniques like Equivalance Partitioning, Boundry Value Analysis, Error Guessing and Cause Effect Graphing) for writing the testcase. By these concepts you should write a testcase which should have the capability of finding the absence of defects 1. 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. 2. What is Database testing? Data bas testing basically include the following. 1)Data validity testing. 2)Data Integritity testing 3)Performance related to data base. 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 referintial 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. 3. How to Test database in Manually? Explain with an example Observing that opertaions, 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). 4. What is data driven test? Ans: Data driven test is used to test the multinumbers of data in a data-table, using this we can easy to replace the paramerers in the same time from deferent locations. e.g: using .xsl sheets. Ans: Re-execution of our test with different input values is called Re-testing. In validate our Project calculations, test engineer follows retesting manner through automation tool.Re-teting is also called DataDriven Test.There are 4 types of datadriven tests. 1) Dynamic Input submissiion ( key driven test) : Sometines a test engineer conducts retesting with different input values to validate the calculation through dynamic submission.For this input submission, test engineer use this function in TSL scriipt create_input_dialog (label); 2) Data Driven Files Through FLAT FILES ( .txt,.doc) : Sometimes testengineer conducts retesting depends on flat file contents. He collect these files from Old Version databases or from customer side. 3)Data Driven Tests From FRONTEND GREAVES : Some times a test engineer create automation scripts depends on frontend objects values such as (a) list (b) menu (c) table (d) data window (5) ocx etc., 4)Data Driven Tests From EXCEL SHEET : sometimes a testengineer follows this type of data

driven test to execute their script for multiple inputs. These multiple inputs consists in excel sheet columns. We have to collect this testdata from backend tables . 5. How to check a trigger is fired or not, while doing database testing? It can be verified by querying the common audit log where we can able to see the triggers fired. 6. How to Test Database Procedures and Triggers? Before testing Data Base Procedures and Triggers, Tester should know that what is the Input and out put of the procedures/Triggers, Then execute Procedures and Triggers, if you get answer that Test Case will be pass other wise fail. These requirements should get from DEVELOPER 7. Is a A fast database retrieval rate a testable requirement? No. I do not think so. Since the requirement seems to be ambiguous. The SRS should clearly mention the performance or transaction requirements i.e. It should say like A DB retrival rate of 5 micro sec. 8. How to test a DTS package created for data insert update and delete? What should be considered in the above case while testing it?What conditions are to be checked if the data is inserted, updated or deleted using a text files? Data Integrity checks should be performed. IF the database schema is 3rd normal form, then that should be maintained. Check to see if any of the constraints have thrown an error. The most important command will have to be the DELETE command. That is where things can go really wrong. Most of all, maintain a backup of the previous database. 9.How to test a SQL Query in Winrunner? without using DataBase CheckPoints? By writing scripting procedure in the TCL we can connect to the database and we can test data base and queries. The exact proccess should be: 1)connect to the database db_connect(query1,DRIVER={drivername};SERVER=server_name;UID=uidname;PWD=pas sword;DBQ=database_name ); 2)Execute the query db_excecute_query(query1,write query u want to execute); -Condition to be mentioned3)disconnect db_disconnect(query); the connection

10. How do you test whether a database in updated when information is entered in the front end? It depend on your application interface.. 1. If your application provides view functionality for the entered data, then you can verify that from front end only. Most of the time Black box test engineers verify the functionality in this way. 2. If your application has only data entry from front end and there is no view from front end, then you have to go to Database and run relevent SQL query. 3. You can also use database checkpoint function in WinRunner. 11. How do you test whether the database is updated as and when an information are added in the front end?Give me an example? It depends on what level of testing you are doing.When you want to save something from front end obviously, it has to store somewhere in the database You will need to find out the relevant tables involved in saving the records. Data Mapping from front end to the tables.Then enter the data from front end and save. Go to database, fire queries to get the same date from the back end.

12. What steps does a tester take in testing Stored Procedures? First the tester should to go through the requirement, as to why the particular stored procedure is written for. Then check whether all the required indexes, joins, updates, deletions are correct comparing with the tables mentions in the Stored Procedure. And also he has to ensure whether the Stored Procedure follows the standard format like comments, updated by, etc.Then check the procedure calling name, calling parameters, and expected reponses for different sets of input parameters. Then run the procedure yourself with database client programs like TOAD, or mysql, or Query Analyzer Rerun the procedure with different parameters, and check results against expected values. Finally, automate the tests with WinRunner. 13. What are the different stages involved in Database Testing verify field level data in the database with respect to frontend transactions verify the constraint (primary key,forien key .) verify the performance of the procedures verify the triggrs (execution of triggers) verify the transactions (begin,commit,rollback) 14. How to use sql queries in WinRunner/QTP ? QTP using output databse check point and database check point ,select SQL manual queries option and enter the select queris to retrive data in the database and compare the expected and actual 15. what is database testing and what we test in database testing? An1: Database testing is all about testing joins, views, inports and exports , testing the procedures, checking locks, indexing etc. Its not about testing the data in the database. Usually database testing is performed by DBA. An2: Database testing involves some in depth knowledge of the given application and requires more defined plan of approach to test the data. Key issues include: 1) Data Integrity 2) Data Validity 3) Data Manipulation and updates Tester must be aware of the database design concepts and implementation rules. An3: Data bas testing basically include the following. 1)Data validity testing. 2)Data Integritity testing 3)Performance related to data base. 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 referintial 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. 16. What SQL statements have you used in Database Testing? The most important statement for database testing is the SELECT statement, which returns data rows from one or multiple tables that satisfies a given set of criteria. You may need to use other DML (Data Manipulation Language) statements like INSERT, UPDATE and DELTE to manage your test data. You may also need to use DDL (Data Definition Language) statements like CREATE TABLE, ALTER TABLE, and DROP TABLE to manage your test tables.

You may also need to some other commands to view table structures, column definitions, indexes, constraints and store procedures. 17. How to test data loading in Data base testing? You have to do the following things while you are involving in Data Load testing. 1. You have know about source data (table(s), columns, datatypes and Contraints) 2. You have to know about Target data (table(s), columns, datatypes and Contraints) 3. You have to check the compatibility of Source and Target. 4. You have to Open corresponding DTS package in SQL Enterprise Manager and run the DTS package (If you are using SQL Server). 5. Then you should compare the columns data of Source and Target. 6. You have to check the number to rows of Source and Target. 7. Then you have to update the data in Source and see the change is reflecting in Target or not. 8. You have to check about junk character and NULLs. 18. What is way of writing testcases for database testing? An1: You have to do the following for writing the database testcases. 1. First of all you have to understand the functional requirement of the application throughly. 2. Then you have to find out the back end tables used, joined used between the tables, cursors used (if any), tiggers used(if any), stored procedures used (if any), input parmeter used and output parameters used for developing that requirement. 3. After knowing all these things you have to write the testcase with different input values for checking all the paths of SP. One thing writing testcases for backend testing not like functinal testing. You have to use white box testing techniques. An2: To write testcase for database its just like functional testing. 1.Objective:Write the objective that you would like to test. eg: To check the shipment that i load thru xml is getting inserted for perticular customer. 2.Write the method of input or action that you do. eg:Load an xml with all data which can be added to a customer. 3.Expected :Input should be viewd in database. eg: The shipment should be loaded sucessfully for that customer,also it should be seen in application.4.You can write ssuch type of testcases for any functionality like update,delete etc. An3: At first we need to go Need to know what tables, stored Then test the functionality of the application.

through procedures

the are

documents mentioned in

provided. the doc.

Simultaneously, start writing the DB testcases.. with the queries you have used at the backend while testing, the tables and stored procedures you have used in order to get the desired results. Trigers that were fired. Based on the stored procedure we can know the functionality for a specific peice of the application. So that we can write queries related to that. From that we make DB testcases also. 19.What is Database testing? An1: here database testing means test engineer should test the data integrity, data accessing,query retriving,modifications,updation and deletion etc An2: Database SQLOpen,

tests are SQLClose,

supported SQLError,

via ODBC SQLRetrieve,

using the following functions: SQLRetrieveToFile, SQLExecQuery,

SQLGetSchema and SQLRequest. You can carry out cursor type operations by incrementing arrays of returned datasets. All SQL queries are supplied as a string. You can execute stored procedures for instance on SQL Server you could use Exec MyStoredProcedure and as long as that stored procedure is registered on the SQL Server database then it should execute however you cannot interact as much as you may like by supplying say in/out variables, etc but for most instances it will cover your database test requirements An3: Data bas testing basically 1)Data validity 2)Data Integritity 3)Performance related to 4)Testing of Procedure,triggers and functions.

include

the data

following. testing. testing base.

for doing data validity testing you should be good in SQL queries For data integrity testing you should know about referintial 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. An4: Data base testing generally deals with the follwoing: a)Checking the integrity of UI data with Database Data b)Checking whether any junk data is displaying in UI other than that stored in Database c)Checking execution of stored procedures with the input values taken from the database tables d)Checking the Data Migration . e)Execution of jobs if any 20. What we normally check for in the Database Testing? An1: 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. An2: Database testing involves some indepth knowledge of the given application and requires more defined plan of approach to test the data. Key issues include : 1) data Integrity 2) data validity 3) data manipulation and updates. Tester must be aware of the database design concepts and implementation rules

Popularity: 5% 1. What we normally check In DB testing we 1.The field 2. Check 3. Indexes are done or not for in the need to size (for Database check Testing? for, validation constraints. related issues)

performance

4. Stored 5. The field size defined in the application is matching with that in the db.

procedures

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.

The database component is a critical piece of any data-enabled application. Todays intricate mix of client-server and Web-enabled database applications are extremely difficult to Test productively. Testing at the data access layer is the point at which your application communicates with the database. Tests at this level are vital to improve not only your overall Test strategy, but also your products quality. In this course you will learn the basics you will need to productively and effectively Test database applications.

Module 1 Database Testing Concepts Primer o The Database Component : What is a Database Application? o Testing at the Database layer o Why should Test professionals know DB Basics? o The DB component:What is a Data-Based Application? o Back end vs. Front End Testing o Examining the datas round trip through the app o Common problems in Relational Databases that affect the Database Application o Testing the Application vs. Testing the DBMS o Knowledge Requirements for Database Testing o Test Plan: Organizing your approach o Data must pass Quality Assurance too! o Test Set up Module 2 Relational Database Basics for Testing o Why should Test professionals know Relational DB basics? o Whats a relational database? o Types of Data Integrity o Lack of data integrity introduces bugs o Identifying Design Defects o Inspecting table structures to reveal design problems o Exploratory Testing: Reading an ERD o Table Relationships: 1-1, 1-many, many-to-many o What to look for when Testing Relational Databases Module 3: Data Normalization Bugs

10

What bugs are caused by improperly normalized databases Understanding Normalization:First, 2nd and 3rd Normal Form Understanding Denormalization Identifying poor design; developing Test cases Module 4: Introduction to SQL o Why should Test professionals know Structured Query Language? o SQL essentials o Basic SQL statements for Testing

o o o o

91. Can u test a website or a web application manually without using any automation tool? As per my idea we can test a web application manually without using automation but its time consuming and might have error so to make our task easy and error free we use automatons tool like Qtp. As for as Manual is concerned we can test Usability, Functionality, Security testing but whereas performance is concerned we cant do it manually accurate 92. What tools are used in Manual testing for bug tracking and reporting? For bug tracking and reporting there are many tools like Rational PVCS Bugzilla clear quest.

93. At what stage in the SDLC testing should be started? Testing Starts from the starting sate of SDLC that is requirement stage where we prepare SRS Or URS DOC. 94. What is mean by designing the application and coding the application? Designing and Testing are two different phases in a software development process(SDLC). 1. Information Gathering 2. Analysis 3. Designing 4. Coding 5. Testing 6. Implementation and Maintenance. If u want answer in Testing terms means STLC, designing test includes preparing Test Strategy, Test Plan and Test Case documents, and testing means executing the test cases and generating Test Reports. Designing the application as per the requirements Designing the application is nothing but deriving the functional flow , alternative flow,How many modules that we are handling, data flow etc Two types of designs are there HLD:

11

In this designing team will prepare functional architecture i.e Functional flow LLD: In this designing team will divide the total application into modules and they will derive logic for each module Coding:writing the course code as per the LLD to meet customer requirements 96. What is the best way to choose automation tool? We use automation only for version wised projects, means if the project comes up with different versions. Once we write the scripts for one version, we can use these scripts with multiple versions with minor changes. So the main advantage of automation is: 1. Saves the time. 2. Saves money. 97. What is the point of reference by which something can be measured? 1. Benchmark 2. Baseline 3. Metric 4. Measure 5. Indicator Baseline 98. what is Concurrency Testing? Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

100. The scenario is while reviewing requirement docs(SRS)if u find or feel any requirement is not meeting the clients requirements whom do you report?and what is your action? When the System Requirement Specification does not meet the clients requirements, it should be intimated to the PL (who prepares the SRS and should be documented in the Test log & analysis of data which should be discussed in the Management Review Meeting. The action is the SRS should undergo a revision thereby updating SRS to match with CRS 101. How to choose a test automation tool? We have to choose depends upon the application complexity & delivery time. 102. Did u come across STUBS and DRIVERS? How did u use these in u r project ? Stub : A piece of code that simulates the activity of missing components. Driver : A piece of code that passes test cases to another piece of code. i will give a gen example.suppose u have 3 modulesA B CA n B r 100% comp.and C is only 50% comp.u r under pressure to comp in a time framewhat u do is u know to build the mod C u need at least 15 daysso u build a dummy mod C which will take 1/2 daysThis is STUB now once all the mod A B and C(dummy) r ready..u integrate them to see how it works..This is a DRIVER

12

81. On what basis you are fixing up the time for project completion? Test strategy; Based on the test strategy and testing Approach 82. How u r breaking down the project among team members? It 1) 2) 3) 4) 5) etc can depend on Number Number of Complexity of Time Duration Team be these of of members following team the casesmodules members Project project experience

the

83. Usually customers wont give all the requirements. How will u manage & collect all the necessary information? Sometimes customer may not produce all the requirements. At this situation Business analyst and project manager will use their experience which they handles this type of projects otherwise we will go through some reference sites where we will observe the functionality and they will prepare use cases and requirements. or I am agree with the above answer. If we really face such a problem then it is better to get information from development team so that we can know the exact info Or else use Ad-hoc testing for the required job. 84. what are the Qualities needed by a software tester? A software tester must have intent of showing the product is not working as specified. Software tester have the basic attitude of showing the presence of errors. He must have perspective of customers i.e he has to use the system as he is the client of the system. He has to strive for the quality. Or Software Tester must has these qualities 1)He/she must observe the problem from both the side say user and programmer. 2)Must has good under standing with other team members . 3)Able to understand programmers view. 4)Once start testing, do not put it remain. 5)First test requirements of the user. 6)Before start testing first analysis the project like ; technology using in project, all the flow etc 85. Did you write test cases of design phase? Yes We can write test cases at the design phase At the time of designing we should be ready with test cases

13

86. In Testing 10 cases you found 20 bugs then how will you know which bug is for which test case? Each Bug Will Have a Unique Bug-ID which would be related to that particular Test Case. We also make use of the Matrix to keep track of bugs and test cases. 87. what is the path for test director,where the test cases are stored ? c:\TDcomdir\TD_projectname\tests\test no Usually test cases are stored in Test Plan in Test director 88. what is mean by test suite? Test suit is set of test cases Group of test cases is nothing but functional(+ve & -ve) and GUI 89. What is the diff. b/w Baseline and Traceability matrix? Baseline : The point at which some deliverable produced during the software engineering process is put under formal change control Traceability : Is used to check if some of the test cases are left out or not in Manual and automated testing. Baseline is nothing but a software specification or functionality that is reviewed or accepted for development. Once the functionality is baseline, we can start developing of the functionality. Where as a Traceability Matrix lists all the functionality or features and the test cases for each feature. By using the traceability matrix we can measure, when to stop testing of the project or application. Generally Traceability Matrix contains: 1. UseCaseID(Functionality/Feature). 2. Description of the Feature. 3. Priority for the Feature. 4. TestCaseIDs for this Feature. (Once if the mapped testcases for each Feature meets Success criteria, then we can stop testing of the project) 5. In which phase is the Feature (Unit,Component,Integration,System) 90. what methodologies you are following? Methodologies are considered in 2 accounts. 1) There are a few methodologies like : v-model,spiral (most common), waterfall, hybrid, prototype, etc depends on the company. 2) Depends on the clients and the requirements. No. 2 is def related to no 1 Methodology means the way we are following while writing test cases . there are different ways like 1. Functional Test cases 2. Equivalence Partitioning Test cases

14

3. Boundary 4. Cause Effect Graphing and Decision table

value

analysis

73. suppose u have raised one bug.u have posted to that concerned developer..he cant accept that is a bug.what will u do in the next stage? If the developer wont accept our sent bug, then we show it to our team leader or we can show it to our superior person. so he/she will go and discuss with developer or else they will conduct one meeting on that. or Sometimes bug not reproducible in Dev Environment at that situation dev doesnt accept we will give him screen shots.If still debate occurs we raise the issue in bug triage meeting 74. Role of Software Test Engineer in Software Company? The role of a software test engineer in company is to find the defect. He/She should have test-to-break attitude. He/She has to test the application taking the customer into mind. He should work hard for quality. 75. Suppose you testing Calculator application and you got problems like 1/1=2, 2/2=1, 3/3=6, 4/4=1, 5/5=10. Now how will you describe the bug title as well as give the bug description? Bug title : Calculation Errors Description: Unable to do the calculations of this application.like the output is giving an undefined/Unstructured format. Here the examples : 1/1=2 Severity : Critical Priority: High/Medium(depends on your Requirement to solve) Bug Title:calculator_functionality_Division Description:Division function is not working properly when the values are(both) same and even. 76. Explain equivalence partitioning with an example? When We have an requirement which has a large class of data split the large class into its subsets For Ex: Sal 10000-45000 Here this is the large class of data equivalence partitioning >take inputs from the below sub classes such as less than 10000 (invalid) between 10000 and 45000 (valid) greater than 45000 (invalid) Instead of choosing values from the large set of information split the inputs into both valid & negative inputs that becomes a subset. this technique is equivalence partitioning

15

77. Explain traceability matrix with an example? Traceability matrix is table which maps each requirement to its functionality in FDS, its internal design in IDS, its code and its test cases. Format is <! /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:"; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; fontfamily:Times New Roman; mso-fareast-font-family:Times New Roman;} pre {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:Courier New; mso-fareast-font-family:Times New Roman;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; msopaper-source:0;} div.Section1 {page:Section1;} >

Requirement--Functionality--Internal design--coding--T.c's R1 P3 in FDS P6 in IDS P4 T13,T14 - -


78. What is the difference between Integration Testing and System Testing? Integration testing will do the completion of unit or module level Testing. System testing is nothing but the application meets the Required specifications or not Or In integration testing individual components are combined with other components to make sure the necessary communications, links and data sharing occur properly. It is not system testing because the components are not implemented in the operating environment. System testing begins one the modules are integrated enough to perform tests in whole system environment.System testing can occur in parallel with integration test, especially with the top-down method. 79. How Could u Present Test Strategy for the Product Testing? Test strategy means that it is a document prepared by quality analyst/project manager. it specifies how to approach to testing team depends upon requirement gatherings, risks involved in our company and customer requirements 80. You may undergone many projects. Do all the projects match up with customers expectations? Any project never matches with 100% requirements. We consider only when it reaches to certain extent Software Testing Interview Questions8

| 0 Comments

16

66. After insert the record in front-end, How will u check the back end by manually? Please explain? Back end Checking is what we call DATABASE TESTING have to know the queries very well. With out queries we will not able to test data base testing. But as a tester we will responsible for test and see the data whether it is stored in back end or not. We dont have permission to do any thing. So what I am coming to tell means select * from condition queries is enough for testing the back end. 67. Do write a separate test case for Regression Testing? If it is Yes, Explain How to write the Test case? Well we are not going to right separate test cases for regression testing. We execute the same test cases on newly modified build which ever failed in previous. OR We are not going to write new test cases. We will select the some of the test cases from test case document, and execute the test cases to check for the bug fixes. Here we selecting the test cases such way that, all the basic functionality test cases, and affected bug test cases. 68. How to do the performance testing manually? Does u have a test case for that? We can test it manually but we dont get accurate result. We dont have separate test cases exactly we will do it with tool i.e. Load runner, Act, Web load. 69. What is the difference between Functional testing and Functionality testing? Functional Testing: The portion of security testing in which the advertised features of a system are tested for correct operation. OR Quality assurance that a web site performs properly. All aspects of the user interface, navigation between pages and off-site, multilingual navigation, etc. are tested. Testing is required in all the current browsers and on the major operating systems and platforms. OR Functional testing is nothing but whether the given function is working or not as per the specifications Ex: field validation, Navigation etc. Functionality Testing is nothing but to check whether our application is equal to customer requirements or not Here we Ex: Error handling testing will Inter do lot system more tests Testing

70. What is Middleware? Can anybody explain me? In the computer industry, middleware is a general term for any programming that serves to glue together or mediate between two separate and often already existing programs. A

17

common application of middleware is to allow programs written for access to a particular database to access other databases. The systematic tying together of disparate applications, often through the use of middleware, is known as enterprise application integration. Or Software that mediates between an applications program and a network. It manages the interaction between disparate applications across the heterogeneous computing platforms. The Object Request Broker (ORB), software that manages communication between objects, is an example of a middleware program 71. Suppose u and your team member is there.your team member (friend) has raised one bug..u dont no about application as well as that functionality of that application.your TL give the task u have to give the Severity & Priority..how can u give the Severity & Priority? I am using Adhoc testing for this type of bugs depends upon past experience i am try to execute the testcase and write the severity and priority of that big. 72. what is JOINTS & REGISTRY in SQL? Joints : Using SQL Joints, you can retrieve data more than one table or view using the keys etc to define an inequality condition Registry : A Windows repository that stores configuration information for a computer. For all the terms on SQL http://www.utexas.edu/its/unix/reference/oracledocs/v92/B105 01_01/win.920/a95490/glossary.htm Plz Visit

65. What kind of testing to be done in client server application and web application? Explain Web Testing During testing Functionality Performance Usability Server Client Security Functionality: In testing Links Internal the functionality of the web sites the following should be tested. links the websites the following scenarios should be considered.

side side

interface compatibility

18

External Mail Broken Forms Field Functional Error message for wrong Optional and mandatory Database Testing will be done on the database Cookies Testing will be done on the client system side, on the temporary internet files. Performance:

links links links validation chart input fields integrity.

Performance testing can be applied to understand the web sites scalability, or to benchmark the performance in the environment of third party products such as servers and middleware for potential purchase. Connection speed: Tested over various Networks like Dial up, ISDN etc Load What is the no. of users per time? Check for peak loads & how system behaves. Large amount of data accessed by user. Stress Continuous load Performance of memory, cpu, file handling etc. Usability : Usability testing is the process by which the human-computer interaction characteristics of a system are measured, and weaknesses are identified for correction. Usability can be defined as the degree to which a given piece of software assists the person sitting at the keyboard to accomplish a task, as opposed to becoming an additional impediment to such accomplishment. The broad goal of usable systems is often assessed using several criteria: Ease of learning Navigation Subjective user satisfaction General appearance Server side interface: In web testing the server side interface should be tested. This is done by Verify that communication is done properly. Compatibility of server with software, hardware, network and database should be tested. The client side compatibility is also tested in various platforms, using various browsers etc. Security: The primary reason for testing the security of an web is to identify potential vulnerabilities and subsequently repair them. The following types of testing are described in this section: Network Scanning Vulnerability Scanning Password Cracking Log Review

19

Integrity

Checkers

Stress testing: Stress testing is a form of testing that is used to determine the stability of a given system or entity. This is designed to test the software with abnormal situations. Stress testing attempts to find the limits at which the system will fail through abnormal quantity or frequency of inputs. Stress testing tries to break the system under test by overwhelming its resources or by taking resources away from it (in which case it is sometimes called negative testing). The main purpose behind this madness is to make sure that the system fails and recovers gracefully this quality is known as recoverability.Stress testing does not break the system but instead it allows observing how the system reacts to failure. Stress testing observes for the following. Does Does Is it Etc. it save its state or it just hang and freeze able to recover from the does it or does last good crash suddenly? it fail gracefully? state on restart?

Compatability Testing A Testing to ensure compatibility of an application or Web site with different browsers, OS and hardware platforms. Different versions, configurations, display resolutions, and Internet connect speeds all can impact the behavior of the product and introduce costly and embarrassing bugs. We test for compatibility using real test environments. That is testing how will the system performs in the particular software, hardware or network environment. Compatibility testing can be performed manually or can be driven by an automated functional or reg The purpose of compatibility testing is to reveal issues related to the products interaction session test suite.with other software as well as hardware. The product compatibility is evaluated by first identifying the hardware/software/browser components that the product is designed to support. Then a hardware/software/browser matrix is designed that indicates the configurations on which the product will be tested. Then, with input from the client, a testing script is designed that will be sufficient to evaluate compatibility between the product and the hardware/software/browser matrix. Finally, the script is executed against the matrix, and any anomalies are investigated to determine exactly where the incompatibility lies. Some typical compatibility tests include testing On various client hardware Using different memory sizes and hard On various Operating In different network With different printers and peripherals (i.e. zip drives, USBs, etc.) your application: configurations drive space Systems environments

20