Testing Interview Questions

1. Who will change the status of bug?
As soon as tester finds a bug he logs the bug as new status and assigns to developer. Developer working on that bug changes the status as open. When developers feels its not required fixing at that moment he changes the status as differed. If he completed working on that he changes the status as close and assigns the report to tester. Tester retests the bug and confirms the status as close. We come across many more statuses such as duplicate, not reproducible, to be fixed, critical, blocked, need clarification. We can use the status according to the bug.

2. Is it possible to have a defect with high severity and low priority or vice verse?
When the development team prepared the modules and they sent it for testing and after doing some part of testing then a bug raised in the first module its severity is minor and at the same time in the second module a bug raised and its severity is major. We come to know by the next day the client is coming for inspection and he wanted to get the first module prepared. So at this time less severity bug gets high priority and high severity bug gets low priority.

3. What is defect life cycle in manual testing?
Defect Life Cycle: Defect detection
Reproduce the defects
Assign the bug to the developer
Bug fixing
Bug resolution
Regression

4. What is difference between bug resolution meeting and bug review committee? Who are the participants in bug resolution meeting and bug review committee?
Bug Resolution meeting: It is conducted in presence of test lead and developers where developer gives his comment whether to correct the bug at this time or later and test leader accepts or rejects developer comments and even they decide what methods should be chosen correct the error so that in regression test no bug should be reported and it should not effect other application.

Bug Review committee: It is often conducted by test lead, project managers in the presence of client, where they decide as to what errors should be considered as bugs and what severity level it should be treated as.

5. How to give bug title and bug description for ODD devision?
Assumption: ODD number devision fails
Bug Title: ODD number fails
Bug Description: Open calculated window
Enter an ODD number
Click divide by [/] button
Enter another Odd number
Enter or click equal button in calculated window
Observe the result
Expected results:
Quotient displayed is correct
Actual result
Quotient displayed is incorrect.

6. What is build interval period?
In some companies builds are delivered from development team to the testing team to starts the system testing. For example a new product ABC is being released to the testing team so the development team will deliver a build to the testing team. Now testing will do the testing and then will release the product to the client. now there is a new version of product coming up with the name ABC1 and is being released to the testing team so this will be the second build and time between these two builds will be called as build interval.

7. What is difference between End to end testing and system testing?
End to End testing : This is the macro end of testing. This testing mimics the real life situations by interacting with real time data, network and hardware etc.

System Testing: this is the process of testing end to end business functionalities of the application(system) based on client business requirements.

In the system testing we are taking sample test data only, where as in the end to end testing we are taking real time data(for a sample) and interacting with network and hardware.,

8. How would you say that a bug is 100% fixed?
In quality world we cannot say bug is 100% fixed or 50% fixed. If the bug is fixed then in new version we do regression testing to make sure that bug fix doesn’t have any impact on old functionality.

9. How to post a bug?
Bugs are posted with the tools these tools are known as bug tracking tools. Custom designed tools, build specific for companies bug format, accepts the details of the issue from the testers as follows
1. Bug Id(tool generates the ID)
2. Bug description
3. Steps to reproduce the bug
4. Software and hardware environment
5. Status (New, reopen ….)
6. version Id of the build
7. Assign to
8. Severity
9. Priority
10. tester name and data execution

Test engineers fills the above fields in the tools and the tool acts as a central repository and tracks the entire bug life cycles.

10. What are the different types of bugs we normally see in any of the project?
1. User interface defects
2. Boundary related defects
3. Error handling defects
4. calculation defects
5. improper service levels
6. Interpreting data defects
7. race condition(comparability and inter system defects)
8. Load conditions (Memory leakages under load)
9. hardware failures
10. Source bugs

Share This

1. What is the difference between use case, test case, test plan?
Use Case: It is prepared by Business analyst in the Functional Requirement Specification(FRS), which are nothing but a steps which are given by the customer.

Test cases: It is prepared by test engineer based on the use cases from FRS to check the functionality of an application thoroughly

Test Plan: Team lead prepares test plan, in it he represents the scope of the test, what to test and what not to test, scheduling, what to test using automation etc.

