Test system

Abstract

To provide a test system which can assist switching of acquisition of a test parameter of software to be tested and error analysis, and efficiently perform test work.SOLUTION: A test system for testing software to be integrated in a vehicle electronic control device as software to be tested, comprises: a test device which outputs a signal to the vehicle electronic control device; simulation test software which executes switching of acquisition of a test parameter of the software to be tested and test result determination during execution of the test of the software to be tested; an operation log recording unit which records the test parameter and a test result determined by the simulation test software; and a result display device which displays a result of the operation log recording unit. The simulation test software automatically executes the switching of acquisition of the test parameter required for determination of the test result and the test result determination.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a test system, and more particularly to a test system for software to be installed in an electronic control unit for a vehicle. [Background technology]

[0002] In the development of software to be embedded in vehicle electronic control units (ECUs: Electronic Control Units), the software to be embedded may be divided into ASW (Application Software) and BSW (Basic Software), with the vehicle manufacturer developing the ASW and the ECU supplier developing the BSW, under a development division system. In this case, when testing the software before it is shipped from the supplier to the vehicle manufacturer, the vehicle manufacturer does not provide the supplier with ASW, but the supplier must test the BSW before the ASW is completed, and the supplier must prepare its own ASW in order to test the BSW.

[0003] BSW testing is generally performed in the order of unit testing, integration testing, and integration testing, with the scope of the testing changing from the standpoint of checking conditional branching in the software and whether there are any problems with the transfer of data using the software interface functions used to transfer data between the ASW and BSW.

[0004] In each test, the return values ​​and variables of functions included in the software are treated as test parameters, and the test procedures and conditions for checking these test parameters are divided into test items and defined as test specifications. Also, the test parameters that must be checked vary depending on the test specifications.

[0005] Software to be embedded in an ECU is tested using a test device that can generate arbitrary input signals to the ECU, such as a hardware in the loop simulator (HILS), and an ECU incorporating the software to be tested. The ECU receives a signal from the test device, and the software incorporated in the ECU calculates test parameters in response to the input signal and verifies whether the test parameters match predetermined expected values.

[0006] Prior art in this technical field is Patent Document 1 (JP Patent Publication 2006-64411 A). Patent Document 1 proposes an internal combustion engine control unit inspection system that links an HILS and an ECU in a control unit device that controls an internal combustion engine, inputs signals to the ECU similar to those during actual internal combustion engine operation, and also calculates parameters related to internal combustion engine operation in the HILS, and automatically determines whether the parameters in the HILS and the ECU are consistent. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] JP 2006-64411 A Summary of the Invention [Problem to be solved by the invention]

[0008] Software embedded in an ECU has many parameters, and it is very time-consuming to select test parameters to be used for judging the results of a specific test, record the transition of the parameters, and judge whether the transition of the parameters is as expected.In addition, if an erroneous operation occurs because the test parameters do not transition as expected, it is necessary to find the software defect by investigating the timing of the erroneous operation during the test and identifying the cause of the erroneous operation.

[0009] The present disclosure provides a test system that assists in switching test parameters and error analysis of software under test, and enables efficient testing operations. Other objects and novel features will become apparent from the description of this specification and the accompanying drawings. [Means for solving the problem]

[0010] A brief summary of representative aspects of this disclosure is as follows. A test system according to one embodiment is a test system that tests software to be installed in a vehicle electronic control device as test target software, the test system comprising: a test device for outputting a signal to the vehicle electronic control device; a simulation test software for switching acquisition of test parameters of the test target software and determining test results during test execution of the test target software; an operation log recording unit for recording the test parameters and the test results determined by the simulation test software; a result display device that displays a result of the operation log recording unit, The simulation test software automatically switches between acquiring the test parameters necessary for determining the test results and determines the test results. Effect of the Invention

