Automation of D-bus communication testing for bluetooth profiles

• US 9,772,919 B2
• Filed: 03/14/2013
• Issued: 09/26/2017
• Est. Priority Date: 03/14/2013
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Rajagopal, Vidya, Chandrababu naidu, Divya Kilari, Grace, Marin, Kudva, Sudhir
• Primary Examiner(s): Satanovsky, Alexander
• Assistant Examiner(s): Suarez, Felix
• Application Number:
  US13/829,949
• Publication Number:
  US 20140278199A1
• Time in Patent Office: 1,657 Days
• Field of Search: 702108, 702119, 702121, 702122, 702123, 702186, 379 101, 717130
• CPC Class Codes: G06F 11/2733 Test interface between tester and unit under test
• CPC Class Codes: G06F 11/3668 Software testing software testing in telephone exchanges H04M3/242, testing of hardware G06F11/22

Abstract

An electronic control unit (ECU) is tested by an automated D-bus testing tool in a first device. The test tool establishes one or more secure shells between the first device and the ECU. The tool reads test input data from an Excel input file. The ECU comprises a software stack including a test client, a Bluetooth middle layer and a hardware abstraction layer, that communicate internally relative to the ECU, via a D-bus. The test tool sends function calls and parameters via the secure shells to the ECU to test execution of Bluetooth functions and/or Bluetooth profiles. The function calls enable simulation of a human machine interface by the test client. The tool monitors API call returns and logs D-bus communications via the one or more secure shells. The test tool outputs test verdict information and/or D-bus communication logs as text in an Excel file.

Claims

1. A method for automated testing of Bluetooth operations of a Bluetooth module in an electronic control unit (ECU) device for a motor vehicle in communication with a mobile communication device, the method comprising:

in an automated testing tool hosted by a first device;

reading test input data from text in an input file on said first device for testing Bluetooth operations of an ECU second device to be used in a motor vehicle wherein;

said Bluetooth operations of said ECU second device controls Bluetooth communication between said ECU second device and a mobile communication third device, said mobile communication third device being located within a distance from said ECU second device for making a Bluetooth radio connection;

said ECU second device comprises two or more layers of software, said two or more layers of software including a Bluetooth module and a test client that tests said Bluetooth module within said ECU second device,

said Bluetooth module and said test client communicate within said ECU second device via a daemon bus (D-bus),

said Bluetooth module further communicates via a Bluetooth radio within said ECU second device to said mobile communication third device, in order to control operations of said mobile communication third device;

establishing one or more secure shell sessions for data communication between said first device and said ECU second device;

calling functions defined in said test client of said ECU second device utilizing a first secure shell session;

monitoring communication on said D-bus utilizing a second secure shell;

sending one or more function calls for said testing Bluetooth operations of said ECU second device to said ECU second device via aid first secure shell session, based on said read test input data, wherein said one or more functional calls initiates communication between said Bluetooth module of said ECU second device and said mobile communication third device via said Bluetooth radio;

receiving by said automated testing tool hosted by said first device, return information from said ECU second device via said second secure shell session, wherein said return information corresponds to said Bluetooth operations of said ECU second device responsive to said one or more function calls for said testing Bluetooth operations of said ECU second device;

comparing expected responses from said text in said read test input file to said return information from said ECU second device to validate execution of application program interfaces called by said Bluetooth module of said ECU second device responsive to said function calls;

determining test pass and test fail verdict information based on said comparison of said expected responses to said return information from said ECU second device; and

writing text in an output file, said text comprising said test pass and said test fail verdict information based on said comparison of said expected responses to said return information from said ECU second device.

2. The method of claim 1, further comprising sending one or more test parameters corresponding to said one or more function calls to said ECU device via said first secure shell sessions, based on said read test input data.

3. The method of claim 1, wherein said one or more function calls sent to said ECU device enable said test client of said two or more layers of software to simulate a human machine interface module.

4. The method of claim 1, wherein said one or more function calls for said testing said Bluetooth operations of said ECU device are sent from said test client of said two or more layers of software in said ECU device via said D-bus to said Bluetooth module for communicating via said Bluetooth radio in said ECU device to said first mobile communication device to control said operations in said first mobile communication device communicatively coupled to said Bluetooth radio.

5. The method of claim 1, further comprising initializing said Bluetooth radio in said ECU via a third secure shell session wherein said first, second and third secure shell sessions are concurrently maintained in parallel by said automated testing tool to send commands to said ECU device and to monitor said operations of said ECU device, responsive to said one or more function calls for said testing Bluetooth operations of said ECU device.