2. How can we design the test cases from requirements? Do the requirements, represent exact functionality of AUT?
Yes, requirements should represents exact functionality of AUT.
First of all you have to analyze the requirements very thoroughly in terms of functionality. Then we have to thing about suitable test case design technique [Black Box design techniques like Equivalence Class Partitioning (ECP), Boundary Valve Analysis (BVA),Error guessing and Cause Effect Graphing] for writing the test cases.
By these concepts you should design a test case, which should have the capability of finding the absence of defects.

3.How t0 launch the test cases in Test Director and where it is saved?
You create the test cases in the test plan tab and link them to the requirements in the requirement tab. Once the test cases are ready we change the status to ready and go to the “Test Lab” Tab and create a test set and add the test cases to the test set and you can run from there.
For automation, in test plan, create a new automated test and launch the tool and create the script and save it and you can run from the test lab the same way as you did for the manual test cases.
The test cases are sorted in test plan tab or more precisely in the test director, lets say quality centers database test director is now referred to as quality center.

4. What is the deference between a bug and a defect?
When tester verifies the test cases, all failed test cases are recorded as bugs directed for necessary action and recorded in defected reports. As a testing point of view all fail test cases are defects as well as found bugs. While development point of view if product doesn’t meet the software requirement specifications or any other features that is to be required, it is defect in the system. Who found this feature is not meeting his requirements, he call it is bug in that product.

5. How can we explain a bug, which may arrive at the time of testing. Explain?
First check the status of the bug, then check whether the bug is valid or not then forward the same bug to the team leader and then after confirmation forward it to the concern developer.

6. What do you mean by reproducing the bug? If the bug was not reproducible, what is the next step?
Reproducing a bug is as simple as reproducing a defect. If you find a defect, for example click the button and the corresponding action didn’t happen, it is a bug. If the developer is unable to find this behavior he will ask us to reproduce the bug.
In another scenario, if the client complaints a defect in the production we will have to reproduce it in test environment.

7. How can you know bug is reproducible or not?
A bug is reproducible if we can reproduce it, If we cannot reproduce it, it is not reproducibles in which case we will do further testing around it and if we cannot see it we will close it, and just hope it would never come back ever again.

8. On which basis we give priority and severity for a bug and give one example for high priority and low severity and high severity and low priority?
Always the priority is given by our team leader. Tester will never give the priority.
For example,
High severity: hardware bugs application crash
Low severity: User interface bugs.
High priority: Error message is not coming on time, calculation bugs etc.
Low priority: Wrong alignment, final output wrong.

9. How is traceability of bug follow?
The traceability of bug can be followed in so many ways.
1. Mapping the functional requirement scenarios(FS Doc) - test cases (ID) - Failed test cases(Bugs)
2. Mapping between requirements(RS Doc) - Test case (ID) - Failed test cases.
3. mapping between test plan (TP Doc) - test case (ID) - failed test cases.
4. Mapping between business requirements (BR Doc) - test cases (ID) - Failed test cases.
5. Mapping between high level design(Design Doc) - test cases (ID) - Failed test cases.

Usually the traceability matrix is mapping between the requirements, client requirements, function specification, test plan and test cases.

10. What will be the role of tester if bug is reproduced?
When ever the bug is reproduced, tester can send it back to the developer and ask him to fix it again. If the developer cannot fix the bug once again and if the tester sends the bug back to the developer, the third time the tester can make the bug as deferred i.e. he can reject the build(.exe)

Share This

1. What is difference between master test plan and test plan?
Master plan is a document showing the planning for whole of the project i.e. all the phases of the project whereas the test plan is the document required for only testing people.

2. What is the main purpose of storing requirement in Test Director?
In test director(Requirement Tab) we stores our project requirement documents according to our modules or functionality of the applications. This hepls us to makes sores that all requirements are covered when we trace developed Test case/ test script to the requirements.

3. What are the 3 views and what is the purpose of each view?
The 3 views of requirements are:
1. Document view-tabulated view
2. Coverage view- establish a relationship between requirement and the test associated with them along with their execution status. Mostly the requirements are written in this view only.
3. Coverage analysis view-show a chart with requirement associated with the test and execution status of the test.

4. How many types of reports can be generated using Test director?
Reports on test director displays information about the test requirements, the test plan, test runs and defect tracking. Reports can be generated from each Test director module using the default settings, or you can customize them. When customizing a report, you can apply filters and sort conditions, and determine the layout of the fields in the report. You can further customize the report by adding sub reports. You can save the settings of your reports as favorite views and reload them as needed.

