Utr PD33843

Change History
Author & Created Reviewed By &

Doc Version Change Description
Date Review Date
Lakshmi Ramesh Shkanda Vikash
1 08/04/2020 PD33843 10/04/2020
Approved By &
Approved Date
Satish Kumar R
10/04/2020
Unit testing Guidelines
To ensure maximum coverage of test cases in unit testing, the following steps can be followed.
1. Progressive Elaboration
2. Unit testing scenario identification
3. Valid, Border and Invalid inputs
4. Cross Function Testing
1. Progressive Elaboration
Each feature (L0) should be broken down into smaller sub-features/levels(L0 to Ln), and then into functions. Then ensure that
Consider a feature F1. This feature can be subdivided into sub-features SF1, SF2 and SF3. Sub-feature SF1 may contain functio
2. Unit testing scenario Identification
While creating test cases for a single function, ensure that all modes of input actions are covered, expected and actual results
3. Valid, Border and Invalid Inputs
When values are to entered in a field, test cases must be created entering 6 different kinds of inputs such as valid input, upper
For, example if a field is to be filled with a number between 6 and 10, test cases needs to be created with input as 8,10,6,11,5,
4. Feature interaction
Feature interaction is used to identify interaction between features.If a new feature is interacting with existing feature 1 and e
Unit testing Guidelines
ctions. Then ensure that test cases are created for all functions in a feature. This will ensure complete coverage of the feature.
SF1 may contain functions Fn1 and Fn2. Sub-feature SF2 may contain functions Fn3 and Fn4. Sub-feature SF3 may contain functions Fn5 a
ected and actual results are entered. This will ensure that all components of the code is operational and ensures complete test coverage.
uch as valid input, upper border input, lower border input, above upper border input, below lower border input and invalid input. This tes
with input as 8,10,6,11,5, and @. This will ensure that all possible test cases have been created.
h existing feature 1 and existing feature 2 then test scenarios must be identified to ensure interactions between them are error free.
the feature.
contain functions Fn5 and Fn6. Now, instead of creating test cases for feature F1, creating test cases for functions Fn1 to Fn6 will mean th
omplete test coverage.
nd invalid input. This tests the code at general, extreme and invalid input conditions.
em are error free.

s Fn1 to Fn6 will mean that the feature F1 has been completely tested .
Feature/Level 0 Level 1 Function
Create Service
Service Update service
Query Service
Create Product
Provision to
capture different
language
descriptions For Update product
Product,Service, Product
Service Hierachy
and Offer UI. Query Product
Create Offer
Offer Update offer
Query Offer
Create Service
Update service
Query Service
Web service/File Upload
Create Product
Update product
Query Product
Create Offer
Update offer
Query Offer
Input Parameter
Service Name
Service Description
Service Charge Description
Service Name
Service Description
Service Name
Service Description
Product Name
Product Description
Product Charge Description
Product Name
Product Description
Product Name
Product Description
Offer Name
Offer Description
Offer Name
Offer Description
Offer Name
Offer Description
Service Name
Service Description
Service Name
Service Description
Service Name
Service Description
Product Name
Product Description
Product Name
Product Description
Product Name
Product Description
Offer Name
Offer Description
Offer Name
Offer Description
Offer Name
Offer Description
Sl No: Test Scenario
C
1 Click create service screen icon
2 All the valid fields are displayed in the 1st crumb

After entering all the mandatory fields in 1st crumb such as Service Type,Service Code,Service Name,
2 And Standalone service as yes and leaf node as yes and click next
3 In the Second crumb Service Charges Block select usage charge
4 In the Second crumb Service Charges Block select one time charge
5 In the Second crumb Service Charges Block select recurring time charge
6 All the fields inside charge applicability pop up Link
7 After Entering all the value in charge applicability field click apply
8 In the Third crumb click save button
9 Again click create service screen icon
10 And Standalone service as no and leaf node as yes and click next
11 Click next in the second crumb
12 In third crumb Library charge block for Charge applicability Link

13 All the fields inside charge applicability pop up Link
Add two charge type such as charge code and rate enter value for Charge applicability link and click apply
14 In third crumb Library charge block enter value for charge applicability link and click save
15 Again click create service screen icon
16 Negotiable,Leaf Node,Purpose and click Next
17 Give value for service cost,competitor fee,service charge and free limit and click next
18 In third crumb enter value for library charge and click save
19 Take a service in edit mode
20 Moved to the second crumb by click next
21 In second crumb Service charge block click charge applicability link
22 Click next button in second crumb
23 In third crumb Library charge block for Charge applicability Link
24 Adding library charge by click add button

