on using tacebillity maatrix

The coverage of testcases can be decided through 
Tracebility Matrix with which we can explain the process of 
through requirements of the users. Generally the 
tracebility matrix may include the following:

1. User Requirements
2. Reviews statements (SRS)
3. Scenarios (Test Conditions)
4. Test Stratagey
5. Test Technique
6. Test Sumarry Report

          If any doubts pls free contact me my id is 
dsrinivas1982@gmail.com and pls send question to me also so 
that I can enrich my knowledge on testing concepts.

By using tracibility matrix we will decide whether are 
requirements are covered or not .

In tracibility matrix we will have:
a)REq id :
b)Testcases id.
Here we will map the requiremnts to the testcases & ensure 
that all requirements are covered.

by using RTM(requrment tracibility matrix)we can decide all 
the test cases r coverd r not

 this is to check wether all the functanalites r coverd r 
not.
1.sr.no
2.reqirments ID.
3.Description
4.unit testcase ID
5.System testcase ID
6.impact analysis
7.bidirectional impact  

 for based on this we can do regration testing

Application programming interface

select name from emp union As select name from emp1;

Sends one or more keystrokes to the active window (as if 
typed on the keyboard).

syntax:object.SendKeys(string)

HI,

  this is simple. we can write DP by using Object
Identification dialog box and Object Spy.

in the Object Identification dialog box we can know which
properties we have to write while DP...and in Object SPY we
can know run time values of these properties.

 For Browser and page  we can give wither Name property or
title property.
 for link HTML Tag and Name.
for webcombo box : class name, attachedtext

   like this we can write. please check in Object
Identification dialog box.

After testing, we collect metrics of no of bugs found, 
open, closed which decides we can close the testing or not. 
Sometimes it depends on the time also. Generally very less 
time is given to the testing team which is though not a 
proper process, due to which there time is very less and 
hence have to stop testing. 
Tracebility Matrix is a work product which helps in tracing 
if all the requirements are developed and tested or not. 
Whether all the bugs found are closed for that test case or 
not. 
Test must submit the test cases, test report, bug report, 
test results to his/her manager

by data validation and data integrity.data validation means 
whether a new value inserted into a table correctly 
inserted or not
data integrity means the impact of the new value on the 
existing value

 hi this is satya ,any doubts contact:9912418320

We have to insert new values in the front end.After that we 
have to open the database and check whether the values are 
inserted correctly.

According to me they are no types in test strategy.....
The test strategy is a company level document which does 
not change from project to project but according to project 
only small modifications will be made...

Just do any operations like insert,delete or modify in
application and see manually that the operation has effected
in database or not(for database Testing u will have DB user
id and password, and u should give the data source name)


If there is any wrong pls let me know

Simply u can Add,Delete and Modify records with the help of 
application  and then use diff.SQL queries to fetch data 
from database then u come to no What type of changes were 
happen in database.

Quality Assurance means Prevent Defects,So

Life Cycle of QA is Reviews-unit tsting-
integration testing.

QA life cycle doesn't necessarly be the same with all the 
organizations .. Depending upon the risk associated with 
the application and the flow that the company is working 
upon , the testing life cycle may change .. A typical QA 
life cycle consists of the following components .. 

Verification (includes reviews of the designs and specs 
etc) - Unit Testing at the very begining stage of the bug 
fix - Integration testing (may be before or after 
functionality testing) - System testing - Acceptance 
Testing - Production 

Again the above flow need not be the same with all 
organizations

-Gathering Requirements
-Preparation of design doc and system specification doc
-Coding or developing the internal structure of application
-Unit testing by developers
-Quality assurance testing
Minimum acceptance tetsing, Functional, module or component,
-Integration, System and User acceptability(alpha & Beta 
testing)
-Deployment and maintainence

This is in general,it might change from org to org. Some 
these steps might be skipped based on the complexity of the 
project and the extent of risk involed and quality reuired.

Whoever opens the defect for the bug (tester) will assign 
the priority depending on how it affects the project.

Project Leader / Project Manager

once defect was detected by the tester ,first he report 
that Bug to testlead with a status NEW ,test lead will 
revise that bug whether it is genuine bug or not .if it is 
genuine then he assign priority and report that bug to the 
developer with ASSIGN status

 hi this is satya ,any doubts contact:9912418320

once defect was detected by the tester ,first he report 
that bug to testlead with a status"new" and first 
tester/testlead give the sevirity to the bug after sending 
the bug to developers status which is "assign"they will 
give the priority to the bug.