Actions can be reusable or non reusable but functions are
always reusable..

Actions are like every event (like press button, mouse 
click )

 Functions are Functionality of an Application like
    Insert scenario, Update Scenario, Delete Scenario
    like that...

VB script is used by QTP

Generally Test cases are prepared by FRS and SRS documents
Testers will follow usecases and scenario's and flow charts 
to prepare 
testcases
boundary value analysis 
Eqivalence class partitioning
Error guesssing
cause and Effect graphing

hi


 Test cases are Designed Using Test Scenario's
 Test Scenario's are prepared using Business Logic of
 Use cases


 sun_ramprasad@yahoo.com

depend on the organizations ,but my company follows this
type of formate  : given below

serial no:
testcase no:
test case id:
discription:
exepect result:
actual result:
pass/fail:

maxim companys follows this types of format only

pls tell iam correct not

Hi

   RTM has Business Logic 
   Where we can prepare Test Scenario's
   RTM could also be used to Map the Requirement 
   to Test Cases.





   sun_ramprasad@yahoo.com

Tracebility Matrix is a proof of document, which says that 
all the specifications are tested according to the 
requirements and the application is bug free.

Traceability Matrix is a one type of checking process which
gives the details about requiremts that are not covered in
the test document. It is a conformation process to check
test case document cover all the requirements exactly or not.

Traceability Matrix contains a tabular format that have the
reference numbers of all the documents that is used to
prepare the Test case Document

This may like following format

UCD-Ref-No    Functional_Point_Doc-Ref-No
Master_Test_case_Doc_Ref-No    Test-Case-No

Hi


   Because Fixed Build could show error while Doing 
   Regression Test.






  sun_ramprasad@yahoo.com

Fix for that bug has arraised a bug for the other test data.

Hi


   
   Database connectivity
   Domain Constraints
   key constraints
   Using(JOINS)





sun_ramprasad2yahoo.com

As a test engineer, to software developer we are submitting 
test report.

to test lead

Test Report is a detailed analysis or summery of what we 
have done in our testing.You can use it for history purpose.

On a high Level (Template):

1. Introduction : { what for this report ...}
2. Test Environment : { Tested Environment..platforms you 
tested etc.}
3. Testing Overview and Build Summary : {Type of testing 
and complete details about your each builds}
For ex :
Build No.
When you recieved from dev.
What is the duration :
Testing type:
No. of fixes:
Verifications:
Closed:
Opened:
Reopened:
FAD:
ER and IR:

4. Test Coverage : {Accross each build}
5.Test Effort : { Man-hrs is preferable}
6.Test Results : 
7.Defects : { Summarize all the defects}
8.Release Criteria.

Through Traceability Matrix

We can check it out by traceability Matrix- 

Traceability Matrix is nothing but No of test cases executed
to that of the requirements.


Shravan Kumar Akula

CTT me - Coolshravan4u@yahoo.co.in, If u have any queries.

Good Question.

Ofcourse through Tracebility Matrix.
In detail..
If you are writing 500 testcases for 10 inputs then all the 
test cases can not be direct cases; means, dependent test 
cases should be there(test case depends on another 
testcase).

So if a test case is failing then obviously the dependent 
test cases will also fail. But usually we use to say that 
the dependent cases are blocked(instead of fail) because of 
the failed test case.

Take an edit box in the screen.
The requirement could be:
User is allowed to enter the values in the username and it 
should accept 10 chars only.
Now, consider the following test cases for this requirement.

1. User able to enter data in username field.
2. Check for max. length of username field.

Assume the first case fails.i.e, the edit field doesn't 
allow the user to enter the values;what happens to the 
second case ? The tester cannot execute the second case as 
he cannot enter the data into edit field.In this scenario 
the second case is said to be blocked by case 1 and both 
belong to the same requirement.

Usually in the tracebility matrix, we use to map the test 
cases developed for the particular requirement.Say, if you 
are developing 10 cases for a requirement and 1 case is 
failing and remaining 9 cases are passed, then the 
tracebility matrix does not say the requirement is passed.
Only if all the 10 cases of the requirement are passed then 
only the tracebility matrix shows the requirement is Passed.

we will report same bug number for both testcases.and 
status of the bug remains active.

i will give the same defect ID for both test cases and i 
will put the status as NEW.

If i report same bug two times i'll change the bug 
status.But i'll not change the test case number.

If a Bug is existed in Present build( Normal test case) and 
Regression status.... Then it can be treated as Duplicate/ 
Production defect with same Defect No. I feel

Hi

  Peer Test is a review process
  In a Testing Team 
   Tester A will Review Tester B Document &
   Tester B will Review Tester A Document.

   

sun_ramprasad@yahoo.com

Reviewing the docs(Peer testing) or code by your peer(peer 
code review).

Hi

  You have to Prepare Business Flow for all the
  Three passwords with combination of Username

sun_ramprasad@yahoo.com

Hi..
Can you please explain in brief

PLEASE EXPLAIN INDETAIL

please explain in brief

Out line:
1. Data Validity.
2. Navigation.
3. Functionality.

hi ppp,
            can u please explain clearly

Hi

   formal review

  sun_ramprasad@yahoo.com

Hi

    review without preparations
   everyday morning module lead speak with us for 5 to
   10 minutes is walkthrough

   sun_ramprasad@yahoo.com

Hi some body has written wrong walkthroughs are informal 
reviews. In walkthroughs everybody will partcipate 
testers,developers and technical writers.walkthrough will 
conduct when ever necessary.

Hi

    1. Methodologies are EP & BVA
    2. inputs are based on scenario's(use case)








  sun_ramprasad@yahoo.com

Hi

  Bug differed is
  bug with least significant 
  customer or clinet point of view not important



 sun_ramprasad@yahoo.com

When a tester finds a bug,the bug is reported to 
developer,the status of the bug is " open".
Developer agrees to fix that bug in next version of the 
product and marks the status of bug as "deferred".

when a bug is found and when a developer cant fix the bug 
in this release and the developer changes the state of the 
bug to differ that it wil get fixed in the next release

In some cases a particular bug stands no importamce & is 
needed to be/can be avoided, that time it is marked 
with 'deferred' status.