Testing Interview Questions

1. Where are the testplan attributes stored?

Testplan attributes are stored in the testplan initilization file, testplan.ini, in silk test installation directory.

2. How to assign attribute values to test cases?

1. Make sure your testplan is open.
2. Click on the test case for which you want to assign an attribute value.
3. Click Testplan/detail menu. The Testplan Details dialog box shows up.
4. Click the test attribute tab.
5. click the component field. The dropdown list shows up with all values of “Component”.
6. Select one of the values in the dropdown list.
7. Click OK.

3. What is a test frame?

A test frame is a file that contains information about the application you are testing. information stored in atest frame will be used as references when Silk test records and executes testcases. A test frame is stored in an include file with file extension .inc.

4. How to create a test frame?

1. make sure your Web browser is active and showing your web application home page. Do not minimize this web page window.
2. Make sure your test project is open.
3. Click File/New Menu. the New dialog box shows up.
4. Select the test frame radio button.
5. click Ok. The new Test frame dialog box shows up with a list of all active web applications.
6. Select your web application.
7. Enter a test frame name. For example: HomeFrame. inc.
8. Review the window name. It should be the HTML title your web application. You can resume it, if needed.
9. Click OK to close the new test frame dialog box.
10. Click File/save menu.

5. What is stored in a test frame?

A test frame is a text file, which records the following types of information gor a web application:

1. Comment: Commentary information.
2. wMain Window: A string constant to identify your application’s homepage.
3. Home page window: An object of class Browser child window that holds application home page.
4. sLocation: The URL of the application’s home page.
5. sUsername and dpassword: user name and password if needed to login to your web application.
6. BrowserSize: A pair of values to indicate the size of the browser window.
7. Homepage objects: A list of all objects on the homepage, such as HtmlImage, HtmlText, HtmlLinks, etc.

6. How DOM browser extension identify a web application UI objects?

A web application UI object is identified in 2 parts:

1. Identify the web browserwindow where the web application is running. For example, a web browser window can be identified as “Browser.BrowserChild(”Yahoo Home page”).
Another web browser window can be identified as “Browser.BrowserChild(”Google Home page”).
2. Identify the web UI object based on the HTML element that represents the UI object. For example, an image in a web page can be identified as “HtmlImage(”Yahoo Logo”)”; A hyperlink in a web page can be identified as “HTMLLink(”Site Map”)”; The full identification of a web application UI object is the concatenation of the browser window indentification and the HTML element identification. For example, the yahoo logo image is identified as:
Browser.BrowserChild(”Yahoo Home Page”).HTMLImage(”Yahoo Logo”). The site map link is identified as: Browser.BrowserChild(”Google Home Page).HTMLLink(”Site Map”).

7. What is the syntax of UI object identifier used by DOM extension?

The DOM browser extension uses the following syntax for web UI objects:
Browser.BrowserChild(”page_titile”).html_class(”object_tag”)
1. “page_title” is the title of the web page, defined by the HTML “TITLE” tag.
2. “object_tag” is the label of the HTML element. How a HTML element is labeled depending on the type of HTML element.

8. What is multi-tagging?

Multi-tagging is a technique used by the DOM browser extension to identify a web page UI object. Whenever possible, DOM extension inserts more than one tag into the object identifier in following format:
Browser.BrowserChild(”page_title”).html_class(”caption_tag|window_tag”)
1. “Caption_tag” is the caption of the HTML element.
2. “#index_tag” is the index of this HTML element, counting from the beginning of this page of the same class of HTML elements.
3. “window_tag” is the window identifier.

9. How to add objects of other pages to a test frame?

If your Web application has pages other than the home page, you should also record their page objects into the test frame:
1. Make sure your web browser is active and showing another page of your web application.
2. Make sure Silk test is running.
3. Click File/Open menu.
4. Select your test frame file. For example:HomeFrame.inc.
5. Click OK to open the test frame.
6. Click Record/Window Declarations menu. The Record Window declarations dialof box shows up.
7. Click your web application window. Web page objects are recorded in the Record Window Declarations dialog box.
8. Press Ctrl_Alt to pause the recording.
9. Click “Paste to Editor” button. All recorded objects will be inserted into the test frame.
10. Repeat this for other web pages, if needed.

10. How to specify a browser extension to a web application?

1. Run Silk test.
2. Open Internet explorer(IE).
3. Enter the URL of the web application.
4. Leave the IE window with the web application. Don’t minimize the IE window.
5. To back to Silk test window.
6. Select Basic workflow bar.
7. Click Enable extersions on the workflow bar.
8. The enable extensions dialog will show up. Your web application running in the IE window will listed in the dialog box.
9. Select your web application and click select.
10. The extension settings dialog will show up. Click OK to enable the DOM browser extension.

1. How to open an existing Silk Test project?

A) 1. Run Silk Test
2. Select File Menu
3. Select Open Project
4. Select the project
5. Click OK
6. Silk Test will open the selected project.

2. What is a Silk test TestPlan?

A) The Silk Test testplan is an outline that provides a framework for the software testing process and serves as the point of control for organizing and managing your test requirements. A testplan consists of two distinct parts; an outline, which is a formatted description of the test requirements, and statements, which are used to connect the test plan to Silk test scripts and test cases that implement the test requirements.

3. Where is a testplan stored?

