0% found this document useful (0 votes)
55 views

QVT Testing Documentaion - Original

Uploaded by

Siva Krishna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
55 views

QVT Testing Documentaion - Original

Uploaded by

Siva Krishna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Status:

Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

QVT Testing Document

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

Contents
1 Introduction....................................................................................................................................3
2 Hardware Required........................................................................................................................3
3 Software Required..........................................................................................................................4
4 QVT Functionality..........................................................................................................................4
4.1 Flashing......................................................................................................................................5
4.2 Logging.......................................................................................................................................6
4.3 CANoe - CAN compatibility......................................................................................................8
4.4 Power Management....................................................................................................................9
4.5 Display......................................................................................................................................10
4.6 Home Screen.............................................................................................................................11
4.7 Navigation................................................................................................................................11
4.8 Media........................................................................................................................................11
4.8.1 USB.................................................................................................................................11
4.8.2 IPod..................................................................................................................................12
4.8.3 Bluetooth.........................................................................................................................12
4.8.4 AUX.................................................................................................................................12
4.8.5 Android Auto...................................................................................................................12
4.8.6 Carplay.............................................................................................................................13
4.8.7 Wireless Carplay..............................................................................................................13
4.9 System......................................................................................................................................13
4.10 HMI........................................................................................................................................13
4.11 Sensor.....................................................................................................................................14

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

1 Introduction
This document specifies the Quick Verification Test (QVT) procedure, where the software
testing of end user functionalities like Startup shutdown, Touch, Audio, Voice Recognition,
Smartphone and IPhone connections with the target are carried out. It also tests some functionalities
like CAN compatibility, TTFis and putty connection which are used for debugging the issue by the
project team. The result of this testing is used to decide if a build is stable enough to proceed with
further testing.

2 Hardware Required
 AIVI2 / PIVI3.1 Target
 HMI Display
 Debug board
 Speaker
 Mic
 Molex hub
 Regulated DC Power supply
 Patch antenna with receiver
 iPhone
 Android Phone
 USB Pendrive
 AUX media source

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

 Serial Cables
 Display Cable
 CAN Case
 Flashing Cable

3 Software Required
 Putty
 Console
 CANoe
 DL Tool
 WinSCP

4 QVT Functionality
Target connected with the Ignition, ACC and Bat to +VE and GND cable to –VE to power supply.

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

4.1 Flashing

 USB Stick Flashing (For Stable target):


 In debug board bring the --11000000 mode.
 Copy the stick data from the binary copied to the USB Pendrive
 Ex:(E:\Gen4_QVT\StabiBranch\20.1S2021.06.4\
AI_PRJ_RN_AIVI_21.0V08_RFS_20.1S2021.06.4_Autosar_stabi_20.1S2020.05.1_gen4\
rnaivi2\stick)

 Connect RNDIS cable of target – USB to USB connector – USB Pendrive


 DL Tool Flashing (For Stable/Unstable target):
 Connect RNDIS cable of target to PC
 In Debug Board bring the --01110000 mode.
 Open DL Tool
 Click on SETUP in menu bar and Paste the flashing path, provided in Mail
 After flashing is completed the colour changes from blue to green and seen as
ALL_COMPLETE
 Progress bar is seen in display while software is getting flashed.

 Check IMX and RFS version


In Putty after completion of flashing and obtaining #root prompt write below commands
root@MYCAR:~# cat /opt/bosch/cc_label.txt
root@MYCAR:~# cat /rfs_version.txt

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

4.2 Logging
Copy the .trc files of AUTOSAR and Full Project with the version specified in the mail
request to the PC.
 AUTOSAR .trc
Ex: AUTOSAR: 20.1S2021.05.1
 Full Project .trc
Ex: PROJECT VIEW: AI_PRJ_RN_AIVI_21.0V08

 For TTFis connection.


 Connect the USB cable of target to Ethernet Adapter
 Open the ConsoleIOMcore for AUTOSAR and DLT logging.
 Click on Tools in menu bar – Settings – In Log – Select the path where it should be
saved.

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

 For AUTOSAR the Script file, should be loaded


Tools – Settings – Script – Select spm_enable_additonal_v850_traces_updated.exc file path.

 Connect the Device

