Hai friend I am raj,
           Don?t worry about the future of Black Box tester.
You remember one thing testing is must because without 
testing client cannot believe the product or application.

Actually Black box testing reveals the behavior of the 
application in a systematic way.See the current market 
trend of testing. Testing will be there forever and ever 
until the computer becomes obsolete.

Hi There,

Testers should feel proud of their profession. How, see 
below.

Domain knowledge is important , Developers may not posses 
that but QA engg will.

Entire system Arch is understood by QA and others have less 
scope for the same.

Hello friend,
              u know testers r the supreme authority bacause
without their approval any software can not be launched into
the markrt/client.And yes there is a good future in testing
field.

nitin9360@yahoo.com

STLC means it starts from the preparation of test plan, 
test case and ends with product release. Meanwhile we'l b 
involved in some other types of testing. Major tasks will b 
done in STLC are as follows,

1. Test Plan Preparation
2. Test Case Preparation
3. Execution of TC
4. Analyze the Result
5. Defect Report Preparation
6. Regression Testing

hai,
 STLC means software testing life cycle.it begin depends on 
SDLC.
But STLC having phases it's starts from 
Test planing.
Test Development
Test Execution
Defect Repoting
Result Analysis.

STLC means Software Test life cycle, it starts with 
Test Initiation
Testplan preparation
Test design
Test Execution------------>Test Report
Test Closure

I hope this will help u .to understand each activity under 
the test cycle.

u can reach me @ rami.cheers@gmail.com


Test Requirements 

? Requirement Specification documents
? Functional Specification documents 
? Design Specification documents (use cases, etc) 
? Use case Documents 
? Test Trace-ability Matrix for identifying Test Coverage

Test Planning

? Test Scope, Test Environment
? Different Test phase and Test Methodologies
? Manual and Automation Testing
? Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc
? Evaluation & identification ? Test, Defect tracking tools

Test Environment Setup

? Test Bed installation and configuration
? Network connectivity?s
? All the Software/ tools Installation and configuration
? Coordination with Vendors and others

Test Design
? Test Traceability Matrix and Test coverage
? Test Scenarios Identification & Test Case preparation
? Test data and Test scripts preparation
? Test case reviews and Approval
? Base lining under Configuration Management

Test Automation

? Automation requirement identification
? Tool Evaluation and Identification.
? Designing or identifying Framework and scripting
? Script Integration, Review and Approval
? Base lining under Configuration Management

Test Execution and 
Defect Tracking

? Executing Test cases
? Testing Test Scripts
? Capture, review and analyze Test Results
? Raised the defects and tracking for its closure

Test Reports 
and Acceptance

? Test summary reports
? Test Metrics and process Improvements made
? Build release
? Receiving acceptance

I hope this will help u .to understand each activity under 
the test cycle.

u can reach me @ rami.cheers@gmail.com


Test Requirements 

? Requirement Specification documents
? Functional Specification documents 
? Design Specification documents (use cases, etc) 
? Use case Documents 
? Test Trace-ability Matrix for identifying Test Coverage

Test Planning

? Test Scope, Test Environment
? Different Test phase and Test Methodologies
? Manual and Automation Testing
? Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc
? Evaluation & identification ? Test, Defect tracking tools

Test Environment Setup

? Test Bed installation and configuration
? Network connectivity?s
? All the Software/ tools Installation and configuration
? Coordination with Vendors and others

Test Design
? Test Traceability Matrix and Test coverage
? Test Scenarios Identification & Test Case preparation
? Test data and Test scripts preparation
? Test case reviews and Approval
? Base lining under Configuration Management

Test Automation

? Automation requirement identification
? Tool Evaluation and Identification.
? Designing or identifying Framework and scripting
? Script Integration, Review and Approval
? Base lining under Configuration Management

Test Execution and 
Defect Tracking

? Executing Test cases
? Testing Test Scripts
? Capture, review and analyze Test Results
? Raised the defects and tracking for its closure

Test Reports 
and Acceptance

? Test summary reports
? Test Metrics and process Improvements made
? Build release
? Receiving acceptance

STLC means software testing life cycle this process 
stararts with test initiation
     test planning
     test design
     test execution
     reporting the bugs
     test closure.

1.Test Statergies
2.Test Plan
3.Test Cases
4.Execution Test Cases
5.Bug Ananlysis
6.Reporting the Bug
7.Regression Testing

Vinodh Anandhan
Software Tester
Exceed Technologies (P) Ltd.,
Chennai

STLC stands for Software Testing Life Cycle
It is a process of conducting sofware testing, means after 
programmer conducted intergration testing by using white 
box testing, the intergrated software build is coming to 
overall developed software testing.