[0011] According to the test system of the embodiment, it is possible to assist in switching the acquisition of test parameters for the software under test and in error analysis, thereby reducing the amount of work involved in acquiring test parameters used to determine the results of a test and identifying the timing at which results outside the expected values ​​were obtained from the acquired test parameters, and enabling efficient testing. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a test system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of the simulation test software in FIG. [Diagram 3] 3 is a diagram showing a schematic flowchart of an engine rotation state determination unit in FIG. 2. [Figure 4] 3 is a schematic flowchart of a test parameter switching unit and a result determination unit in FIG. 2. [Diagram 5] FIG. 11 is a schematic flowchart of a result determination unit according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, the embodiments and examples will be described with reference to the drawings. However, in the following description, the same components are given the same reference numerals and repeated description may be omitted. Note that the drawings may be shown more diagrammatically than the actual embodiment in order to make the description clearer, but they are merely examples and do not limit the interpretation of the present invention.

[0014] (Embodiment) The present disclosure relates to a test system (10) for embedded software of a vehicle electronic control unit (ECU) that is composed of ASW (Application Software) and BSW (Basic Software). In the test system (10), during a BSW test, the simulation test software consisting of the ASW automatically switches the acquisition of test parameters according to the operating state of a control target controlled by the ECU during test execution, and further determines whether the test parameters are within the range of expected values, clarifies the timing when the test parameters are outside the range of expected values, and outputs the result to the outside of the ECU to assist in error analysis.

[0015] The configuration of the test system (10) of the present disclosure includes a test device (100) that transmits a signal to an ECU, and an ECU (200) that includes a BSW, which is software to be tested (220), and a simulation test software (210) that assists in the execution of a software test. The test system (10) further includes an operation log recording unit (300) that records test parameters of the BSW and test judgment results by the simulation test software (210) during test execution, and a result display device (400) that displays the test parameters and the test judgment results.

[0016] When the control target of the ECU (200) is, for example, a vehicle engine, the test device (100) outputs a signal required for calculating the engine speed to the ECU (200).

[0017] The simulation test software (210) includes an operation counter (OC) for determining the rotation state of the engine during the test, and a process for switching the test parameters of the BSW acquired according to the counter value of the operation counter (OC). The simulation test software (210) further includes recorded data of test parameters used to determine the test results of the BSW, and test result determination data used to determine the test results of the BSW from the recorded data of the test parameters and to specify the timing at which the determination result is determined to be outside the range of expected values.

[0018] The operation log recording unit (300) records the BSW test results output from the simulation test software (210) during test execution. The result display device (400) refers to the test parameters and test result judgment data acquired and stored by the operation log recording unit (300) and indicates the timing of an error occurrence and the test parameters that caused the error.

[0019] According to the present disclosure, a simulation test software (210) is prepared to assist in the execution of a test of software (220) to be incorporated in a vehicle electronic control device (200). By using the simulation test software (210), the amount of work required to acquire test parameters used to determine the results of the test and to identify the timing at which a result outside the expected value was acquired for the acquired test parameters can be reduced, and the test work can be performed efficiently.

[0020] Hereinafter, embodiments for carrying out the present disclosure will be described in detail with reference to the drawings. EXAMPLES

[0021] FIG. 1 is a diagram showing the configuration of a test system according to a first embodiment, for example, for testing a BSW (Basic Software) used in a vehicle electronic control device that controls a vehicle engine mounted on a vehicle as test target software.

[0022] As shown in FIG. 1, the BSW test system 10 of the first embodiment includes a test device 100, a vehicle electronic control unit (hereinafter referred to as ECU) 200, an operation log recording unit 300, and a result display device 400.

[0023] The test device 100 is a device that outputs a signal for calculating engine speed information required for testing the software component 220 under test. In other words, the test device 100 is a test device that simulates the operation of a vehicle engine, and the output value (output signal) of the test device 100 is a signal required for calculating the engine speed. The software component 220 under test corresponds to the BSW.

[0024] The ECU 200 is, for example, an ECU for controlling an engine of a vehicle, and has a simulated test software 210 that is combined with a software component 220 to be tested to realize the functions of the ECU 200 and is added to test the operation of the software component 220 to be tested. The simulated test software 210 corresponds to ASW (Application Software). The simulated test software 210 made of ASW is provided to assist in the implementation of a test of the software that is the software component 220 to be tested.