o AUTOSAR
Select – GEN3FLEX@COM1 – Load aivi2_cfg04_board.trc file for specified AUTOSAR version.
o DLT
Select – GEN3FLEX@DLT – Load aivi2_cfg04_board.trc and prj_overall_a.trc files for specified
AUTOSAR and Full Project version.
 Once the TTIF’s connection established with AUTOSAR and DLT the traces are observed
and click on User Log ON/OFF.
 For Putty connection
 Connect serial cable to UART uP port of GEN4 debug board
 Open Putty and establish a serial connection via COMX port with speed=115200
Test Cases:

A. DLT Traces should be available on Console window.


B. Traces should be seen in putty.
C. Target should reboot, when the below command is executed in GEN3FLEX@COM
console. "SYSINFO_TEST_ECUM_GODOWN"
D. Execute "reboot" command in putty, traces should be seen during target reset.
E. Execute "lxc-ls -f" command in putty, which should be executed successfully.

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

4.3 CANoe - CAN compatibility

Copy the .odx-e files from the Full Project release mail for the AIVI/PIVI target to the PC.

 Open CANoe Software tool


Note: Initial Settings if opening for first time–

 Load Configuration file A-IVI_Scope3_C1A_HS_CANoe85.cfg.


 Menu bar - Hardware – Channel Mapping
o CAN 1 – MCAN – Virtual CAN Bus 1 Channel 1
o CAN 2 – VCAN – Virtual CAN Bus 1 Channel 2

 Click on UDT Signal (VCAN/MCAN) – Unit Power State (ON) – Power Signal
Transmission (Start) – VCAN and MCAN (Start) - VCAN (Start) – MCAN (Start).
Test Cases:

A. Switch ON the Nissan Head Unit from SYSTEM_OFF to SYSTEM_ON state 1 to 2 times
via CAN, no resets should be observed.
B. Target should be stable, within 60 Seconds using CAN.
C. Click on Customer Configuration which will be seen at the bottom of the screen Execute:
Default session start, Extended Diagnostic session start and KeyOffOnReset Reset, for
which observe the positive response.
D. Click on Target Configuration which will be seen at the bottom of the screen.

 Browse for the path for a) PD, b) CD DEF, and c) CD which is saved on the desktop
 Select Scope 2.X

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

 Click on Configuration type individually first PD


 In select a variant: Write the target number which can be found on the top of it.
 Then Click on: Get Fingerprint of selected variant
 Then click on Start - Green Traces can be seen
 Click on Verify Fingerprint
 Repeat the same steps for PD, CD DEF and CD
 At last click on Store costumer configuration persistent where we observe the
KeyOffOnReset as positive response.

4.4 Power Management

Connect Battery, Ground, and Ignition and Auto ACC cable to the power supply.
Test Cases:

A. Target should boot up and current consumption should be from 2.5-2.8 A.


B. Remove Ignition and Auto ACC pin from power supply, target should shut down within 3
Minutes.
C. Connect back Ignition and Auto ACC pin to power supply, after boot up, check for cyclic
resets of target for 5mins.
D. No resets should be observed when Ignition and Auto ACC pin are removed from power
supply are connected back within 2mins.
E. Audio should be working when wake up is connected back during Shutdown
Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

4.5 Display

Note: If the touch response not working change the Byte 57 to 0XCO in CAN simulation.

Steps to carry out:


 Establish the CAN connection
 Click on Customer Diagnosis
 In Session click Default Session Start and Extended Diagnostic Session
 In Variant Coding right click on Start System. Information Common Write.
 In Variant Coding select Initialize Parameter.
 Change the Byte 57 to 0XC0 and click enter , and click on Execute
 In Session click Extended Diagnostic Session Start
 In ECU Reset click KeyOffOnReset Reset.
 In Putty execute sync 3 times and reboot the target.

Test Cases:
A. Display screen should be available without any blank screen or flickering
B. Basic Touch behaviour should work. Example: Touching on Navigation icon from home
screen should open the Maps

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

4.6 Home Screen

Test Cases:
A. Default gadgets should be available on Home Screen.
B. In Home Screen swiping and page indicator should be visible.
C. Respective screen should be updated when a gadget is selected in home screen.
D. Home page is customization :
o Select settings – Customise menus – Customise Home menu – Delete / Add Widget – Save
E. Widget deletion on Home Page
F. Audio Source Customization :
o Select settings – Customise menus – Customise Audio Source – Save
G. Lower Menu Bar and Destination Menu Customization :
o Select settings – Customise menus – Customise Audio Source – Save
4.7 Navigation