Reports available in Requirements Module:
standard Requirements:
Tabular
Requirements with Coverage tests
Requirements with coverage tests and steps
Requirements with associated defects

Reports available in Test plan module:
Stan dared test planning
Subject tree
Tests with covered requirements
Tests with associated defects

Reports available in test lab module:
Current test set
Cross test set with tests
Current test set with failed test runs
Cross test set with failed test runs

Reports available in defects module:
Standard defects
Tabular defects
Defects with associated test and runs
Fixed or rejected defects detected by current user
Opened defects and assigned to current user

5.What does Test Grid contains?
The test Grid displays all the tests in a test director projects
The test grid contains the following key elements
Test grid tool bar, with buttons of commands commonly used when creating and modifying the test grid.
Grid filter, displaying the filter i.e. currently applied for a column
Description Tab: Displaying a description of the selected test in the test grid.
History Tab, displaying the changes made to a test. For each change the grid displays the field name, data of change, name of the person who made the change, and the new value.

6. How will you generate the defect ID in test director? Is it generated automatically or not?
When you will add a new defect and submit it to test director it will generate a new ID for that defect.
The defect ID automatically generate after we click submit button.

7. Difference between TD8.0 and QC8.0?

8. How do you ensure that there are duplication of bugs in test director?

In the defect tracking window, at the top we can find the similar defect icon, If we click after writing our defect, if any of the tester already added the similar defects it will tell else we can add.

9. How you integrated your automated scripts from test director?

When you work with winrunner you can choose to save your tests directly to your test director database or while creating a test case in the test director we can specify whether the script in automated or manual. And if it is automated script then test director will build a skeleton for the script that can be later modified into one which could be used to test the AUT.

Share This

1. How many types of tabs in Test Director?
There are 4 tabs available in Test Director.
1. Requirement
2. Test plan
3.Test lab.
4. Defect

We can change the name of Tabs, as we like. Test Director enables us to rename the Tab. In TD there only 4 tabs are available.

2. How to generate the graphs in Test Director?
The generation of graphs in the Test Director that to Test Lab module is:
1. Analysis
2. graph.
3. Graph Wizard.
4. select the graph type as summary and click the next button.
5. Select the show current tests and click the next button.
6. Select the define a new filter and click the filter button.
7. Select the tests set and click on the ok button
8. select the plan: subject and click on the Ok button.
9. select the plan:status.
10. select the test set as X axis.
11. Click the finish button.

3. How can we export multiple test cases from TD in a single go?
If we want to export it to any office tools
1. Select the multiple steps/cases you need.
2. Right click > save as and proceed.

4. How to upload test cases from excel into test director?
First we have to activate excel in test director with the help of adding page. After activation we can view the option as ‘export to test director’ in excel under tools tab.
If you select the export to test director pop up dialog box opens the following process should be followed i.e.,
Enter
1. URL of Test Director
2. Domain name and project name
3. user name and password
4. Select anyone of these 3 options: Requirements or test cases or defects
5. Select a map option. a)select a map b)select a new map name c)create a temporary map.
6. Map the test director to corresponding excel. Map the field whatever you mention in excel.

These are the required steps to export the excel into TD.

5. Does anyone know of any integration between Test director and Rational Robot?
Any idea on the technical feasibility of such integration and level of effort would also be interesting?
Test Director is software management tool. It is a Mercury Interactive Product.
Rational Robot is a Rational product. It comes included with ‘test manager’ module for software management.
Integrating the test director and Rational Robot is not feasible.

6. Explain the project tree in test director?
Project Tree in test director : Planning tests –Create test– execute tests–tracking defects.

7. What is coverage status, what does it do?
Coverage status is percentage of testing covered at a given time. If you have 100 test cases in a project and you have finished 40 of test cases out of total test cases then your coverage status of project is 40%. Coverage Status is used to keep track of project accomplishment to meet the final deadline of the deliverables.

8. Difference between data validation and data integrity.
Data Validation: We check whether the input data/output data is valid in terms of its length, data type etc..
Data Integrity: We check out database contains only accurate data. We implement data integrity with the help of integrity constraints. So in data integrity we check whether the integrity constraints or implemented correctly or not