[0025] The operation log recording unit 300 is a recording device that records the judgment results of the test parameter data acquired by the simulation test software 210 during test execution.

[0026] The result display device 400 is a display device that displays the data recorded by the action log recording unit 300 , and includes a display unit 410 .

[0027] The test system 10 is applied to a software test system that is implemented in response to engine rotation transitions in an ECU for engine control of a vehicle, for example. As an example, a test device 100 that simulates the engine operation of an automobile is used, and a signal such as an engine crank angle position signal is output from the test device 100, the ECU 200 receives the signal, and a test target software component 220 in the ECU 200 performs calculations of test parameters used to determine the test results. In addition, the simulation test software 210 acquires the test parameters calculated by the test target software component 220, and determines the progress of the test from parameters such as the engine rotation speed included in the test parameters, and switches the acquisition of test parameters required to determine the test results according to the progress of the test. In addition, the simulation test software 210 also performs a test result judgment as to whether the acquired test parameters are as expected or not.

[0028] The operation log recording unit 300 records the test parameters and the test result judgment data acquired by the simulation test software 210 of the ECU 200. The operation log recording unit 300 may be provided inside the ECU 200, or may be configured by an information storage device connected to the outside of the ECU 200.

[0029] The result display device 400 includes a display unit 410 and displays the test parameters and test result judgment data stored in the operation log recording unit 300. The acquired data is visualized and output to the display unit 410 so that the tester can check the test results. In other words, the result display device 400 visualizes and outputs the test parameters of the test target software 220 selected, collected, and judged by the simulation test software 210 and the test judgment results of the test target software 220. The visualized data is visual data arranged so that the tester can easily judge the test results. For example, the test parameters are output in a two-dimensional graph in chronological order, and the test judgment results are also displayed. The display unit 410 may be an image display device or a print output device.

[0030] FIG. 2 is a diagram showing an example of the configuration of the simulation test software 210 of FIG.

[0031] The simulation test software 210 shown in FIG. 2 is software prepared for testing a test target software component 220, and is made up of an engine rotation state determination unit 211, a test parameter switching unit 212, and a result determination unit 213.

[0032] The engine rotation state determination unit 211 includes an operation counter OC for determining the progress of the test based on parameters calculated by the software component 220 under test.

[0033] The test parameter switching unit 212 switches the test parameters acquired from the software component under test 220 according to the progress of the test during execution of the test.

[0034] The result judging unit 213 has test result judgment data for judging whether or not the test parameters acquired from the software component under test 220 during test execution are as expected. The test result judgment data may be data for judging whether the test parameters are as expected values ​​as they change from moment to moment, or data for judging whether the test has passed or failed by comparing and evaluating a part or all of the acquired test parameters with the expected values.

[0035] Fig. 3 is a diagram showing a general flowchart of engine rotation state determination unit 211 in Fig. 2. Each of steps S11 to S15 shown in the flowchart in Fig. 3 will be described below.

[0036] 3 has an operation counter OC for determining the progress of a test, acquires the engine speed in S11, and determines whether the engine speed is within an expected range in S12 or S13. When the engine speed reaches the range expected for the next test progress state, the counter value of the operation counter OC is updated in S14 or S15.

[0037] This will be specifically described using an example in FIG.

[0038] In S11, engine speed information is acquired, and the result of the calculation is judged in S12 or S13. For example, if the engine speed is between 0 rpm and 100 rpm (S12, Yes), an operation counter OC is set to 1 in S14. If the engine speed is not between 0 rpm and 100 rpm (100 rpm>) (S12, No), the process proceeds to S13. In S13, if the engine speed calculated is between 100 rpm and 1000 rpm (S13, Yes), the operation counter OC is set to 2 in S15 to judge that the test has progressed. In S13, if the engine speed calculated is not between 100 rpm and 1000 rpm (1000 rpm>) (S13, No), the process proceeds to a predetermined processing step not shown.

