Hi


   Test Metrics

   1. Cost
   2. Time
   3. Test Effectiveness
   4. Bug Severity


sun_ramprasad@yahoo.com

flash is a . net product so we are able to test the
application using QTP

1) invokeapplication"path of the application 
example(c:\program files\ieexplorer.exe)"


2) SystemUtil.Run "application path(C:\Program 
Files\Opera\Opera.exe)"

a)	In QTP possible to open the application two types. They are
b)	Invoke the application: That give the invoke application
syntax
c)	That is ex (c:\program files\path of the application)
d)	Second one is the system utilities only 
e)	It is automatically open the application

Hi This is K.Chandra Sekhar
If any query then send to mail ndra_143@yahoo.co.in
I am taking the testing projects FAQS class
Call 9246540049/65880049
In Hyderabad

reviews serve to purity the software work products that 
occur as a result of analysis, design , and coding.

Review meeting conducted by weekend discuss the task .task 
means work. What we have to do in the past week and know 
the status of the work.
We can say completeness and correctness of the document.
In these review meeting discussed in 3 points
Whether to accept the work product without further 
modification.
== reject the work product due to errors.
== accept the work product

Review means comparing the relative documents inorder to 
check their completeness and correctness.

Ex:Test cases review,Bug report review,requirements 
review,code review.....

Hi

   To find the Errors through evaluation.









sun_ramprasad@yahoo.com

the process of  developing test cases can help to find 
problems inthe requirements or design of an application,
since it requires completely thinking through the operation 
of the application
A test case is a document that describes an input, action 
or event and an expected response to determine if a feature 
of an application is working correctly.

Database testing is testing whether the data is being stored
by the system in a manner where the data is not compromised
by updating, restoration, or retrieval processing. Basically
this testing is done using SQL commands to check whether the
correct data is entering in the tables and fields. Database
can be any database used for your software either Oracle, My
SQL & so on

Actually I don't know, Because I put fake experience. I 
never did these things. So, how can I tell you about those?
-----Fun-----
To trace out whether the process is going on without any 
interruption. By reviewing, we can get an insight what is 
the status of the project, what are different things, are 
there any obstacles while completing our project. If any 
problems are arised, workarounds can be implemented.

After completion of functional and regression testing, a
review  meeting is conducted.  In that meeting, the Test
Lead will review all modules that are in application to
assess defect density.  The regression test will be
conducted once again on the module, which has more defects
found by test engineer.

After completion of final regression, the application will
undergo for User Acceptance Test.

If I am wrong, please let me know.

J. Sambasivarao
9948280248
jampani_sivarao@yahoo.com

After Completion of Regression Testing (i.e GM) :

1. A meeting with the testing resources to make sure there 
are no MBF bugs and to measure the depth of not-MBF bugs 
and to make sure whether all the requirements are met.

2.Test report will be prepared and reviewed.If there is any 
rework then that will also be taken care and the final 
version will be sent to the client.

3. Retrospection Meeting with Resources,Manager and Quality
(process Oriented) people. The purpose of Retrospection 
Meeting is "We need to learn about what we did and how we 
did" - This meeting is very important and useful because 
through this meeting we can learn lot of things from our 
mistakes.The duplicate and FAD bugs may be raised because 
of insufficient knowledge on the product and not going 
through the document properly.So, Defect Prevention methods 
can also be discussed here.

4. Analyze the defect Density to make sure the following 
things..
* defect density within the limit
* defect density greater than the limit 

4. The final Build will be sent for UAT and in parallel an 
internal Audit for process stuff will be done by the QA 
people.

If it is automatable, then go for auto. Means, If there are 
things, which we have to/can test repeatedly with different 
values, then go for auto. Once the appli became stable then 
go for auto. While regression also. First Manul.t should be 
completed on the appli. 
Generally, large web applications are the best candidates 
for auto. If it is Insurance, Banking, Finance application, 
then it best suits for auto process.
--------
Post your opinions on this -whether this is understandable 
or not.

The tests, which have to be tested more than one time or
repeatedly for many times with valid and invalid test data,
then we have to go for test automation on these tests to
assess consistency of that particular function in that
particular application.

If I am wrong, please let me know

J. Sambasivarao
9948280248
jampani_sivarao@yahoo.com

Master data occur in the OLTP system and that can't change 
regularly,When the changes are occured in the OLTP 
system,that changes can be handle by the dimension 
tables.Such type of dimensions is called Slowly changing 
dimensions.

There are three types of dimensions
TYPE1(Maintain only current data)
TYPE2(Maintain complete historic data)
TYPE3(Maintain one historic data)

Dimensions that change over time are called Slowly Changing 
Dimensions. There are three types namely,
1) Overwriting the old values
2) Creating an another additional record
3) Creating new fields

Provide fast and effective way of monitoring key measures.

Scorecard is a concept used for measuring a company's 
activities in terms of its vision and strategies, to give 
managers a comprehensive view of the performance of the 
business.

testing strategy is the sequence of steps for testing which
involve sthe testing methodologies.Testing Methedologies are
Block box and white box testing. 



  Testing strategies are unit testing,integration, system
,security ,performance etc testings

Test Strategy defines all the steps for handling a 
particular project.

A test stategy document would generally contain the 
following

* The scope (complete cycle,only few features,new features 
and major bugs etc) and duration of the testing should be 
clearly set/defined.
* The No: of ppl required for the project is determised  
from the duration and scope of the testing.
* The ppl/resourses should be identified and their role 
defined (manager,test lead,tester etc)
* Tools and infrastructure required/deployed.
* The testing process decided for this project  
      *defining the entry criteria,exit criteria,
      *The different phases planned and
      *the types of testing  
(Sanity,functionality,stress,regression etc)covered at the 
different stages of the product life cycle and also in each 
phase and the order in which it will be executed.

i.e initially(Alpha stage) the product could be very 
unstable with very few basic features.Then the scope of the 
testing would only be test against requirement and 
functionality testing etc. AD-Hoc,regression,stress testing 
etc will not be done in this stage. But as the product 
reaches a more mature stage (beta) all the phases/types of 
testing would be covered.

testing strategy is the sequence of steps for testing like 
unit,system,integration ,performance,user acceptance which
involve the testing methodologies.but Testing Methedologies 
are the type of testing
Block box and white box testing. 



  Testing strategies are unit testing,integration, system
,security ,performance etc testings