The TestDirector Testing Process

TestDirector offers an organized framework for testing applications before they are deployed. Since test plans evolve with new or modified application requirements, you need a central data repository for organizing and
managing the testing process. TestDirector guides you through the requirements specification, test planning, test execution, and defect tracking phases of the testing process.

The TestDirector testing process includes four phases:
Specifying             Planning     Running    Tracking
Reqirements                 Tests           Tests        Tests

Introducing TestDirector

Application testing is a complex process. TestDirector helps you organize and manage all phases of the application testing process, including specifying testing requirements, planning tests, executing tests, and tracking
defects.
In this lesson, you will learn about:
➤ The TestDirector Testing Process
➤ Starting TestDirector
➤ The TestDirector Window
➤ The Mercury Tours Sample Web Site

Test Plan

Test plan is a strategic document in order to do testing.
it consists of test plan id, reference documents,Revision
history,Test schedules,Test Item,Test
process,Resources,Risks and mitigations,Training..those type
of info..

What exactly ad-hoc testing is? At what situation .

It's a random testing It means testing a application without proper test plan.It's carried out at the end of the project when all the test cases are executed.To check the application randomly. or it's carried out in CMM 1 level company where test are executed without planning

Testing the application randomly beyond the requirement to avoid the bug flow at the end users place is called ADHoc TESTING.

its a negative type of testing
we will never write any test cases for ADHOC.
if u found any bugs in adhoc try to convert into functionality/integration/system level bug
to re-test that bug we are going to write the Test Case because in future we may expect that bug.

What is acceptance testing?

In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience. UAT can be done by in-house testing in which volunteers or paid test subjects use the software or, more typically for widely-distributed software, by making the test version available for downloading and free trial over the Web. The experiences of the early users are forwarded back to the developers who make final changes before releasing the software commercial.

Most of the time it is tested by beta tester or end user(depends on company policy)  to know if the application is working as expected.

Testing which is done to enable the customer/user whether to accept the product or not. it is done by end users.

What is meant by cyclomatic complexity? Explain With Example?

It is used to measure the complexity of software process& it<br>is used to measure how many test cases are passed in the<br>application

Cyclomatic Complaxity comes under white box testing.<br>It means best path searching. To measure logical Complaxity <br>of a prog.<br>for ex.<br><br>1-main()<br>2-if(a>1)<br>3{<br>------<br>------<br>}<br>4-else<br>5-{<br>-------<br>-------<br>}<br>}<br><br>Now a diagram would drawn from top as it would start from 1.<br>underneath it would be 2. and 2 would have two edges i.e. 3 <br>and 4. they would futher combine to form 5.<br><br>2,3,4 & 5 would make close region while outside would <br>become open region..<br><br>the arrows joining would be edges 2 would become predicate <br>node. while others are simple nodes.<br><br>it has got a formula:<br><br>v(g)=Node-edges+2<br>v(g)= 5-5+2<br>v(g)=2<br>v(g)= predicate node+1<br>v(g)=1+1<br>v(g)=2

How do you use boundary value analysis testing for evaluating the password ?

Boundary Value Analysis for testing password.<br><br>As per rule boundary value Analysis must have SIx Conditions MIN-1, MIN, MIN+1<br>MAX-1, MAX, MAX+1<br><br>For user id when can apply same for password it works like this<br>lets have condition password min 4 char max 10 char in length.password can be any thing since password depends on userid.<br><br>MIN-1<br>User ID : master<br>password : abc<br>result :Should not accept should popup msg "enter Correct Password".<br><br>MIN<br>User ID : Master<br>password : abcd<br>result : Should accept<br><br>MIN+1<br>User ID : Master<br>password : abcd<br>result : Should accept<br><br>MAX-1<br>User ID : Master<br>password : 123456789<br>result : Should accept<br><br>MAX<br>User ID : Master<br>password : abcd123456<br>result : Should accept<br><br>MAX+1<br>User ID : Master<br>password : abcd1234567<br>result : Should not accept should popup msg "enter Correct Password".