Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

TCER Document

No description
by

karishma Tiwari

on 3 July 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of TCER Document

Sample
TCER
Introduction
TCER

Properties
TCER
Who uses
TCER?
Test Conditions and Expected Results
Example
TCER
TCER
Test Condition2:
Customer can enter a valid username.

Expected Results:
The system accepts the data without error.




Test Conditions and Expected Results
TCER
Test Condition 3:
Customer inputs a password into the password field

Expected Results:
The system masks the content of the password field as the user enters it.



Test Conditions and Expected Results
TCER
Test Condition 1:
The Create Account screen provides the facility to enter username, password, confirmation password, title, first name, last name, email address, telephone number and postcode.

Expected Results:
The Create Account screen has the following fields to allow the customer to enter the required information for their account:
username, password, confirmation password, title, first name, last name, email address, telephone number and postcode.




TCER Document
-Test Conditions and Expected Results (TCER)
Defines what should occur when a requirement is tested
-Specifies:
Positive values – what should occur
Negative values – what should not occur
Limit values – what is not within the normal range but are acceptable
Exception values – values that are not normal but can occur,
and if they need special processing

Name and description of the test condition.
Begin these with an action verb: create, print, etc.
Expected result.
For each test condition, define a corresponding expected result. The expected results created during test planning can be relatively high level. For example, an expected result for the test condition, create invoice, can simply be, an invoice is created.
Requirement or design source.
Each test condition is derived from one requirement or design item. This makes it easier to verify if all requirements and design elements are covered and to track the defects that are detected during test execution
Testers
use this deliverable to allocate appropriate test conditions into the Test Scenarios template in readiness for test scripting or if starting with Test Scenarios to drill down the specific test conditions and expected results applicable to each test scenario
Modified By:

Application Designer
Developer
Technical Designer
Tester
Test Lead
Description:
Create Customer Account
T
est Condition Id:
1
Requirement:
Create Customer Account-Mainflow-
Step 1
Presented By:
Karishma Tiwari
Shejal Rawat
Deepti Agre
Pooja Torniya
Full transcript