Digital Key Solution Friend

Qualification
l Key Solution Friend Key Termination (Web) SW
Qualification Test Report

Document Ver : 1.0

Date: 18-Aug-23
Prepared by Namadeva
Approved by MA
 Revision History
Reviewed/
Rev.No Date Author
Approved by
0.1 24-Aug-23 Namadeva Manjunath

0.2 24-Aug-23 Namadeva Manjunath

1 25-Aug-23 Namadeva SQA Team

 Description
Initial draft
Peer review and incorporated
comments
SQA review comments
fixed_verified
 Traceability Reference
Test Case ID Feature Name Variant
Id

Friend Key
TC_FKTW_01 NA NA
termination(web)

Friend Key
TC_FKTW_02 NA NA
termination(web)

Friend Key
TC_FKTW_03 NA NA
termination(web)

Friend Key
TC_FKTW_04 NA NA
termination(web)

Friend Key
TC_FKTW_05 NA NA
termination(web)

Friend Key
TC_FKTW_06 NA NA
termination(web)
 Friend Key
TC_FKTW_07 NA NA
termination(web)

Friend Key
TC_FKTW_08 NA NA
termination(web)

Friend Key
TC_FKTW_09 NA NA
termination(web)

Friend Key
TC_FKTW_10 NA NA
termination(web)

Friend Key
TC_FKTW_11 NA NA
termination(web)

Friend Key
TC_FKTW_12 NA NA
termination(web)

Friend Key
TC_FKTW_13 NA NA
termination(web)
 Friend Key
TC_FKTW_14 NA NA
termination(web)

Friend Key
TC_FKTW_15 NA NA
termination(web)

Friend Key
TC_FKTW_16 NA NA
termination(web)

Friend Key
TC_FKTW_17 NA NA
termination(web)

Friend Key
TC_FKTW_18 NA NA
termination(web)

Friend Key
TC_FKTW_19 NA NA
termination(web)

Friend Key
TC_FKTW_20 NA NA
termination(web)
 Friend Key
TC_FKTW_21 NA NA
termination(web)

Friend Key
TC_FKTW_22 NA NA
termination(web)

Friend Key
TC_FKTW_23 NA NA
termination(web)

Friend Key
TC_FKTW_24 NA NA
termination(web)

Friend Key
TC_FKTW_25 NA NA
termination(web)

Friend Key
TC_FKTW_26 NA NA
termination(web)

Friend Key
TC_FKTW_27 NA NA
termination(web)
 Friend Key
TC_FKTW_28 NA NA
termination(web)

Friend Key
TC_FKTW_29 NA NA
termination(web)

Friend Key
TC_FKTW_30 NA NA
termination(web)

Friend Key
TC_FKTW_31 NA NA
termination(web)

Friend Key
TC_FKTW_32 NA NA
termination(web)

Friend Key
TC_FKTW_33 NA NA
termination(web)

Friend Key
TC_FKTW_34 NA NA
termination(web)
 Friend Key
TC_FKTW_35 NA NA
termination(web)

Friend Key
TC_FKTW_36 NA NA
termination(web)

Friend Key
TC_FKTW_37 NA NA
termination(web)

Friend Key
TC_FKTW_38 NA NA
termination(web)

Friend Key
TC_FKTW_39 NA NA
termination(web)

Friend Key
TC_FKTW_40 NA NA
termination(web)

Friend Key
TC_FKTW_41 NA NA
termination(web)
 Digital Key Solution Software
Test Case Objective Test Case Description Test Precondition Test input data/ file

To verify that sending

Vehicle OEM server make Request
request to notify
a request to notify termination_notification of {URL}/digitalKey/
termination of digital key
termination of an specific a Digital Key API should terminate-notification
has endpoint as per
digital key be ready
document

