All about Test Plan .....

Test Plan
1. If I update an existing test in Test Plan, do I also need to update the test in Test Lab?
No, you don�t need to update the test in Test Lab. The changes will carry through to the test in the Test Lab.
However, if you�re running a test in Test Lab and decide to make some changes to the test, upon closing out of the test, you will be prompted if you want to save the changes to the test (in Test Plan). If you choose no, the changes will only appear in the specific test that you had run when you made the change.
2. How do I print off a checklist of my tests?
• To print off a list of your tests (excluding steps), go to the view menu under the Test Plan tab.
• Select test grid. You'll need to set up the screen to display the data you want. This is acheived by using the filter and select columns buttons.
• When the screen is displaying what you want, then with the mouse right click anywhere on the test grid and use the save as Excel option to save the test list.
• Open the file in Excel which may cause the import wizard to appear. If that happens, select the defaults.
• Print the file in Excel
3. How do I print off my tests including the test steps?
• First, make sure you close your WORD application and any WORD documents
• Click on the Test Director's "Tools" button and select "Document Generator". A document generator window opens.
• From the window's favorite droplist, select the document that you need. Make sure the document is appearing in the favorite field before the next step.
• Click on "Full Document" button. Upon selecting the button, Test Director will begin generating your report in WORD. When the processing is completed, a word document will appear on the screen.
Test Lab
1. If I did not run a specific test in a test set, do I need to update anything in Test Director?
If you didn't run a test, you do not need to document anything. The fact that a test was not run is noted by the absence of a run date.
Whenever you run a test, a record of that test is created. So, if you ran a test five times, the test will have five separate run dates.
2. How can I view all the test runs for a specific test in a test set?
First, locate the test in the test set. By double clicking anywhere in the row of the test in the execution grid, another screen appears where the run history for the test is displayed

1.Who all are having the rights to detect and report the defects?
Software developers
Testers
End users
2.What are the main things want to be considered while reporting the bug?
Description about the bug
Software version
Additional informations necessary to reproduce and repair the defect
3.Describe about mailing defect data
Connecting TestDirector to your e-mail system lets you routinely inform development and quality assurance personnel about defect repair activity.
4.What is report designer?
Its a powerful and flexible tool that allows you to design your own unique reports
5.What is the use of graphs in TestDirector?
TestDirector graphs help us visualize the progress of test planning,test execution,and defect tracking for our application,so that we can detect bottlenecks in the testing process.

6. What is the use of Test Director software?
TestDirector is Mercury Interactive.s software test management tool. It helps quality assurance personnel plan and organize the testing process. With TestDirector you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects.

7. What is the use of Test Lab in Test director?
Test Lab can be used to create a test set. You can add one or many test cases into a test set. Then run all test cases in a test set together and change the status as pass/fail.
8. How many tabs in TestDirector and explain them?
There are 4 tabs available in Testdirector.
1. Requirement - used to track the customer requirenments
2. Testplan - used to design the testcases & to store the testscripts
3. Testlab - used to exectue the testsets & track the results
4. Defect - used to log a defect & to track the logged defects
9. Explain the process of Test Director?
Step 1: Introducing Testing Provides you with an overview of the Test Director workflow and familiarizes you with the Test Director user interface.

Step 2 : Getting Ready to Test Shows you how to create a master test plan based on your goals, resources, and time constraints.

Step 3 : Creating a New Project Shows you how to create a new database and customize it to meet the requirements of your application.

Step 4: Creating a Test Plan Shows you how to analyze the sample application and break it down into subjects. It also helps you build a test plan tree that represents the hierarchical relationship of the subjects.

Step 5: Designing Tests Shows you how to define test steps. It also helps you decide whether to automate a test or perform it manually.

Step 6: Running Tests Shows you how to organize test execution by building test sets, and how to execute manual and automated tests.

Step 7: Tracking Defects Shows you how to report and track defects detected in an application.
10. Which tool is best to do Regression Testing?
Both WinRunner and QTP are used to test regression testing. Regression testing is 'testing the application on modified build to ensure that whether the bugs are fixed or not, and fixed bugs giving any side effects to existing functionality and further functionality' is called as regression testing.
11. How to import data from an excel sheet to Test director?
Master plan is the 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.

Differences between static testing and dynamic testing?

Define static testing

Answer1: In software development, static testing, also called dry run testing, is a form of software testing where the actual program or application is not used. Instead this testing method requires programmers to manually read their own code to find any errors.
Static testing is a stage of White Box Testing

Answer2
The Verification activities fall into the category of Static Testing. During static testing, you have a checklist to check whether the work you are doing is going as per the set standards of the organization. These standards can be for Coding, Integrating and Deployment. Review's, Inspection's and Walkthrough's are static testing methodologies.


Differences between static testing and dynamic testing

Q: What is the difference between static and dynamic testing?

Difference number 1: Static testing is about prevention, dynamic testing is about cure.

Difference number 2: The static tools offer greater marginal benefits.

Difference number 3: Static testing is many times more cost-effective than dynamic testing.

Difference number 4: Static testing beats dynamic testing by a wide margin.

Difference number 5: Static testing is more effective!

Difference number 6: Static testing gives you comprehensive diagnostics for your code.

Difference number 7: Static testing achieves 100% statement coverage in a relatively short time, while dynamic testing often often achieves less than 50% statement coverage, because dynamic testing finds bugs only in parts of the code that are actually executed.

Difference number 8: Dynamic testing usually takes longer than static testing. Dynamic testing may involve running several test cases, each of which may take longer than compilation.

Difference number 9: Dynamic testing finds fewer bugs than static testing.

Difference number 10: Static testing can be done before compilation, while dynamic testing can take place only after compilation and linking.

Difference number 11: Static testing can find all of the followings that dynamic testing cannot find: syntax errors, code that is hard to maintain, code that is hard to test, code that does not conform to coding standards, and ANSI violations.