The project manager is initiate the STLC processs
the phases of STLC
1. System test initiations
2. System test Planning
3. System test design
4. System test execution
5. System test Reporting
6. System test closure

explanation of STLC

1.System test initiations: in the the PM is initiates the 
whatever testing tools are available (either mannual or 
automation tools), with respect to specific custumet 
requirement 
2. test planning: schedule the which type of testing tools 
is allocate a specific tester to test the module in the 
developed project.(simply distribute the work to different 
testers based on their experience) and allocate the time to 
complete the work.
3. test design: means prepare test cases for each and every 
verified object are correctly working or not w.r.t customer 
requirement.
4.test execution: means the particular object is working or 
not as per customer requiremnt. means test is pass or fail 
or find any defect are informed to the development section 
for once again correct the coding part
5. System test preparing: after programmer correct the 
code, we can retest them 
6. test closure: after completion of all object test 
execution the PM is closed the test.

1.requirements
2.use cases
3.test plan
4.test case
5.test case execution
6.report analysis
7.bug analysis
8.bug reporting

these steps are involved in software testing life cycle.

pardeep16d@gmail.com

Mr.rami reddy's answer is absolutley true. I ask you please 
follow that answer. Its in deatailed.

(software test engineer-II)

Stages of STLC :

1. Test Initiation or Test Planning :
Contents of Test Plan :
a) Scope of testing.
b) Functionalities to be tested and not to be tested.
c) Resource Planning, Scheduling.
d) Test Strategies, Test Deliverables, Test metrics
Defnition, defect metric definition.
e) Areas to be automated, and area not to be automated.
f) Evaluation of automated tools and selection of them.
g) Risk and contigency plans.

2. Test Design : Is nothing but preparation of test case
document.
Contents in Test Design :
a) Scope of test.
b) Test Scenario.
c) Test Procedure.
d) Test Cases.
e) Test data.

3. Test Execution : Execute the test cases and record actual
behaviour of the application.

4. Result Analysis : Compare Actual and Expected behaviour
of application if both are matched consider test case pass
otherwise test case is failed.

5. Bug Tracking : Consider all failed test cases as defects
and track them in a separate doc that is called as defect
profile doc.

6. Defect Reporting : Defect profile doc is send to PM and
Developer for the purpose of rectification.

1.	Test Requirements
2.	Test Planning
3.	Test Environment Setup
4.	Test Design
5.	Test Automation
6.	Test Execution
7.	Defect Tracking
8.	Test Reports and Acceptance

As the SDLC is "software Developement life Cycle" like that
STLC is the "Software testing life cycle" and this is
clearly mean to lifecycle which is totally based on the
testing of the Software.

I m giving a simple idea on it which will be very easy to
understand for everybody .
SDLC is mainly based on :-
 
Requirement analysis
function specification
testcase execution
Bug reporting
make ready for implementation

A)Requirement Analysis :-
Analyze the requirement ,and understand what is the main
Goal of the Project.

B)Functional specification :-
How can we get the right Output of fulfill the Outcome.

C)Testcase Execution :-
 on which way we can test this software to get the maximum
errors.

d)Bug report :-
 Report the error to the development team and also if you
have any idea/solution on the  error then you can also
suggest them.

E)Make Raddy to Implement:-
  this stage is for final implementation ,you have to make
conform whether is there any error exist or not.and also
mentioned this error is managable or may crash the system.
can we take the Risk here to deliver  the Product.

grammar should be check before you post it.

test plan: Road for entire testing activity.
test case:set of produre which we execute your find out defects.
test execution:running the test case,after approval the test
lead.fail/pass information stored in test log.
defect tracking:failed item carried to defect tracking.
reports:result analisys,test graphs preparation.

test plan:road map for entire testing activity

software testing life cycle. it's template
1. test plan
2. test design
3. test execution
4. track & management
planing done by manager
design done by developer
execution done by tester

Defect life cycle is also called as bug life cycle. It has 6
stages namely
1.new: found new bug
2.assigned: bud assigned to developer
3.open : developer is fixing the bug
4.fixed : developer has fixed the bug
5.retest: tester retests the application 
6.closed/reopened: if it is ok tester gives closed staus
else he reopens and sends back to developer.