6. The method of claim 1, wherein said return information comprises information communicated to or from said Bluetooth module via said D-bus, corresponding to said one or more function calls for said testing Bluetooth operations of said ECU device.

7. The method of claim 1 further comprising, in said automated testing tool, comparing expected responses from said text in said read test input file to said received return information from said ECU device, to determine said test verdict information.

8. The method of claim 1, wherein said first device and said ECU second device are communicatively coupled via said mobile communication third device and a mobile communication fourth device;

and

said automated testing tool verifies Bluetooth operations of said ECU second device utilizing;

a call initiated automatically by said automated testing tool of said first device from said mobile communication third device to said mobile communication fourth device;

or

a call initiated automatically by said automated testing tool of said first device from said mobile communication fourth device to said mobile communication third device;

based on said read test input data.

9. The method of claim 1, wherein said ECU device comprises an embedded system that controls one or more electrical systems or subsystems in a vehicle and said Bluetooth operations of said ECU device include communication via said D-bus with said Bluetooth module based on one or more Bluetooth profiles, after receiving by said ECU device, one or more of an audible voice command, a command in a wireless signal, a command in an optical signal or a command in a wire line signal.

10. A system for automated testing of Bluetooth operations of a Bluetooth module in an electronic control unit (ECU) device for a motor vehicle in communication with a mobile communication device, the system comprising one or more circuits or processors in a first device, said one or more circuits or processors perform:

in an automated testing tool hosted by said first device;

read test input data from text in an input file for testing Bluetooth operations of an ECU device to be used in a motor vehicle, wherein;

said Bluetooth operations of said ECU device controls Bluetooth communication between said ECU device and a first mobile communication device, said first mobile communication device being located within a distance from said ECU device for making a Bluetooth radio connection;

said ECU device comprises two or more layers of software, said two or more layers of software including a Bluetooth module and a test client that tests said Bluetooth module within said Bluetooth module,

said Bluetooth module and said test client communicate within said ECU device via a daemon bus (D-bus),

said Bluetooth module further communicates via a Bluetooth radio within said ECU device to a first mobile communication device, in order to control Bluetooth operations of said first mobile communication device;

establish one or more secure shell sessions with said ECU device for data communication between said first device and said ECU device;

call functions defined in said test client of said ECU device utilizing a first secure shell session;

monitor communication on said D-bus utilizing a second secure shell;

send one or more function calls for said testing operations of said ECU device to said ECU device via said first secure shell sessions, based on said read test input data, wherein said one or more functional calls initiates communication between said Bluetooth module of said ECU device and said first mobile communication device via said Bluetooth radio;

receive by said automated testing tool hosted by said first device, return information from said ECU device via said second secure shell session, wherein said return information corresponds to said Bluetooth operations of said ECU device responsive to said one or more function calls for said testing Bluetooth operations of said ECU device;

compare expected responses from said text in said read test input file to said return information from said ECU device to validate execution of application program interfaces called by said Bluetooth module of said ECU device responsive to said function calls;

determine test pass and test fail verdict information based on said comparison of said expected responses to said return information from said ECU device; and

write text in an output file, said text comprising said test pass and said text fail verdict information based on said comparison of said expected responses to said return information from said ECU device.

11. The system of claim 10, wherein said one or more processors or circuits send one or more test parameters corresponding to said one or more function calls to said ECU device via said first secure shell sessions, based on said read test input data.

12. The system of claim 10, wherein said one or more function calls sent to said ECU device enable said test client of said two or more layers of software to simulate a human machine interface module.

13. The system of claim 10, wherein said one or more function calls for said testing said Bluetooth operations of said ECU device are sent from said test client of said two or more layers of software in said ECU device via said D-bus to said Bluetooth module for communicating via said Bluetooth radio in said ECU device to said first mobile device to control said operations in said first mobile communication device communicatively coupled to said Bluetooth radio.

14. The system of claim 10, wherein said automated testing tool in the first device is configured for initializing said Bluetooth radio in said ECU via a third secure shell session wherein said first, second and third secure shell sessions are concurrently maintained in parallel by said automated testing tool to send commands to said ECU device and to monitor said Bluetooth operations of said ECU device, responsive to said one or more function calls for said testing Bluetooth operations of said ECU device.

15. The system of claim 10, wherein said return information comprises information communicated to or from said Bluetooth module via said D-bus, corresponding to said one or more function calls for said testing Bluetooth operations of said ECU device.

16. The system of claim 10, wherein said one or more processors or circuits perform:

in said automated testing tool, compare expected responses from said text in said read test input file to said received return information from said ECU device, to determine said test verdict information.

17. The system of claim 10, wherein said first device and said ECU device are communicatively coupled via said first mobile communication device and a second mobile communication device;

and

said automated testing tool verifies Bluetooth operations of said ECU device utilizing;

a call initiated automatically by said automated testing tool of said first device from said first mobile communication device to said second mobile communication device;

or

a call initiated automatically by said automated testing tool of said first device from said second mobile communication device to said first mobile communication device;

based on said read test input data.

18. The system of claim 10, wherein said ECU device comprises an embedded system that controls one or more electrical systems or subsystems in a vehicle and said Bluetooth operations of said ECU device include communication via said D-bus with said Bluetooth module based on one or more Bluetooth profiles, after receiving by said ECU device, one or more of an audible voice command, a command in a wireless signal, a command in an optical signal or a command in a wire line signal.

19. A non-transitory computer readable medium having stored thereon one or more instructions for automated testing of Bluetooth operations of a Bluetooth module in an electronic control unit (ECU) device for a motor vehicle in communication with a mobile communication device, said one or more instructions executable by one or more processors to cause the one or more processors to perform steps comprising:

in an automated testing tool hosted by a first device;

reading test input data from text in an input file for testing Bluetooth operations of an ECU device to be used in a motor vehicle, wherein;

said Bluetooth operations of said ECU device controls Bluetooth communication between said ECU device and a first mobile communication device, said first mobile communication device being located within a distance from said ECU device for making a Bluetooth radio connection;

said ECU device comprises two or more layers of software, said two or more layers of software including a Bluetooth module and a test client that tests said Bluetooth module,

said Bluetooth module and said test client communicate within said ECU device via a daemon bus (D-bus),

said Bluetooth module further communicates via a Bluetooth radio within said ECU device to said first mobile communication device, in order to control operations of said first mobile communication device;

establishing one or more secure shell sessions with said ECU device for data communications between said first device and said ECU device;

calling functions defined in said test client of said ECU device utilizing a first secure shell session;

monitoring communication on said D-bus utilizing a second secure shell;

sending one or more function calls for said testing operations of said ECU device to said ECU device via said second secure shell session, based on said read test input data, wherein said one or more functional calls initiates communication between said Bluetooth module of said ECU device and said first mobile communication device via said Bluetooth radio;

receiving by said automated testing tool hosted by said first device, return information from said ECU device via said second secure shell sessions, wherein said return information corresponds to said operations of said ECU device responsive to said one or more function calls for testing operations of said ECU device;

comparing expected responses from said text in said read test input file to said return information from said ECU device to validate execution of application program interfaces called by said Bluetooth module of said ECU device responsive to said function calls;

determining test pass and test fail verdict information based on said comparison of said expected responses to said return information from said ECU device; and

writing text in an output file, said text comprising said test pass and said test fail verdict information based on said comparison of said expected responses to said return information from said ECU device.

20. The non-transitory computer readable medium of claim 19, wherein said one or more function calls sent to said ECU device enable said test client of said two or more layers of software to simulate a human machine interface module.

21. The non-transitory computer readable medium of claim 19, wherein said one or more function calls for said testing operations of said ECU device are sent from said test client of said two or more layers of software in said ECU device via said D-bus to said Bluetooth module for communicating via said Bluetooth radio in said ECU device to said first mobile communication device to control said Bluetooth operations in said first mobile communication device communicatively coupled to said Bluetooth radio.

22. The non-transitory computer readable medium of claim 19 further comprising instructions for initializing said Bluetooth radio in said ECU via a third secure shell session wherein said first, second and third secure shell sessions are concurrently maintained in parallel by said automated testing tool to send commands to said ECU device and to monitor said Bluetooth operations of said ECU device responsive to said one or more function calls for said testing operations of said ECU device.

23. The non-transitory computer readable medium of claim 19, wherein said return information comprises information communicated to or from said Bluetooth module via said D-bus, corresponding to said one or more function calls for said testing operations of said ECU device.

24. The non-transitory computer readable medium of claim 19, wherein said first device and said ECU device are communicatively coupled via said first mobile communication device and a second mobile communication device;

and

said automated testing tool is operable to verify Bluetooth operations of said ECU device utilizing;

a call initiated automatically by said automated testing tool of said first device from said first mobile communication device to said second mobile communication device;

or

a call initiated automatically by said automated testing tool of said first device from said second mobile communication device to said first mobile communication device;

based on said read test input data.