9. What are the uses of filters in test director?
Limits the data displayed according to the criteria you specified.
For Ex: You could create a filter that displays only those tests associated with the specified tester and subject.
Each filter contains multiple filter conditions. These are expressions that are applied to a test plan tree or to the field in a grid. When the filter is applied, only those records that meet the filter conditions are displayed.
You create and edit filters with the filter dialog box.This opens when you select the filter command. Once you have created a filter, we can save it for future use.

10. How do we generate test cases through test director?
Test lab we do the design step. Design grid we create parent child tree.
Ex: Database operation (test name)
1. Delete an order
Description: Click delete button to delete the order.
Expected results: Order is deleted.
Pass/Fail:
Update an order
create an order.

Share This

1. What is meant by test lab in test director?
Test lab is a part of test director where we can execute our test on different cycles creating test tree for each one of them. We need to add test to these test trees from the tests, which are placed under test plan in the project. Internally test director will refer to this test while running then in the test lab.

2. Can you map the defects directly to the requirements(Not through the test cases) in the test director?
In the following methods is most likely to used in this case:
Create your Req.Structure
Create the test case structure and the test cases
Map the test cases to the App.Req
Run and report bugs from your test cases in the test lab module.

The database structure in test director is mapping test cases to defects, only if you have created the bug from Application. test case may be we can update the mapping by using some code in the bug script module(from the customize project function), as per as i know, it is not possible to map defects directly to an requirements.

3. how do you run reports from test director. Does any one have good white paper or articles?
This is how you do it
1. Open the test director project
2. Displays the requirements modules
3. Choose report
Analysis > reports > standard requirements report

4. Can we upload test cases from an excel sheet into test director?
Yes go to Add-In menu test director, find the excel add-In, and install it in your machine.
Now open excel, you can find the new menu option export to test director. Rest of the procedure is self explanatory.

5. Can we export the file from test director to excel sheet. If yes then how?
Requirement tab– Right click on main req/click on export/save as word, excel or other template. This would save all the child requirements

Test plan tab: Only individual test can be exported. no parent child export is possible. Select a test script, click on the design steps tab, right click anywhere on the open window. Click on export and save as.

Test lab tab: Select a child group. Click on execution grid if it is not selected. Right click anywhere. Default save option is excel. But can be saved in documents and other formats. Select all or selected option

Defects Tab: Right click anywhere on the window, export all or selected defects and save excel sheet or document.

6. How many types of tabs are there in test director. Explain?
There are four types of tabs are available

1. Requirement : To track the customer requirements
2. Testplan : To design the test cases and to store the test scripts
3. test lab : To execute the test cases and track the results.
4. Defect : To log a defect and to track the logged defects.

7. How to map the requirements with test cases in test director?
1. In requirements tab select coverage view
2. Select requirement by clicking on parent/child or grandchild
3. On right hand side(In coverage view window) another window will appear. It has two tabs
a) Tests coverage
b) Details
Test coverage tab will be selected by default or you click on it.
4. Click on select tests button a new window will appear on right hand side and you will see a list of all tests. You cans elect any test case you want to map with your requirements.

8. How to use test director in real time project?
Once completed the preparing of test cases
1. Export the test cases into test director( It will contained total 8 steps)
2. The test cases will be loaded in the test plan module
3. Once the execution is started. We move the test cases from test plan tab to the test lab module.
4. In test lab, we execute the test cases and put as pass or fail or incomplete. We generate the graph in the test lab for daily report and sent to the on site (where ever you want to deliver)
5. If we got any defects and raise the defects in the defect module. when raising the defects, attach the defects with the screen shot.

9. Difference between Web Inspect-QA Inspect?
QA Inspect finds and prioritizes security vulnerabilities in an entire web application or in specific usage scenarios during testing and presents detail information and remediation advise about each vulnerability.
Web Inspect ensures the security of your most critical information by identifying known and unknown vulnerabilities within the web application. With web Inspect, auditors, compliance officers and security experts can perform security assessments on a web enabled application. Web inspect enables users to perform security assessments for any web application or web service, including the industry leading application platforms.

10. How can w add requirements to test cases in test director?
Just you can use the option of add requirements.
Two kinds of requirements are available in TD.
1. Parent Requirement
2. Child requirements.

Parent Requirements nothing but title of the requirements, it covers high level functions of the requirements

Child requirement nothing but sub title of requirements, it covers low level functions of the requirements.

Share This