[0039] 3 is an example, and the engine speed condition for S12 or S13 is determined in advance in the test specifications. Also, the upper limit of the operation counter OC for determining the test transition is set according to the number of test transitions in one test specification.

[0040] Fig. 4 is a diagram showing a schematic flowchart of the test parameter switching unit 212 and the result determination unit 213 in Fig. 2. Below, steps S21-S24 and S31-S36 shown in the flowchart in Fig. 4 will be described.

[0041] The test parameter switching unit 212 determines the counter value of the operation counter OC described in FIG. 3 in S21 or S22. In S21, it determines whether the counter value of the operation counter OC is 1 or not. If the counter value is 1 (S21: Yes), it proceeds to S23. If the counter value is not 1 (S21: No), it proceeds to S22. In S22, it determines whether the counter value of the operation counter OC is 2 or not. If the counter value is 2 (S22: Yes), it proceeds to S24. If the counter value is not 2 (S22: No), it proceeds to a predetermined processing step not shown.

[0042] In S23, a test parameter acquisition process 1 is performed. In S24, a test parameter acquisition process 2 is performed.

[0043] Based on the counter value of the operation counter OC, the process route is switched between test parameter acquisition process 1 in S23 and test parameter acquisition process 2 in S24. This allows the system to appropriately select test parameters based on the operation counter from a large number of test parameters, and acquire data and determine test results, thereby reducing the burden on the operator of confirmation.

[0044] The test parameter switching unit 212 in FIG. 4 is just one example. By adding a test parameter acquisition process in accordance with the counter value of the operation counter OC of the engine rotation state determination unit, it is possible to test the test target software component 220 covering multiple test transition states.

[0045] The test parameter result determination unit 213 determines whether the values ​​of the test parameters of the test target software component 220 acquired in the test parameter acquisition process 1 in S23 and the test parameter acquisition process 2 in S24 are as expected. Specifically, in S31, the difference between the latest value and the previous value of the test parameter 1 acquired in the test parameter acquisition process 1 is calculated. Then, in S33, it determines whether the difference calculated in S31 is within the range of expected values. Also, in S32, the difference between the latest value and the previous value of the test parameter 2 acquired in the test parameter acquisition process 2 is calculated. Then, in S34, it determines whether the difference calculated in S32 is within the range of expected values.

[0046] In S33 and S34, if the difference between test parameter 1 or test parameter 2 is within the expected value range (expected range) (S33: Yes, S34: Yes), the test parameter switching and result determination are completed.

[0047] In S33 and S34, if the acquired test parameters are outside the expected values, that is, if the difference in test parameter 1 or the difference in test parameter 2 is outside the expected value range (outside the expected range) (S33: No, S34: No), error process 1 such as setting an error flag in S35 or error process 2 such as setting an error flag in S36 is performed. In S31 or S32, an embodiment in which the difference between the latest value and the previous value of the test parameter is calculated has been described, but instead of this method, only the latest value of the test parameter may be output, or a specific calculation process other than calculating the difference may be applied. EXAMPLES

[0048] FIG. 5 is a flowchart illustrating an outline of the result determination unit according to the second embodiment.

[0049] The configuration of the test system for the test target software component 220 in the second embodiment is the same as the configuration of the test system 10 in the first embodiment, but the processing of the test parameter switching unit 212 and the result determination unit 213 described in Fig. 5 is different from the processing of the test parameter switching unit 212 and the result determination unit 213 described in Fig. 4. The following mainly describes the different operations.

[0050] The counter value of the operation counter OC is determined in S21 or S22 of the test parameter switching unit 212, and the selected test parameter A or test parameter B is acquired continuously, in part or in whole, in chronological order during test execution in test parameter acquisition process A (S600) or test parameter acquisition process B (S610).

[0051] Then, the result determination unit 213 calculates the maximum / minimum / average value from the accumulated data of test parameter A acquired in S700, and determines in S720 whether the maximum / minimum / average value of test parameter A falls within the expected range (expected range) defined in the test specifications. Also, the result determination unit 213 calculates the maximum / minimum / average value from the accumulated data of test parameter B acquired in S710, and determines in S730 whether the maximum / minimum / average value of test parameter B falls within the expected range (expected range) defined in the test specifications.