{
when sending notify "vehicleIdentifier":
To verify that valid
termination request url "2222000000000622",
response message shows Request
with valid input data ,it "slotIdentifier":
& key status also change, termination_notification of
should show valid response "AAAAAAAAAAAAAA
when sending notify a Digital Key API should
massage.And also key AA",
termination request url be ready
status will change to "origin":
with valid input data
15(Intermination) "VEHICLE_OEM"
{
To verify that only 4 type Only 4 type of origin is "vehicleIdentifier":
of origin is vaild in post used in request body Request "2222000000000622",
request for notify VEHICLE,VEHICLE_OE termination_notification of "slotIdentifier":
termination of digital key, M,FRIEND_DEVICE,OW a Digital Key API should "AAAAAAAAAAAAAA
except these it will NER_DEVICE; else it will be ready AA",
show/throw show/throw error "origin":
"VEHICLE_OEM"
{
To verify the response "vehicleIdentifier":
should show error while Should not be Terminate a Request "2222000000000622",
entering a unknown digital key with unknown termination_notification of "slotIdentifier":
parameter for the paramter which is not in a Digital Key API should "AAAAAAAAAAAAAA
terminate_notification the requirement schema be ready AA",
request "origin":
"FRIEND_DEVICE",

To verify that endpoint for Vehicle OEM server make

Request terminate of a
notify that digital key is a request to notify that an {URL}/digitalKey/
Digital Key API should be
already terminated is as per specific digital key is terminate
ready
document already terminated

To verify that only valid {

Valid vehicle identifier &
json body in the request is "vehicleIdentifier":
slotIdentifier is used in the
able to notify that digital Request terminate of a "2222000000000622",
request body for notify
key is already terminated Digital Key API should be "slotIdentifier":
termination of digital key
and key status will also ready "AAAAAAAAAAAAAA
and key status will change
change, else it will show AA"
to 10 (termination)
error }
 {
"vehicleIdentifier":
To verify the response 2222000000000622,
Should not be Terminate a
should show error while Request terminate of a "slotIdentifier":
digital key with unknown
entering a unknown Digital Key API should be "AAAAAAAAAAAAAA
paramter which is not in
parameter for the terminate ready AA",
the requirement schema
request "color":"blue"
}

Response will shows http

To verify that response Request
status of 404 when digital
shows http status of 404 terminate_notification and {URL}/-notification &
key is misssing within
when digital key is terminate of a Digital Key {URL}/terminate
request url for the
misssing within request url API should be ready
termination of digital key

The response should throw

To verify the response for Request
an error if user misses any
the Invalid API end point terminate_notification of a
paramater in the end point {URL}/-notification
for terminate-notification Digital Key API should be
url for terminate-
request ready
notification request

{
"vehicleIdentifier":
The user can make an "2222000000000622",
To verify the user is able to Request
FriendKey with keystatus "slotIdentifier":
make an FriendKey to terminate_notification of a
of InTermination which is
InTermination for Digital Key API should be "AAAAAAAAAAAAAA
going to be terminated on AA",
termination purpose ready
later stage "origin":
"VEHICLE_OEM"

The keyID of the previous

To verify the database is
testcase (TC_FKTW_10) Request
showing keyID as
will have a keyStatus of 15 terminate_notification of a
InTermination, for the NA
in the database (15 is the Digital Key API should be
keyID which is mentioned
keyStatus for ready
in TC_FKTW_10
"InTermination")

The response should throw

To verify the response for
an error if user misses or Request terminate API
the Invalid API end point {URL}/terminate
eneters invalid end point should be ready
for terminate request
url for terminate request

{
API shall perform the "vehicleIdentifier":
Validate the vehicle "222200000000061A",
validation for 'vehicle Request
identifier parameter "slotIdentifier":
identifier' parameters terminate_notification of a
contains the value with the
contains the value with the Digital Key API should be "AAAAAAAAAAAAAA
vehicle identifier stored in AA",
vehicle identifiers stored in ready
database "origin":
database
"VEHICLE_OEM"
 API shall perform the {
Validate the vehicle "vehicleIdentifier":
validation for 'vehicle
identifier parameter Request terminate of a "222200000000061A",
identifier' parameters
contains the value with the Digital Key API should be "slotIdentifier":
contains the value with the
vehicle identifier stored in ready "AAAAAAAAAAAAAA
vehicle identifiers stored in
database AA"
database
}
{
Validate the Terminate- "vehicleIdentifier": "",
Validate the vehicle notification request API Request "slotIdentifier":
identifier parameter does shall perform the validation terminate_notification of a "AAAAAAAAAAAAAA
not contains any value or for ''vehicle identifier' Digital Key API should be AA",
null parameter contains the ready "origin":
value null or blank "VEHICLE_OEM"
}

Validate the Terminate- {

Validate the vehicle notification request API "vehicleIdentifier": "",
Request terminate of a
identifier parameter does shall perform the validation "slotIdentifier":
Digital Key API should be
not contains any value or for ''vehicle identifier' "AAAAAAAAAAAAAA
ready
null parameter contains the AA"
value null or blank }

{
Verify that "vehicleIdentifier":
vehicleIdentifier parameter "2222000000000622",
Verify the correctness and Request
should accepts only the "slotIdentifier":
handling of the terminate_notification of a
hexadecimal value which
hexadecimal value for Digital Key API should be "AAAAAAAAAAAAAA
exists in the database for AA",
parameter vehicleIdentifier ready
terminate_notification "origin":
request "VEHICLE_OEM"

Verify that {
Verify the correctness and vehicleIdentifier parameter "vehicleIdentifier":
Request terminate of a "2222000000000622",
handling of the should accepts only the
Digital Key API should be "slotIdentifier":
hexadecimal value for hexadecimal value which
ready "AAAAAAAAAAAAAA
parameter vehicleIdentifier exists in the database for
terminate request AA"
}
{
Verify that a non-empty "vehicleIdentifier":
Verify the correctness and string with whitespace Request "22220000 00000622",
handling of the characters is not terminate_notification of a "slotIdentifier":
hexadecimal value for accepted for Digital Key API should be "AAAAAAAAAAAAAA
parameter vehicleIdentifier terminate_notification ready AA",
request "origin":
"VEHICLE_OEM"

{
Verify that a non-empty "vehicleIdentifier":
Verify the correctness and
string with whitespace Request terminate of a "22220000 00000622",
handling of the
characters is not Digital Key API should be "slotIdentifier":
hexadecimal value for
accepted for terminate ready "AAAAAAAAAAAAAA
parameter vehicleIdentifier
request AA"
}
 {
Verify that "vehicleIdentifier":
vehicleIdentifier parameter "2222000000000622",
Verify the correctness and Request
should accepts only the "slotIdentifier":
handling of the unique terminate_notification of a
unique value in the
value for parameter Digital Key API should be "AAAAAAAAAAAAAA
database for AA",
vehicleIdentifier ready
terminate_notification "origin":
request "VEHICLE_OEM"
{
"vehicleIdentifier":
Verify the correctness and 2222000000000622,
Verify that a non-string Request
handling of the string data "slotIdentifier":
value (e.g., integer or terminate_notification of a
type for parameter
boolean) is not accepted for Digital Key API should be "AAAAAAAAAAAAAA
vehicleIdentifier for AA",
terminate_notification ready
terminate_notification "origin":
"VEHICLE_OEM"

{
Verify the correctness and "vehicleIdentifier":
Verify that a non-string
handling of the string data Request terminate of a 2222000000000622,
value (e.g., integer or
type for parameter Digital Key API should be "slotIdentifier":
boolean) is not accepted for
vehicleIdentifier for ready "AAAAAAAAAAAAAA
terminate
terminate AA"
}

Verify that {
Verify the correctness and vehicleIdentifier parameter "vehicleIdentifier":
Request terminate of a "22220000 00000622",
handling of the unique should accepts only the
Digital Key API should be "slotIdentifier":
value for parameter unique value in the
ready "AAAAAAAAAAAAAA
vehicleIdentifier database for terminate
request AA"
}
{
"vehicleIdentifier":
Verify the correctness and "2222000000000622",
Verify that a non-string Request
handling of the string data "slotIdentifier":
value (e.g., integer or terminate_notification of a
type for parameter "123456789",
boolean) is not accepted for Digital Key API should be
slotIdentifier for "origin":
terminate_notification ready
terminate_notification "VEHICLE_OEM"
}
{
"vehicleIdentifier":
Verify the correctness and Verify that a non-empty "2222000 000000622",
Request
handling of the string data string with whitespace "slotIdentifier":
terminate_notification of a
type for parameter characters is not "AAAAAAA
Digital Key API should be
slotIdentifier for accepted.for the AAAAAAAAA",
ready
terminate_notification terminate_notification "origin":
"VEHICLE_OEM"

{
Verify the correctness and "vehicleIdentifier":
Request
handling of the string data Verify that an empty string
terminate_notification of a "2222000000000622",
type for parameter is not accepted for the "slotIdentifier": " ",
Digital Key API should be
slotIdentifier for terminate_notification "origin":
ready
terminate_notification "VEHICLE_OEM"
}
 Verify the parameter
slotIdentifier is
mandatory in request
body for
terminate_notification
Verify the correctness and
handling of the unique
value for parameter
slotIdentifier for
terminate_notification
Verify the correctness and
handling of the string data
type for parameter boolean) is not accepted for
slotIdentifier for terminate
Verify the correctness and
handling of the string data
type for parameter
slotIdentifier for terminate
Verify the correctness and
Verify that an empty string Request terminate of a {
handling of the string data
type for parameter
slotIdentifier for terminate
Verify the correctness and
handling of the unique
value for parameter
slotIdentifier
Verify the correctness and
handling of the string data
type for parameter origin
for terminate_notification
If user misses or {
Request
intentionally removed "vehicleIdentifier":
terminate_notification of a
the parameter
Digital Key API should be "2222000000000622",
slotIdentifier then it "origin":
ready
should throw an error "VEHICLE_OEM"
}
{
Verify that slotIdentifier "vehicleIdentifier":
"2222000000000622",
parameter should accepts Request
"slotIdentifier":
only the unique value in terminate_notification of a
the database for Digital Key API should be "AAAAAAAAAAAAAA
AA",
terminate_notification ready
"origin":
request
"OWNER_DEVICE"
Verify that a non-string {
Request terminate of a "vehicleIdentifier":
value (e.g., integer or
Digital Key API should be "2222000000000622",
ready "slotIdentifier":
terminate
111111111111
}
Verify that a non-empty {
string with whitespace Request terminate of a "vehicleIdentifier":
characters is not Digital Key API should be "2222000000000622",
accepted.for the ready "slotIdentifier": "AAAA
terminate AAAA AAAAAAAA"
}
is not accepted for the Digital Key API should be "vehicleIdentifier":
terminate ready "2222000000000622",
"slotIdentifier": " "
}
{
Verify that slotIdentifier "vehicleIdentifier":
parameter should accepts Request terminate of a "2222000000000622",
only the unique value in Digital Key API should be "slotIdentifier":
the database for terminate ready "AAAAAAAAAAAAAA
request AA"
}
{
Verify that a non-string "vehicleIdentifier":
value (e.g., integer or Request "2222000000000622",
boolean) is not accepted for terminate_notification of a "slotIdentifier":
parameter origin of Digital Key API should be "AAAAAAAAAAAAAA
terminate_notification ready AA",
request "origin": 1234567
}
 {
"vehicleIdentifier":
Verify the correctness and Verify that an empty string Request "2222000000000622",
handling of the string data is not accepted for the terminate_notification of a "slotIdentifier":
type for parameter origin terminate_notification of Digital Key API should be "AAAAAAAAAAAAAA
for terminate_notification origin parameter ready AA",
"origin": ""
}
{
"vehicleIdentifier":
Verify the correctness and Request "2222000000000622",
Verify that the parameter "slotIdentifier":
handling of the string data terminate_notification of a
origin should accepts
type for parameter origin Digital Key API should be "AAAAAAAAAAAAAA
the VEHICLE_OEM AA",
for terminate_notification ready
"origin":
"VEHICLE_OEM"
{
"vehicleIdentifier":
Verify the correctness and Request "2222000000000622",
Verify that the parameter "slotIdentifier":
handling of the string data terminate_notification of a
origin should accepts
type for parameter origin Digital Key API should be "AAAAAAAAAAAAAA
the VEHICLE AA",
for terminate_notification ready
"origin": "VEHICLE"
}
{
"vehicleIdentifier":
Verify the correctness and Request "2222000000000622",
Verify that the parameter "slotIdentifier":
handling of the string data terminate_notification of a
origin should accepts the
type for parameter origin Digital Key API should be "AAAAAAAAAAAAAA
OWNER_DEVICE AA",
for terminate_notification ready
"origin":
"OWNER_DEVICE"
{
"vehicleIdentifier":
Verify the correctness and Request "2222000000000622",
Verify that the parameter "slotIdentifier":
handling of the string data terminate_notification of a
origin should accepts the
type for parameter origin Digital Key API should be "AAAAAAAAAAAAAA
FRIEND_DEVICE AA",
for terminate_notification ready
"origin":
"FRIEND_DEVICE"
{
Verify the didgital key "vehicleIdentifier":
Verify that the digital key "2222000000000622",
status should be active in Request
and status of the key "slotIdentifier":
the database, If the status is terminate_notification of a
present in the database to
InTermination or Digital Key API should be "AAAAAAAAAAAAAA
perform AA",
Terminated then it should ready
terminate_notification "origin":
throw an error
"FRIEND_DEVICE"
Verify that without sending
notification the key should {
not be terminate directly, Request "vehicleIdentifier":
Verify the order of
first the terminate_notification and "2222000000000622",
execution to Terminate a "slotIdentifier":
terminate_notification terminate of a Digital Key
digital key "AAAAAAAAAAAAAA
request needs to send and API should be ready
then the terminate request AA"
to the Vehicle OEM }
Key Solution Software Qualification - Test Report
Test Steps Expected result/behavior Mode of Execution Priority

The end point should be

1. Cross check actual end
according to requirement
point with document Manual P1
({URL}/digitalKey/termin
requirement
ate-notification)

1. Select Post and give the The status code should be

URI as mentioned. 200 and key Statuts should
2. Click on Body to change from active to Manual P1
provide data and click on InTermination for valid
send button. request

1. Select Post and give the

URI as mentioned. It should accept any one
2. Click on Body to origin which is mentioned Manual P1
provide data and click on in test description
send button.

1. Select Post and give the

It should throw an error
URI as mentioned.
instead of changing the
2. Click on Body to Manual P1
status from active to
provide data and click on
InTermination
send button.

1. Cross check actual end

The end point should be
point with document Manual P1
according to requirement
requirement

1. Select Post and give the

The status should change
URI as mentioned.
from InTermination to
2. Click on Body to Manual P1
Terminated and Status
provide data and click on
code is 200
send button.
1. Select Post and give the
URI as mentioned. The response should throw
2. Click on Body to error with an error message Manual P1
provide data and click on of Illegal parameter
send button.

1. Select Post and give the

URI as mentioned. The Http status will be
2. Click on Body to match with document Manual P1
provide data and click on requirement
send button.

1. Select Post and give the

In the input data the key
URI as mentioned.
"digital" is missing, so it
2. Click on Body to Manual P1
should throw an error with
provide data and click on
an status message of 404
send button.

1. Select Post and give the The response should

URI as mentioned. indicate the key is going to
2. Click on Body to be terminated (on later Manual P1
provide data and click on stage) is successfully
send button. notified to device OEM's

The keystatus should be 15

1. Select digital_key table
for the data which is
under vos_srv schema in Manual P1
mentioned in
the database
TC_FKTW_10

1. Select Post and give the

In the input data the key
URI as mentioned.
"digital" is missing, so it
2. Click on Body to Manual P1
should throw an error with
provide data and click on
an status message of 404
send button.

1. Select Post and give the

The response should throw
URI as mentioned.
an error with an status code
2. Click on Body to Manual P1
404 If the vehicle identifier
provide data and click on
not exists in the database
send button.
1. Select Post and give the
The response should throw
URI as mentioned.
an error with an status code
2. Click on Body to Manual P1
404 If the vehicle identifier
provide data and click on
not exists in the database
send button.

1. Select Post and give the The response should throw

URI as mentioned. an error with an status code
2. Click on Body to 400 If the vehicle identifier Manual P1
provide data and click on parameter in null in the
send button. request body

1. Select Post and give the The response should throw

URI as mentioned. an error with an status code
2. Click on Body to 400 If the vehicle identifier Manual P1
provide data and click on parameter in null in the
send button. request body

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
200
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
200
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
400
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
400
provide data and click on
send button.
1. Select Post and give the
URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
200
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
2. Click on Body to The Status Should be 404 Manual P1
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
2. Click on Body to The Status Should be 404 Manual P1
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
200
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
404
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status message should
2. Click on Body to Manual P1
be Unexpected Error
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status message should
2. Click on Body to Manual P1
be Unexpected Error
provide data and click on
send button.
1. Select Post and give the
URI as mentioned.
The Status message should
2. Click on Body to Manual P1
be Unexpected Error
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
200
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
404
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status message should
2. Click on Body to Manual P1
be Unexpected Error
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status message should
2. Click on Body to Manual P1
be Unexpected Error
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
The Status code should be
2. Click on Body to Manual P1
200
provide data and click on
send button.

1. Select Post and give the

URI as mentioned.
It should thorw an error
2. Click on Body to Manual P1
with an error message
provide data and click on
send button.
1. Select Post and give the
URI as mentioned.
It should thorw an error
2. Click on Body to Manual P1
with an error message
provide data and click on
send button.

1. Select Post and give the The Status code should be

URI as mentioned. 200 with an Status message
2. Click on Body to of Terminate key Manual P1
provide data and click on successfully notified to
send button. device OEM's

1. Select Post and give the The Status code should be

URI as mentioned. 200 with an Status message
2. Click on Body to of Terminate key Manual P1
provide data and click on successfully notified to
send button. device OEM's

1. Select Post and give the The Status code should be

URI as mentioned. 200 with an Status message
2. Click on Body to of Terminate key Manual P1
provide data and click on successfully notified to
send button. device OEM's

1. Select Post and give the The Status code should be

URI as mentioned. 200 with an Status message
2. Click on Body to of Terminate key Manual P1
provide data and click on successfully notified to
send button. device OEM's

1. Select Post and give the The Status message should

URI as mentioned. be Digital Key with
2. Click on Body to VehicleIdentifier and Manual P1
provide data and click on SlotIdentifier and status
send button. [ACTIVE] not found

1. Select Post and give the

URI as mentioned. It should throw an error
2. Click on Body to and key status remains the Manual P1
provide data and click on active
send button.
 Logs (Log
ODC trigger (Optional) Actual Result/behavior Test Execution status directly/Embed
Log/Provide Link)

The Actual is is same as

Pass NA
expected

{
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
successfully notified to
{device OEM's"
"responseHeader": {
"statusCode":
"400",
"subStatusCode": Logs cpatured in FKTW
"15", Pass
zip file with test case Id
"statusMessage":
"Illegal parameter :
color"

The Actual is is same as Logs cpatured in FKTW

Pass
expected zip file with test case Id

{
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
successfully notified to
device OEM’s"
{
"responseHeader": {
"statusCode":
"400",
"subStatusCode": Logs cpatured in FKTW
"15", Pass
zip file with test case Id
"statusMessage":
"Illegal parameter :
color"
{
"timestamp": "2023-
08-
18T08:06:37.059+00:00" Logs cpatured in FKTW
, Pass
zip file with test case Id
"status": 405,
"error": "Method Not
Allowed",
{
"timestamp": "2023-
08-
18T08:03:15.324+00:00" Logs cpatured in FKTW
, Pass
zip file with test case Id
"status": 405,
{ "error": "Method Not
Allowed",
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
successfully notified to
device OEM's"

The Actual is is same as Logs cpatured in FKTW

Pass
expected zip file with test case Id

{
"timestamp": "2023-
08-
18T08:11:53.584+00:00" Logs cpatured in FKTW
, Pass
zip file with test case Id
"status": 404,
{ "error": "Not Found",
"path": "/terminate" {
"responseHeader":
"statusCode":
"404",
"subStatusCode":
"50110", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Digital Key with
VehicleIdentifier
[222200000000061A]
{
"responseHeader": {
"statusCode":
"404",
"subStatusCode":
"50110", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Digital Key with
VehicleIdentifier
[222200000000061A]
{
"responseHeader": {
"statusCode":
"400",
"subStatusCode": Logs cpatured in FKTW
"13", Pass
zip file with test case Id
"statusMessage":
"vehicleIdentifier is
{mandatory"
"responseHeader": {
"statusCode":
"400",
"subStatusCode": Logs cpatured in FKTW
"13", Pass
zip file with test case Id
"statusMessage":
{"vehicleIdentifier is
mandatory"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
successfully notified to
device OEM’s"
{
"responseHeader": {
"statusCode":
"400", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"13",
"statusMessage":
"Invalid vehicleIdentifier"
{
"responseHeader": {
"statusCode":
"400", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"13",
"statusMessage":
"Invalid vehicleIdentifier"
{
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Fail
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Fail
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
successfully notified to
device OEM's"
{
"vehicleIdentifier":
"2222000000000622",
"slotIdentifier": Logs cpatured in FKTW
12345678, Pass
zip file with test case Id
"origin":
"VEHICLE_OEM"
}
{
"responseHeader": {
"statusCode":
"500", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"50000",
"statusMessage":
"Unexpected Error"
{
"responseHeader": {
"statusCode":
"500", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"50000",
"statusMessage":
"Unexpected Error"
{
"responseHeader": {
"statusCode":
"500", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"50000",
{ "statusMessage":
"Unexpected Error" {
"responseHeader":
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"404",
"subStatusCode":
"50110", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Digital Key with
VehicleIdentifier
[2222000000000622]
{
"responseHeader": {
"statusCode":
"500", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"50000",
"statusMessage":
"Unexpected Error"
{
"responseHeader": {
"statusCode":
"500", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"50000",
{ "statusMessage":
"Unexpected Error" {
"responseHeader":
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
successfully notified to
device OEM's"
{
"responseHeader": {
"statusCode":
"500", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"1",
"statusMessage":
"Error"
{
"responseHeader": {
"statusCode":
"500", Logs cpatured in FKTW
"subStatusCode": Pass
zip file with test case Id
"1",
{ "statusMessage":
"Error" "responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"200",
"subStatusCode":
"0", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Terminate key
{successfully notified to
device OEM's"
"responseHeader": {
"statusCode":
"404",
"subStatusCode":
"50110", Logs cpatured in FKTW
"statusMessage": Pass
zip file with test case Id
"Digital Key with
VehicleIdentifier
{[2222000000000622]
"responseHeader": {
"statusCode":
"400",
"subStatusCode": Logs cpatured in FKTW
"13", Pass
zip file with test case Id
"statusMessage":
"Invalid Termination
Origin"
Bug Id Remarks

NA NA

NA NA

NA NA

NA NA

NA NA

NA NA
NA NA

NA NA

NA NA

NA NA

NA NA

NA NA

The SRS documents

NA
has been changed
 The SRS documents
NA
has been changed

NA NA

NA NA

NA NA

NA NA

NA NA

NA NA
NA NA

By considering the client

NA input releasing the API
with defect

By considering the client

NA input releasing the API
with defect

NA NA

NA NA

NA NA

NA NA
NA NA

NA NA

NA NA

NA NA

NA NA

NA NA

NA NA
NA NA

NA NA

NA NA

NA NA

NA NA

NA NA

NA NA
 Test Summary Report

Softwar

Test Execution Summary

Planned
Executed Test Test Case Pass Test Case Not % of Test Case
Test Case Test Case Fail Count
Case Count Count tested Count Passed
Count

41 41 39 2 0 95%

Test Case Selection

Test Round ID Variant Feature/Module Mode of testing Priority ODC Trigger

 Test Summary Report

Friend Key
Friend Key ODC trigger
Termination_Web NA Manual P1
termination(web) (Optional)
1.0
 Test Summary Report

Software Qualification - Friend Key Termiantion Web

Test Summary Report

Test Summary : M2

Test Completion Evaluation

Test Case Count - Passed vs Failed
Test Completion
Reason for Not Meeting Test
% of Test Case Failed Criteria
[ Met/Not]
completion criteria 2

5% Met 39
Test Case Pass Count Test Case Fail Count Test

Test Summary : Roundwise Details

Test Environment Details - Actual

Build/ Release Hardware

Rationale for Test Case Selection Executed by Executed date
No Version
 Test Summary Report

Requirement Coverages Namadeva 18-Aug-23 M2 NA

 Test Summary Report

t Case Count - Passed vs Failed

39
Pass Count Test Case Fail Count Test Case Not tested Count

tual Test Result Summary

Test Case Test Case

Test Specification Test Case Test Case Test case % of Test % of Test
Planned Executed
document with Version Pass Count Fail Count Not Tested Case Passed Case Failed
Count Count
 Test Summary Report

1 41 41 39 2 0 95% 5%
Test Summary Report
 Guideline for using the Test Rep
Cover Page
<Project Name>

<SW Qualification/ SYS Qualification/SYS Integration/ SW

Integration/ SW Unit Testing> - Test Report

QMS No :
QMS Version:

No : TDAU/Proj WON/TE/03
Ver : <Document Revision number >
<DD-MM-YY>
Prepared by
Approved by

Revision History

Summary Report <<Milestone >>

Summary Report <<Milestone >>

SW Qualification/ SYS Qualification/SYS Integration/ SW
Integration/ SW Unit Testing
Test Summary Report

Test Summary : <Milestone Name>

Test Execution Summary

Test Completion Evaluation

Test Summary : Round wise Detail

Steps to be followed for test case selection, execution and test
summary generation - For each round/iteration
 Guideline for using the Test Report
Cover Page
Mention the Project Name

Keep the relevant Test Area and remove the rest ( <SW Qualification/ SYS Qualification/SYS Integration/ SW Integration/ SW

No need to change this field as it’s the template version number

This is the Document ID. In this , add the relevant project WON no.
Mention the latest Test Report document revision number
Latest Test Report Revision Date
Update the author name based on the latest revision details while using the Test Report in the project
Update the approver name based on the latest revision details while using Test Report in the project
Template revision history to be replaced with Test Report Revision History at the time of usage in the project. Update the
Rev.No, Date, Author, Reviewed/Approved by and Description.
Summary Report <<Milestone >>
"Milestone" to be replaced with project milestone name
Test execution summary and test completion evaluation shall be updated only for a milestone

Keep the relevant Test Area and remove the rest ( <SW Qualification/ SYS Qualification/SYS Integration/ SW Integration/ SW

Update the Milestone number / name.

This section includes summary of the test cases executed for the milestone. This shall be auto populated [ macro generated] fro

Below details shall be auto populated by the macro considering the test execution rounds
"Planned Test Case Count", Executed Test Case Count, Test Case Pass Count,Test Case Fail Count,Test Case Not tested Coun
Passed, % of Test Case Failed

Test Completion Criteria [ Met/Not] to be filled.

Reason for Not Meeting Test completion criteria : Test completion evaluation shall be performed by the tester based on the
summary and the test completion criteria specified in the test plan. In case of any deviations, reason for not meeting the test com
residual risks, factors that blocked progress shall be updated in the milestone deviation report and provide the path of the miles
Pass/ Fail graph shall be automatically plotted based on the test execution summary

Test Summary : Round wise Details

Step 1: Click "Select Test Cases".
Step 2: GUI will pop up for test case selection . There are 2 options for selecting the Test cases.
*Test Specification
*From previous rounds [ For re executing the test cases which are already run in the previous round/rounds. This is for valida
Fail test cases in previous rounds ]
Browse the test specification sheet and select the relevant fields applicable for test case selection. "Rationale for Test Case Se
based on the test strategy specified in the test plan
Step 3: A new test report shall be auto created as another tab with Round name provided in the GUI. Selected data shall be pop
Round in Test Case Selection table [ Variant, Feature/Module, Mode of testing, Priority, ODC Trigger, Rationale for Test Case
Step 4: Test Environment Details - Actual: Fill the test environment details before test execution [ Executed by, Executed date
Hardware Version, Test Specification document with Version ]
Step 5: Execute the selected test cases and fill the fields based on status [ Actual Result/behaviour, Test Execution status, Logs
Log/Provide Link), Bug Id, Remarks ] in Test report sheet.
Step 6: After the test execution and updation of test report details for the specific round , click "Update Test Result Summar
Report Sheet". Details shall be auto populated from test report [ Test Case Planned Count, Test Case Executed Count, Test Ca
Case Fail Count, Test case Not Tested, % of Test Case Passed, % of Test Case Failed ]. Based on the Round summary, "Test E
will showcase the Milestone level Test Summary Data.