25 At-last click save button
D
26 Take a service in Detail mode
28 Moved to third crumb I.e last crumb
Cr
29 Click create Product screen icon
30 After entering all the mandatory field in 1st crumb and click Next
31 In second crumb Service charge block click add standalone service
32 For standalone service charge applicability link and their fields
33 In second crumb Service charge block click add Non standalone service
34 For non standalone service charge applicability link and their fields
35 Click add variation button in service charge block
36 click add charge button by tick service
37 After entering all the required fields click save button
38 For Competitor charge and product charge block
39 Again Click create Product screen icon

40 Enter required value in 2nd crumb such as product cost ,service charge and free limit and click Next
41 Entering required value in 3rd crumb and click save
42 Take a product in edit mode

44 In second crumb service charge block for charge applicability link
45 Click save button
46 Again Take a product in edit mode
If changing any of the fields in any of the blocks such as product cost,Service charge,
47 Competitor Charge and moved to next crumb
48 After entering all the mandatory fields move to the last crumb and select save
D
49 Take a product in Detail mode
50 Moved to the second crumb
51 Moved to last crumb
C
52 Click create Offer screen icon
53 Select offer type as benefit and enter all the required field in 1 st crumb and click next
54 In 2nd crumb enter benefit charge required values and click next
55 In 3rd crumb enter the schema details and click save

56 Select offer type as bundle and enter all the required field in 1 st crumb and click next
57 In 2nd crumb select two or more product and one or more standalone service and click next
58 For standalone service, charge applicability link and their fields

60 Select offer type as Product and enter all the required field in 1 st crumb and click next
61 In 2nd crumb select one product and one or more standalone service and click next
63 For non standalone service charge applicability link and their fields
65 Select offer type as Service and enter all the required field in 1 st crumb and click next
66 In 2nd crumb select one or more services and click next

69 Take a Offer in edit mode
70 For offer type as Service
71 Click next in first crumb
72 In third crumb For standalone service, charge applicability link and their fields
73 Moved to the last crumb and select save
74 For offer type as product
78 For offer type as bundle
82 Take a offer in Detail mode
83 Moved to the 2nd crumb

84 Moved to last crumb
Web Se
C
85 If all the mandatory value is given for Service Screen
86 If missing some mandatory value for service screen
87 Give the charge value for service
88 Give the value for charge applicability link block more than one list
89 Give charge model other than usage charge and give value for charge applicability link .
90 Give the value for charge applicability link block
U
91 For Service Screen
92 If update the existing field values
93 if no value is given for Service Screen
Q
94 For Service Screen
95 For charge applicability block and their field values
Cr
96 If all the mandatory value was given for product screen
97 If missing some mandatory value for product screen
98 Entered the charge values for product charges
99 Give the value for charge applicability link block more than one list in create mode
100 Give charge model other than usage charge and give value for charge applicability link .
101 Entered the multiple charge values in product charge block
102 Entered the Service charges in product charge as product service linkage.
Up
103 For Product Screen
105 Give the value for charge applicability link block more than one list in update mode
106 Give charge model other than usage charge and give value for charge applicability link in update mode
107 if no value is given for product screen fields
Q
108 For Product Screen
C
109 If all the mandatory value is given for Offer Screen
110 If missing some mandatory value for offer screen
111 Entered the charge values for offer service charges
112 Give the value for charge applicability link block more than one list in create mode
114 if no value given for service offer screen charge applicability link for new charge
U
115 For Offer Screen
117 Give the value for charge applicability link block more than one list in update mode
119 if no value given for service offer screen charge applicability link for new charge
120 For Offer Screen

Expected Output
Create Service
Screen will be displayed with all the default values
2 Links are displayed next to Service Name and Description
respectively.
The value in the Field is Validated and moved to next crumb
successfully
Charge applicability Link will be shown successfully
Charge applicability Link will be hidden successfully
Charge applicability Link will be hidden successfully
All the fields are optional
The given value was applied successfully
The given value was stored to db successfully
The value in the Field is Validated and moved to next
Crumb successfully
screen will be moved to next crumb successfully
Link will be visible for charge code and rate charge type
Successfully.
All the fields are optional
The given value was applied successfully
The given value was saved to db successfully
The value in the Field is Validated and moved to next

Crumb Successfully.
The value in the field is validated successfully and moved to

Second crumb
The given value was stored to db successfully
Edit Service
The edit screen will be displayed with the given values
If value is given in the blocks the values
Will be displayed in the block
All the fields inside the link are editable
The value was validated and moved to last crumb successfully
All the fields inside the links are editable
New library charge was added Successfully

The given values was validated and stored to the DB successfully
Detail Service
The detail screen will be displayed with the given values
Entered Value in the block is shown correctly and as non editable
The given values are displayed correctly and as non editable
Create Product
The value in the field is validated correctly and
Moved to next crumb
New Standalone service was added successfully

Charge applicability link will be visible and inside fields are
Non editable
New non Standalone service was added successfully

Charge applicability link will be invisible and inside fields are
Non editable
Charge applicability link and their old value will be auto
populated for variation and as non editable
New charge was added and charge app link was editable.
The given value was saved to db successfully