[0052] In S720 and S730, if the maximum value / minimum value / average value of test parameter A or test parameter B is within the expected range (S720: Yes, S730: Yes), the test parameter switching and result determination are completed.

[0053] In S720 or S730, if the maximum value / minimum value / average value of test parameter A or test parameter B is not within the expected range (S720: No, S730: No), error processing 1 such as setting an error flag in S740 or error processing 2 such as setting an error flag in S750 is performed.

[0054] Although an embodiment in which the maximum value, minimum value, and average value of the test parameters are calculated has been described in S700 or S710, instead of this method, only the average value of the test parameters may be calculated, or the evaluation test parameters may be calculated by removing singular values ​​such as noise and applying a specific filter process.

[0055] That is, when there is variation in the test parameters or when noise is superimposed on (the values ​​of) the test parameters, it is preferable to calculate the maximum, minimum and average values ​​of the test parameters as in Example 2. When there is not much variation in the test parameters or when there is not much noise superimposed on (the values ​​of) the test parameters, there is not much need to calculate the maximum, minimum and average values ​​of the test parameters, so it is preferable to adopt Example 1. In Example 1, there is no need to continuously store some or all of the test parameters in chronological order during the execution of the test, so there is an effect that a large amount of memory area inside the ECU 200 is not used, or the maximum, minimum and average values ​​of the test parameters are not calculated, so that the calculation load on the ECU 200 can be reduced. EXAMPLES

[0056] Of course, a test system 10 according to a third embodiment may be configured by combining the first embodiment and the second embodiment. That is, in the test system 10 according to the third embodiment, one or more test parameters are handled as in the first embodiment, and the maximum value, minimum value, and average value of one or more other test parameters are calculated as in the second embodiment. According to the third embodiment, the effects of the first embodiment and the second embodiment can be obtained.

[0057] Although the present disclosure has been specifically described above based on examples, it goes without saying that the present disclosure is not limited to the above-described embodiments and examples, and various modifications are possible. [Explanation of symbols]

[0058] 10: Test system 100: Test equipment 200: ECU 210:Mock Test Software 211: Engine rotation state determination unit 212: Test parameter switching unit 213: Result judgment section 220: BSW (Basic Software) 300: Operation log recording section 400: Result display device 410: Display section

Claims

1. A test system for testing software to be installed in a vehicle electronic control device as test target software, comprising: a test device for outputting a signal to the vehicle electronic control device; a simulation test software for switching acquisition of test parameters of the test target software and determining test results during test execution of the test target software; an operation log recording unit for recording the test parameters and the test results determined by the simulation test software; a result display device that displays a result of the operation log recording unit, The simulation test software automatically switches between acquiring the test parameters necessary for determining the test results and determines the test results. Test system.

2. 2. The test system of claim 1, The test device is a test device that simulates the operation of a vehicle engine, A test system, wherein the output signal of the test device is a signal required for calculating an engine rotation speed.

3. 2. The test system of claim 1, The simulation test software includes an operational counter for determining the progress of a test.

4. 4. The test system according to claim 3, The simulation test software includes a test parameter switching unit that switches acquisition of the test parameters of the software under test, A test system that switches the test parameters to be acquired depending on the counter value of the operation counter.

5. 2. The test system of claim 1, The simulation test software includes a result determination unit that determines a result of the test parameters, A test system, wherein the simulation test software calculates a difference between a previous value and a latest value of the test parameter of the software under test during execution of the test of the software under test, and uses the difference in value to determine a test result of the software under test.

6. 2. The test system of claim 1, The simulation test software includes a result determination unit that determines a result of the test parameters, A test system, wherein the simulation test software acquires maximum, minimum and average values ​​of the test parameters of the software under test during test execution of the software under test, and judges a test result of the software under test.

7. 2. The test system of claim 1, The result display device visualizes and outputs the test parameters of the software under test selected, collected and judged by the simulation test software and the test result judgment of the software under test.

Images