If Map data corrupted in the target, steps to be followed


 Copy the TomTomNDSFull file to USB stick
 Connect RNDIS cable of target – USB to USB connector – USB Pendrive
Test Cases:
A. Map version:
o Select settings - System Updates

B. POI (Point of Interest)


o Map gadget – Search POI
4.8 Media

4.8.1 USB

Note: If the video not playing when selected the execute "VEDA_HandBrake_Input ON" command
in Gen3flex@DLT

Test Cases:
Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

A. USB media device should be detected.


B. Media tracks should be played
C. Play and Pause of the media should be played
D. USB media content should be displayed correctly
E. Video song should be played
o Source – USB – Browse – Video
4.8.2 IPod

Note: Conversion of iPhone to iPod through CAN by disabling the bit Connectivity.
Carplay

Test Cases:
A. iPod media track should be played
B. Repeat and Random option should work
C. Switching of Sources should be successful , from USB/IPod to FM
D. Ejected Media device source should be updated to Radio.

4.8.3 Bluetooth

Note: Settings – Connection – Bluetooth – Add Device

Test Cases:
A. Bluetooth should be established with Test Phone(Android / iPhone)
B. Call Features should be successful- Incoming call, Outgoing call, Ringtone and Audio.
C. Phonebook and Call History should be updated.
D. Music should be heard in speaker- Display of Artist name, album name and track name on
screen.
E. Wi-Fi connection should be established – Settings – Connection – Wi-Fi.
F. Hotspot connection should be established – Settings – Connection – Vehicle Wi- Fi.

4.8.4 AUX

Test Cases:
A. Connect the Phone to the target with the AUX cable.

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

B. Audio music should be played.


C. Check for the audio quality with the volume change.
4.8.5 Android Auto

Test Cases:
A. Connect Android Phone to target with the USB cable.
B. Call Features should be successful- Incoming call, Outgoing call, Ringtone and Audio.
C. Phonebook and Call History should be updated.
D. Music should be heard in speaker- Display of Artist name, album name and track name on
screen.
E. Map functionalities with POI guideline and audio for the route, hear over speaker.
F. Open PCTS application in Android mobile and find Car infoTests - C8 test case, check for
development or Production Certificate in the device.
4.8.6 Carplay

Test Cases:
A. Connect iPhone to target with the USB cable.
B. Call Features should be successful- Incoming call, Outgoing call, Ringtone and Audio.
C. Phonebook and Call History should be updated.
D. Messages list should be seen on Carplay screen.
E. Music should be heard in speaker- Display of Artist name, album name and track name on
screen.
F. Map functionalities with POI guideline and audio for the route, hear over speaker.
4.8.7 Wireless Carplay

Test Cases:
A. Pair the iPhone through Bluetooth of the target.
B. Turn on Carplay in iPhone.
C. Icon accessibility should be successful and with the Call Features, Music and Map.
4.9 System

Test Cases:
A. Date and time Update: Settings-> Clock -> Offset (hour) -> Offset (min) -> Clock Format ->
Date Format.
Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process
Status:
Testing Document
Reviewed by
Version: Date: Author:
Testing Procedures
1.0 Sumalatha V

B. Language Update: Settings -> System Settings -> Language


C. User Profile Modification : Settings -> Edit User
4.10 HMI

Test Cases:
A. Day/Night Feature Update: Settings -> System Settings -> Display
B. Brightness Update: Settings -> System Settings -> Display -> Brightness
C. There should be expected response for the touch on the display.
D. Display should be on once connected to the target.
E. Basic parameters should be available on the display.
4.11 Sensor

Test Cases:

A. Give a command TR_SET_CONFIG TR_CLASS_VD_SENSOR 8 in the ConsoleIOMcore


which is established with a connection for Gen3flex@DLT and observe the GNSS status in
trace VDSENSOR.
B. Observe the GNSS status in trace VDSENSOR for under voltage.

Version 1 © This is the exclusive property of ROBERT BOSCH ENGINEERING AND BUSINESS SOLUTIONS LIMITED. Without their consent, it may not be reproduced or given to third parties.
If printed, this document is an uncontrolled copy.

RBEI Internal
Te
sting Process

You might also like