1. Check for the specifications which are recommanded for 
(like phone's size and color, no. of buttons and its size).
2. Check for the buttons working status.
3. Check for the logo printed on phone
4. once connection is given dial tone should be there
5. Telephone internal connection must be fine
6. Telephone must be Checked(Mark of Tested)
7. Telephone should have facility to Increase or decrease 
of ring volume
8. we should recieve msgs from other end once the 
connection is given

I think some kind of lazy interviewers throw this knid of 
non-sense questions. It is very clear to everybody that We 
do not go for testing until we are clear with each and 
every piece of functionlity. In this scenario they throw 
open-end questions like this and want to see the fun that 
is going to happen. Questions like these put the tester to 
more pressure. They force us to assume something about the 
shit and expect some kind of miracles in terms of 
testcases. So drill him on telephone with question.

Thanks
Jagadeesh

You are 100% Correct Jagadeesh!!!
But Testers are being faced these type of quite often.
How to face them

Metrics: is nothing but a measurement analysis.Measurment 
analysis and Improvement is one of the process area in CMM 
I L2.

Performance Testing:-testing the present wroking condition 
of the product

Regression Testing:-Regression Testing is checking for the 
newly added functionality causing any erros interms of 
functionality and the common functionality should be stable 
in the latest and the previous versions

Performance Testing
     Testing the application  how speed is is working
Estimation of response time of server/CPU.
Perfromence of the application depends on the technology 
used to built the software.
The network capability(BandWidth).
Server capacity to handle the max. number of requests per a 
time.
Performance testing is divided into three tests again
1.Load Testing
2.Stress Testing
3.Volume Testing
Perfromance testing is very important  in WebApplications
,E-Commerce applications,Online banking applications..etc.

Regression Testing:-Regression Testing is checking for the 
newly added  or defect fixed functionality causing any 
erros interms of functionality and the common functionality 
should be stable in the latest and the previous versions

  If you still have any doubt feel free to mail me at :  
rajendra_penumalli@yahoo.com
or call me:9885162742

performance testing is done to check for real time impact of
load, stress & volume on the application, when all the
modules are ready and is working as an complete application. 

Regression testing is done to check for the impact of the
fixed bug, new added features either on single module or all
the module. this is done till alpha testing.

Alpha Testing:-It is conducted at the Developer sight by 
end users 


Beta Testing:-It is conducted at the end users site

If the software is Application then Alpha testing will be done.
Alpha Testing:
              If the testers and real customers combinedly
test the software in development site then it is called
Alpha testing.

If the software is product then Beta testing will be done.

Beta Testing:
             If the testers and model customers combinedly
test the software in customer site,then it is called Beta
testing.

Alpha and Beta testing concepts are different from Product 
based company and a Service based company. 

In a Product based company:
Alpha Testing defines as the testing which is done at the 
developer's site by the testers.
Beta testing is the testing done by the tester by 
generating the customer's environment.

In a Service based company:
Alpha testing is the testing conducted by customers at 
Developer's site. 
Beta Testing is the process of giving the product to 
customers and let them do the testing at their environment.

Note: 
Simple fact, if ur company is Product based company, u 
don?t have any customers as such. U developed ur won 
product and sell in open market. Whoever buys ur product is 
ur customers. So u usually tries to generate the possible 
customer?s environment for testing both Alpha and Beta


Correct me if I m wrong!!!

Alpha Testing: Particular part of an application is tested 
by enduser.

Beta Testing: Whole application is tested by enduser

Alpha Testing 

Tested at developer site by customer.
Developer "looks over shoulder" and records errors & usage 
problems.
Tests are conducted in a controlled environment.

Beta Testing 

Conducted at one or more customer sites by end user of 
software.
Live application environment cannot be controlled by 
developer.
Customer records all problems encountered and reports to 
developer at regular intervals.

alpha testing is conducted by real customer, this test is 
done in the development site, in this test involved few 
developers, few testers,and some ofcustomer site people, 
this test is suitble for applications.

beta testing is conducted by model customer, this test is 
done in the customer site, suitble for products.

Alpha testing-- Simulated or actual operational testing by 
potential users/customers or an independent test team at 
the developers'site, but outside the development 
organization.

Beta testing--operational testing by potential and/or 
existing users/customers at an external site not otherwise 
involved with the developers, to determine whether or not a 
component or system satisfies the user/customer needs & 
fits within the business processes. Beta testing is ofen 
employed as a form of external acceptance testing for off-
the-shelf software in order to acquire feedback from the 
market.

Alpha Testing:Testing of a s/w pruduct or system conducted 
at the developer sites by the customer.

Beta Testing:Conducted at the more than one customers by 
the end user of delivered s/w product.

Alpha testing is done by end users in development site,this 
test is suitble for application.                         
beta testing is done by real customers in customer site, 
this is suitble for 
products.                                                
The different between application&product.
application is used by with in the company,but product is 
used globally.

alpha testing means where the test going to be conducted
with out customer intervention

and beta testing is where the test is to be conducted in
customer presence.

if u want set the 9th action as the first action, in 
keyword view drag that 9th action and drop at first

hi,
This is nice question 

In my thought,

First check the actions are dependable or not . If 
dependable we cannot convert.

If not change the 9th action as a 1st action by using QTP 
batch testing tool.

Go to Action0 folder in you test folder,
Open the Action0 script and change it...

cooooooool man

To get run 9 th action make sure that that action is 
reusable action by default every action will be non 
reusable. to make it reusable go to Edit>Action Properties >
If you waish edit the action name and mark the check box.
In keword view go to Insert > Call to existing actions then 
insert the 9 th action make it to run first followed by 
next scripts (actions)

free feel to contact stil more...........

i think it is possible using the recovery scenario mechanism
at the Post Recovery Scenario we have to select the options
from which point on wards we have to run out test.

i answered this one but intervier says wrong ,

if u know the answer give me reply

You have to go to the settings tab and in the run settings 
reduce the time that the system shouls wait before it goes 
to another iteration (2000 by default) and uncheck nthe box 
for popup window when there is  error.I am not having qtp 
access as i speak so i gave a rough idea.

Write the top of the script
"ON ERROR RESUME NEXT"

There was a method in QTP to continue from the next step
once U got the error 
              
              (OR)

Prepare the Recovery Manager file depends on the req.

Go To File->settings->Run Tab->
select the "proceed next action iteration" in the list box 
when errors occur during run session.
Just try it it may be work.

By using Recovery Scenario Manager it is possible. suppose
there is error in 3rd line for that there is a error msg box.
we will post that msg box by using  recovery scenario. so if
error msg box is displying, by default it accepts and go to
the  next line.

For Recovery Scenario Manger extension is .qrs

tools>recovery scenario manager>new>.............
in case u r not select the add to current test in the
recovery manager then we will go for 
test> properties> recovery>add(+)>ok


      if there is any error ply tell the ..............

I agree with nagesh :
use this.....

"ON ERROR RESUME NEXT"

ON ERROR RESUME NEXT is the best answer

I think we can use the exception handler!!!

Question is not clear

If you are talking about if the browser is not displayed on 
desktop

you can use this code to open a browser

SystemUtil.Run "C:\Program Files\Internet 
Explorer\IEXPLORE.EXE"

please give ans

If browser(xxxx).Exist then
   browser(xxxx).close
End if

The following code can be used in order to close all the IE 
browsers:

SystemUtil.CloseProcessByName "IEXPLORE.EXE"

While Browser("CreationTime:=0").Exist
    Browser("CreationTime:=0").Close
Wend

QTP Tip1: The first browser that opens receives the 
value "CreationTime" = 0, the second browser 
receives "CreationTime" = 1, and so on...

i think using 
recovery.setactivationmode "disable"

I tried using this method but not get it usefull.Please 
provide another answers or tell us how to use this method

we need to create a .qrs(recovery scenario file)file & 
activate that file to all the tests...by using recovery 
scenario manager...

or else ...we can give "ON ERROR RESUME NEXT" as the 
starting of the script...

This can be resolved by changing your browser setting to low
security or creating such environment and save the same as
script by generating script.

types of reviewing testcases depends upon company standards,
viz..,
peer review,team lead review,roject manager review.
Some times client may also review the test cases reg what is
approach following for project

After preparation of testcases project manager will release
software release note in that Document there will be URL 
path  of the website link from from that we will receive 
the build 
   
correct me i am wrong 
 sirisha

In case of web server projects, you will be provided with 
an URL or a 192.168.***.*** (Web address) which will help 
you access the project using a browser from your system. 

In case of Client server, the build is placed in the VSS 
(Configuration tool) which will help you get the .exe 
downloaded to your computer. 

Please mail me if I am wrong. Roopesh1980@msn.com

Modules or a unit are coded by Developer and once its 
finished coding, these modules or units are delivered to 
the Configuration Management Team (CMT). This team is the 
dedicated team who works only on configurations of the 
project. They are sometime called as SDE - System 
Development Engineer. They collect all these modules or 
units and run the CM application to construct the built (I 
don't how they run this thing). Once the built is 
constructed, SDE guys informed the Project Manager that the 
built is ready for Testing. In turn, the PM informs the 
Tester that the built is ready and gives the path of the 
location of the built and to start the testing. 
This process follows for all the builds as the project 
progress.

I dont know the exact answer.
But I think as per the question,
If a tester gets this much of builds,
It is an Iterative software model used in the company and 
for every iteration they are releasing a build to client 
and that should be tested by the tester.

Please correct me If Iam wrong.

Tester gets the initial build from the Dev.Manager...he 
tests the same n logg the bugs...dev team fix the bugs n 
sends the new build with newly added functionalities..