Hi,

 Requirements,test plan,run test, defects are mandatory 
fields in TD.if it is wrong let me know 



Thanks&Regards
siddu

TD has 3 mandatory fields..
1. Run tests 
2.Plan tests--->for creating test palns and test cases.
3.track defects

Test Director mainly have four grids
1.Requirements
2.Test plan
3.Testlab
4.Defect

TD is web based tool .Its not client-server tool ,Its like 
a client-server tech.

this is with respect to saritha,ur answer is wrong it is a 
client server not web based tool...
it will maintain clint server architechure where server is 
the database with stores the test information,and client is 
qc center machine by which the data stored will be retirved 
n the server n client r communicating with active x 
controls...

Hello Xyz and saritha,

Test Director is web based as well as client-server tool.We 
can access TD by web browser only.

cheerz,
kiran kumar

Latest version of Td is QC 9.0 (Quality center)

Ms. saritha i am asking about TD version before coming QC

In td 8.0 is the last version after 8.0 it comes Qc 9.0

The latest Version is HP Quality Center 9.2.

Hi
Latest Version Of QC is 9.5.

In TD,In the requirment tab two  views are available
1.Document View
2.Coverage View

Thanq saritha
I heared about there r tree view and log view is it right
if not correct it

The both answers above are mistake.
There are three types of views:
Document view
Coverage view
Coverage Analysis view

can u ravi briefly explain all the views,n their 
importance...thanx in advance

Requirements Views:
1. Requirements Tree View
2. Requirements Grid View
3. Requirements Coverage view
4. Coverage Analysis View

Test Plan Views:
1. Test Grid View
2. Test Plan Tree View

Test Lab Views:
1. Test Sets Tree View
2. Test Sets Grid View

This question doesn't make any sense. But still i will try
to give information as much as possible.

1) Using keyword view you can do parametrization.
2) Using VB script you can do that.
3) By passing arguments from one script to other you can
parametrize.

Dose it make sense? :)

Types of Parametarizations are:
1.Through Keyword View
2.Through Expert View using Data Table Methods by using 
Import and Export Methods
3.Through Data Driver
Correct if i am wrong

Types of  parametarization
Through flat files
through Keyboard
through excel sheet
through frontend grids

no parametrization types
but passing values by keyword view, vb scripting, similar 
to data driven approach

Test fusion reports is nothing but test results.

Once a tester has run a test, a TestFusion report displays
allaspects of the test run: a high-level results overview,
an expandableTree View of the test specifying exactly where
application failuresoccurred, the test data used,
application screen shots for every stepthat highlight any
discrepancies, and detailed explanations of eachcheckpoint
pass and failure. By combining TestFusion reports
withQuickTest Professional, you can share reports across an
entire QAand development team.

If the script is saved with per action mode:
script is saved with .mts xtension(module test script)
repository is saved with .mtr xtension(module test 
repository)

If the script is saved with shared repository mode:
Filles will be stored with .tsr xtension(test shared 
repository)

library files will be stored with .vbs xtension
test results will be stored with .xml xtension
test batch files will be stored with .mtb xtension(module 
test batch)
recovery file will be stored with .qrs xtension(quick 
recovery scenario)
action templates will be stored with .mst xtension
test data files(if it is excel)will be stored with .xls 
xtension.

Regression testing:

Re execution of a selected test case on modified build to 
ensure bug fix work and occurances of side effects is 
called regression test.

Retesting:

Re executing the same test more than one time with multiple 
test data.it is also called iterative or re-testing.


For Example: There are 10 testcases to be passed for a 
requirement. But 10th testcase failed and tester raised a 
defect in the defect log.

Retesting: After the above defect is fixed, tester need to 
execute the 10th testcase to check the expected result for 
the same.

Regression Testing: After the above defect is fixed, tester 
need to execute the 20% of above testcases by selecting 
randomly to make sure that existing functionality is not 
broken because of the above fix.

Vidya is absolutely correct with her answer above !

I FEEL THAT BOTH REGREESION AND RE TESTING ARE SAME

regression testing:
     regression testing means reported bug is resolved or 
not this is called regression testing.
retesting means to test diffrent combinaions of data i,e 
called retesting testing.....

Regression Testing:Whenever there is a change/modification 
in the code of an application may be due to change in 
requirement or bug fixing the testing carried out in this 
event to avow that application is not behaving in an 
aberrant manner is called regression testing.

Re-testing:This testing is done with both positive and 
negative inputs i.e. executing one fuctional test case with 
different sets of data.

Plz correct me if i'm wrong

Shijath Ali
9945327269

Both of these are more or less the same.  Checking the 
basic functionalities of the build after deploying the code 
is called smoke or sanity testing.

Hope im rite.

Quality Assurance: It is a group of management, where they 
monitor and improve the entire development process, monitor 
whether they are able to meet the agreed standards of the 
company and whether problem issues were found and dealt.

Quality control: It is the actual testing for each and 
every phase of an application to meet customer requirements 
or to maintain the quality in an application.

QA : Measuring and monitoring the software development     
process is called Quality Assurance.

QC: The validation of deliverables i.e., outcomes after 
process is called Quality Control.

QA

* QA make sure you are doing the right things  in right way.
* QA is Developing,orgnising the best quality processes.
* QA is the process Related 
* QA is the Preventive Process.

QC

* QC  makes sure the results of what you have done and what 
you expected.
* QC means implementing the process developed by former 
team.
* QC is the actual testing of the software.
* QC is corrective process.

Quality Assurance:
Software QA involves the entire software development PROCESS
- monitoring and improving the process, making sure that any
agreed-upon standards and procedures are followed, and
ensuring that problems are found and dealt with. It is to
'prevention

Quality Control:
A set of activities designed to evaluate a developed work
product.Quality Control makes sure the results of what
you've done are what you expected.

Verification is doing the right job.
Validation is doing the job right.
Implies, if there is an application to test, verification 
means, testing the correct application, whereas, validation 
means, testing the application correctly with correct 
testing methods.

1.verification means examing the document and finding a 
error
2.am i building product right
3.it is low level activity
4.methods used in  inspections,walkthrough,per review
validation means excuting the document and finding a defect
2.am i building  right product
3.it is high level activity
4.methods used in black box and white box

verification:verification is building a right producu/right 
application 
validation: validation is building the product/application 
right

Software testing is used in association with verification 
and validation:

* Verification: Have we built the software right (i.e., 
does it match the specification)?.Its process based.
* Validation: Have we built the right software (i.e., is 
this what the customer wants)?.Its product based.

Verification is process oriented. It involves the process 
and procedures followed. Its a preventive action.
Eg: walkthrough, inspection, review checklists...

Validation is product priented. It is ths actual testing of 
the product.