A) Silk Test testplan is stored in a file with .pln file extension.

4. How to create and edit a test plan?

1. Make sure your project is open.
2. Click the files tab in the project explorer.
3. Right click the plan folder.
4. click New file
5. An untitled testplan file opens in the silk test testplan editor.
6. Click file/save menu to save the testplan.

5. What are the types of text lines in a test plan file?

A testplan file contains text lines. There are 5 types of text lines in a testplan file:
1. Comment - Marked in green color: Providing commentary information.
2. Group Description - Marked in black color: Providing description for groups of tests. tests in a testplan can be grouped into multiple levels of groups.
3. Test description - Marked in blue color: Providing descriptions for individual test.
4. Testplan statement - Marked in dark red color: Providing relations to link scripts, testcases, test data, closed sub testplans or an include file to the test plan.
5. Open Subplan file marker - marked in magenta color: Providing relations to link sub testplans to be included in a master testplan.

6. How to create group and sub group descriptions in a testplan?

In a testplan, each text line starting from column 0 represents a top level group description. To create sub group description:

1. Move the cursor the next line below the top level group description.
2. Click Outline/Move Right.
3. The text line will be indented to the right to be come a sub group description.

7. What are testplan attributes?

Test plan attributes are user defined characteristics to be associated with test group descriptions and/or test descriptions. You search, identify, and/or report test cases based on values of the different attributes.

8. What are the default testplan attributes?
Silk Test offers you 3 predefined default attributes:
1. Category: The type of testcase or group of testcases. For example, you can use this attributes to categorize your test groups as “Boundary value tests”, “Navigation tests”, etc.
2. Component: The name of the application modules to be tested.
3. Developer: The name of the QA engineer assigned to develop the testcase or group of testcases.

9. How to define new testplan attributes?

1. Make sure your test project is open.
2. Click Testplan/define attributes menu. The define attributes dialog box shows up. You should see predefined default attributes: Category, Component, and Developer.
3. Click the New button. The New attribute dialog box shows up.
4. Enter a name for your new attribute. For Example: “Level” to indicate the complexity level of test cases.
5. Select an attribute type: Normal, Edit, or Set.
6. Click OK.

10 How to define values for a testplan attribute?

You must define values for a testplan before using it:
1. Make sure your test project is open.
2. Click Testplan/define attribute menu. The define attributes dialog box shows up. You should see predefined default attributes and other attributes defined by yourself.
3. Select an attribute. For example, “Component”. The values box should be empty.
4. Enter a value in Add box. For example, “Catalog”.
5. Click Add. Value “Catalog” should be inserted into the Values box.
6. Repeat the last two steps to add more values.

1. What is Silk Test?

Silk test is a software testing automation tool developed by Segue Software, Inc.

2. What is the Segue Testing Methodology?

Segue testing Methodology is a six-phase testing process:

1. Plan : Determine the testing strategy and define specific test requirements.
2. Capture : Classify the GUI objects in your application and build a framework for running your tests.
3. Create : Create automated, reusable tests. Use recording and/ or programming to build test scripts written in Segue’s 4Test language.
4. Run : Select specific tests and execute them against the AUT.
5. Report : Analyze test results and generate defect reports.
6. Track : Track defects in the AUT and perform regression testing.

3. What is AUT?

AUT stands for Application Under Test.

4. What is Silk Test Host?
Silk test Host is a silk test component that manages and execute test scripts. Silktest Host usually runs on a seperate machine different than the machine where AUT is running.

5. What is Silk test Agent?
Silk test Agent is a silk test component that receives testing commands from the Silk test Host and interacts with AUT directly. Silk test Agent usually runs on the same machine where AUT is running.

6. What is 4Test?
4Test is a test scripting language used by silk test to compose test scripts to perform automated tests. 4Test is an object-oriented fourth generation language. It consists of 3 sets of functionalities:

1. A robust library of object-oriented classes and methods that specify how a testcase can interact with an application’s GUI objects.
2. A set of statements, operators and datatypes that you use to introduce structure and logic to a recorded testcase.
3. A library of built-in functions for performing common support tasks.

7. What is the DOM browser extension?
Document Object Model (DOM) browser extesion is a silk Test addon component for testing Web applications. DOM browser extension communicates directly with the web browser to recognize and manipulate objects on a web page. It does this by working with the actual HTML code, rather than relying on the visual pattern recognition techniques currently employed by the Virtual Objects (VO) extension.

8. What is the VO browser extension?
Virtual Object (VO) browser extention is a silk test add-on component for testing Web applications. VO browser extersion uses sophisiticated pattern recognition techniques to identify browser-rendered objects. The VO extention sees Web pages as they appear visually; it does not read or recognize HTML tags in the Web application code. Instead, the VO extension sees the objects in a web page; for example, links, tables, images and compound controls the way that you do, regardless of the technology behind them.

9. What is Silk Test project?
A silk Test is a collection of files that contains required information about a test project.

10. How to create a new Silk Test project?
1. Run Silk Test.
2. Select Basic Workflow bar.
3. Click Open Project on the Workflow bar.
4. Select New Project.
5. Double click Create Project icon in the New Project dialog box.
6. On the Create Project dialog box, enter project name, and your project description.
7. Click OK.
8. Silk Test will create a new subdirectory under Silk Test project directory, and save all files related to the new project under that subdirectory.

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

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)