Charge applicability Link is not applicable and it is not shown
Successfully

The value in the Field is Validated and moved to next crumb
The given values will be stored in the DB
Edit Product
The edit screen will be displayed with all the given values
First crumb value will be validated moved to second crumb
The field value inside the link will be shown and as non editable
The changed value will be updated to db successfully
The edit screen will be displayed with all the given values
The value in the Field is Validated and moved to
Next crumb successfully.
The values will be updated successfully in the db
Detail Product
Given values in the fields was shown correctly and as non editable
The value will be displayed as a non editable field
Create Offer
Screen will be displayed with all the default values Successfully
The given values was validated and moved to next crumb
The given values are validated and moved to next crumb
The given values in all the block was validated correctly
And stored to db successfully.
Charge applicability Link will be enable and fields are non
Editable
Editable
Editable
Editable
The given values will be stored in the DB
Edit offer
The edit screen will be displayed with the given values
All default value will be shown in first crumb
The value is validated and moved to next crumb
Editable
The values will be updated successfully
Editable
Editable
Detail Offer

Given and updated values are displayed successfully
And as non editable
The value will be displayed as a non editable field
Web Service /File Upload
Create Service
The given value was stored in the DB while saving
Mandatory exception will be thrown
The given value was stored in DB while saving
Validation was thrown successfully
Update Service
The given values was displayed correctly in ui
The Updated value will be stored in the DB while saving
Query Service
The values will be displayed successfully
The field values will be shown
Create Product
The given value was stored in DB while saving successfully
Update Product
The given values was displayed correctly in user interface
Query Product
The given values will be displayed successfully
Create Offer

Update Offer
The given values was displayed correctly in user interface


Query Offer
The given values will be displayed successfully

Actual Output Remarks
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
As Expected Passed
Input Possible Values Invalid Lower Valid Inputs Invalid Upper
…. -2 -1 0 1
2 …… 500 501 …. 998 999 1000 1001 1002 ….
New feature 1 New feature 2 New feature 3 Existing feature 1
New feature 1 ✖ O ✖ O
New feature 2 O ✖ O O
New feature 3 ✖ O ✖ O
Existing feature 1 O O O ✖
Existing feature 2 ✖ O ✖ O
Existing feature 3 O O O O
✖ - Features having no interaction

O - Features having interaction `
Existing feature 2 Existing feature 3
✖ O
O O
✖ O
O O
✖ O
O ✖
Review Comments
Sl. No. Version No. Iteration Number Section No:
1 1 1 1
Review Comments
Actions
Review finding Actionee
Agreed
Need to add the test case for service offer upload scenario
Completion
Priority
date
High

Utr PD33843

Uploaded by

Copyright:

Available Formats

You might also like

Utr PD33843

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Utr PD33843

Uploaded by

Copyright:

Available Formats

Change History

Author & Created Reviewed By &

omplete test coverage.

em are error free.

Service Update service

Offer Update offer

Web service/File Upload

2 All the valid fields are displayed in the 1st crumb

12 In third crumb Library charge block for Charge applicability Link

19 Take a service in edit mode

20 Moved to the second crumb by click next

21 In second crumb Service charge block click charge applicability link

22 Click next button in second crumb

23 In third crumb Library charge block for Charge applicability Link

24 Adding library charge by click add button

31 In second crumb Service charge block click add standalone service

32 For standalone service charge applicability link and their fields

35 Click add variation button in service charge block

36 click add charge button by tick service

37 After entering all the required fields click save button

38 For Competitor charge and product charge block

39 Again Click create Product screen icon

42 Take a product in edit mode

55 In 3rd crumb enter the schema details and click save

58 For standalone service, charge applicability link and their fields

59 In 3rd crumb enter the schema details and click save

62 For standalone service, charge applicability link and their fields

67 For standalone service, charge applicability link and their fields

82 Take a offer in Detail mode

83 Moved to the 2nd crumb

109 If all the mandatory value is given for Offer Screen

110 If missing some mandatory value for offer screen

111 Entered the charge values for offer service charges

116 If update the existing field values

120 For Offer Screen

The value in the Field is Validated and moved to next

The value in the field is validated successfully and moved to

All the fields inside the link are editable

The value was validated and moved to last crumb successfully

All the fields inside the links are editable

New library charge was added Successfully

New Standalone service was added successfully

New non Standalone service was added successfully

The given value was saved to db successfully

Screen will be displayed with all the default values

The detail screen will be displayed with the given values

The given value was stored in the DB while saving

Mandatory exception will be thrown

The given value was stored in DB while saving

Validation was thrown successfully

Validation was thrown successfully

The given value was stored in the DB while saving

The Updated value will be stored in the DB while saving

Validation was thrown successfully

The given value was stored in the DB while saving

The given values will be displayed successfully

✖ - Features having no interaction