Simulation-based interface testing automation system and method for robot software components

• US 8,601,436 B2
• Filed: 08/10/2010
• Issued: 12/03/2013
• Est. Priority Date: 06/09/2010
• Status: Active Grant

• Current Assignee: Knu-Industry Cooperation Foundation
• Original Assignee: Knu-Industry Cooperation Foundation
• Inventors: Park, Hong Seong, Kang, Jeong Seok, Choi, Hyeong Seob, Meng, Sang Woo, Kim, Si Wan
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Sinha, Ravi K
• Application Number:
  US12/853,475
• Publication Number:
  US 20110307860A1
• Time in Patent Office: 1,211 Days
• Field of Search: None
• US Class Current: 717/107
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable
• CPC Class Codes: G06F 8/30 Creation or generation of source code

Abstract

A testing tool for verifying a reliability of robot software components is provided, and more particularly, a simulation-based interface testing automation system and method that may automatically perform a test for functions and performance of an interface with respect to robot software components are provided. Thus, it is possible to efficiently perform a test for an interface of robot software components. In particular, it is possible to automatically generate test cases required for testing, to perform a test in various languages, and to perform a test suitable for a robot.

Claims

1. A testing automation method, comprising:

receiving, as input by a user, test specification information and an expected result value for a test case;

generating a test case based on interface representation information and the test specification information, the interface representation information and the test specification information being associated with a robot software component of a target robot to be tested;

generating a source code of a test application based on the test case, the source code being used to test the robot software component;

compiling the source code of the test application using the test case, connecting the source code to a robot hardware simulator while executing the compiled test application, and outputting a result corresponding to the test case, said result being based at least in part on information received from the robot hardware simulator while executing the compiled test application; and

comparing the output result with the expected result value,

wherein the outputting of the result comprises;

compiling a source code of a test application, when a build of the test application is requested;

controlling a test simulation environment, an object in the environment, and an operation of the target robot using components of the test application and the robot hardware simulator based on the test case, when executing the test application having the compiled source code; and

outputting an execution result of the controlled test application,

wherein the generating of the test case comprises;

parsing the interface representation information and extracting information regarding input and output parameters of the robot software component;

generating a plurality of test case candidates of the robot software component based on the test specification information; and

combining the plurality of generated test case candidates to generate at least one test case based on the test specification information.

2. The testing automation method of claim 1, wherein the controlling comprises connecting the test application to the robot hardware simulator and controlling at least one of a test driver component, a simulation control component, and a test stub component of the test application, based on the test case.

3. The testing automation method of claim 1, further comprising:

requesting a build of the test application at a predetermined point in time or periodically.

4. The testing automation method of claim 1, wherein the generating of the plurality of test case candidates comprises:

generating test case candidates of a type of a test case for input parameter, and a type of a test case for simulation control, based on the interface representation information and the test specification information.

5. The testing automation method of claim 1, wherein the generating of the source code comprises:

generating at least one of a test driver component, a simulation control component, and a test stub component, based on the test case and information regarding a robot software component of the target robot to be tested; and

connecting at least two of the generated test driver component, the generated simulation control component, and the generated test stub component to each other, and generating a single source code of the test application.

6. A testing automation system, comprising:

a testing automation server on a host computer having a processor to generate a test case, and a source code of a test application, based on interface representation information and test specification information, the test specification information being received as input by a user, the interface representation information and the test specification information being associated with a robot software component of a target robot to be tested;

a test build agent to compile the source code of the test application using the test case, and to output a result corresponding to the test case while executing the compiled test application;

a robot hardware simulator to perform a simulation of virtual robot hardware and a robot test environment based on an operation of the test build agent, the robot hardware simulator being connected to the test build agent, wherein the output result is based at least in part on information received from the robot hardware simulator while executing the compiled test application; and

a test driver component to compare the output result with an expected result value, received as input by a user,

wherein the test build agent controls a test simulation environment, an object in the environment, and an operation of the target robot using components of the test application and the robot hardware simulator based on the test case, when executing the test application having the compiled source code,

wherein the testing automation server comprises;

an interface parser to parse the interface representation information and to extract information regarding input and output parameters of the robot software component;

a test case candidate generator to generate a plurality of test case candidates of the robot software component based on the test specification information; and

a test case combination generator to generate a plurality of test cases of the robot software component through a combination of the plurality of generated test case candidates.

7. The testing automation system of claim 6, wherein the test build agent controls at least one of the test driver component, a simulation control component, and a test stub component of the test application, based on the test case, and controls an operation of the robot hardware simulator.

8. The testing automation system of claim 6, wherein the testing automation server further comprises a test build scheduler to request a build of the test application at a predetermined point in time or periodically.

9. The testing automation system of claim 6, wherein a plurality of test build agents exist based on a plurality of test target environments, and

wherein, when a request for a build of a test application is received from a user, the testing automation server selects a test build agent associated with the request from among the plurality of test build agents, and transfers the request to the selected test build agent.

10. The testing automation system of claim 6, wherein the test case candidate generator generates test case candidates of a type of a test case for input parameter, and a type of a test case for simulation control, based on the interface representation information and the test specification information.

11. The testing automation system of claim 6, wherein the testing automation server generates at least one of the test driver component, a simulation control component, and a test stub component, based on the interface representation information and the test specification information, connects at least two of the generated test driver component, the generated simulation control component, and the generated test stub component to each other, and generates a single source code of the test application.