KR20210046390A - AUTOSAR BSW testing automation system and testing method thereof - Google Patents

Abstract

The present invention relates to an Autosar basic software (BSW) testing automation system and a method thereof. The present invention provides a system for testing BSW of Autosar, which is a standard software platform of a vehicle, comprising: a test system generator, based on information extracted from ECU design information, generating a test case module storing information on a test case and a tester module storing test execution information for testing a predetermined BSW part, which becomes a test target according to the test case; a test system receiving and storing the generated test case module, driving the test case module to transmit the test case to a target system through a vehicle network, and receiving a test result from the target system to generate a test report; and the target system receiving and storing the generated tester module, driving the tester module to test the BSW part according to the test case received from the test system and then transmitting the test result through the vehicle network. The present invention can automate the process for testing the Autosar BSW by using the ECU design information and rapidly and easily test functions and performance of the BSW in advance even though there is no implemented application software component.

Description

AUTOSA basic software testing automation system and its method TECHNICAL FIELD [AUTOSAR BSW testing automation system and testing method thereof]

The present invention relates to an Autosa basic software testing automation system and a method thereof, and more particularly, to an Autosa basic software testing automation system and a method for testing Autosa Basic Software (BSW).

In recent years, software has been implemented increasingly complex as the number of installed functions increases, and it takes a lot of time and cost to design a test execution environment and test case accordingly. In addition, complicatedly implemented software can cause many errors in the test phase.

In recent years, embedded software technology for vehicles is evolving in the direction of securing high quality with minimum cost of system software in a short period of time in order to respond to the needs of the automotive industry. For this, the first part that must be determined is to establish a system standard, and it is necessary to secure the independence of hardware and software so that the same software can be used in different systems.

System standards such as AUTOSAR (AUTomotive Open System ARchitecture) enable hardware independence and standardization of software components.

Auto Corp. provides a software configuration method that allows vehicle software to be independently supplied to hardware structures based on ECUs and networks, so that it can be applied to various vehicle platforms.

Otto's structure consists of Basic Software (BSW), Otto's Runtime Environment (RTE), and the application layer. The basic software corresponds to the'basic software' of Auto Corporation, and the application layer is the software of the actual automotive electric field, which corresponds to the'application software'.

Each automobile and parts maker develops software (application software) for automotive electronics (eg, control programs for brakes and air conditioning systems, etc.) according to the standard specifications of Auto Corporation. Conventionally, a method for testing the conformity of automotive electronic software to check whether such application software has been developed in accordance with the standards proposed by Auto Corporation has been disclosed.

However, this is to test whether the application software, which is an automotive electronic software, has been developed according to the actual standards of Auto Corporation, and tests for the basic software (BSW) and real-time environment (RTE), which are lower levels of these application software, are not included. .

In general, the design of Auto's Basic Software (BSW) is very complex, and the functions and performances that need to be tested are very diverse. Therefore, there is a need for a technology capable of effectively testing the basic software (BSW) before being integrated with the actual application software.

The technology behind the present invention is disclosed in Korean Patent No. 1134735 (announced on April 13, 2012).

An object of the present invention is to provide an Autosa basic software testing automation system and method capable of automatically testing Autosa's basic software (BSW).

The present invention is a system for testing a basic software (BSW) of AUTOSAR, a standard software platform of a vehicle, based on information extracted from ECU design information, a test case module storing information on a test case And a test system generator for generating test modules each storing test execution information for testing a predetermined BSW part to be tested according to the test case, and receiving the generated test case module, and driving the test case module. Then, a test system for transmitting the test case to a target system through a vehicle network and generating a test report by receiving a test result from the target system, and the generated tester module are stored, and the tester module is driven, and the test It provides an Autosa basic software testing automation system including a target system that tests the BSW part according to the test case received from the system and transmits the test result through the vehicle network.

In addition, the test system generator includes an information extractor for extracting information necessary for a test from the ECU design information, and the test case for a function test for the BSW target element and a performance test for the corresponding function based on the extracted information. The test case module is constructed by generating the information of-Here, the test case information includes a case code for each test case, a step code for each test step in the corresponding test case, and a code for generating a test result/evaluation/report. A test case module generator that generates a test case module generator, and an execution code for respectively executing a function and performance test of a corresponding BSW part corresponding to the information of the generated test case, and constructs the test case module corresponding to the test case module. It may include a module generator.

In addition, the test system is operated to test the BSW part, transmits a test command including information of the test case to the target system or input/output control module, and then receives a test result from the target system or input/output control module. And, the test case module that generates a test report by comparing the received test result with the expected result, and when the test command is received from the test case module, the input of the hardware required for the execution of the test case is controlled and It may include an input/output control module that measures the correspondingly derived output of the hardware and provides it as the test result.

In addition, the target system, when a test command including the information of the test case is input, converts the target system to a test mode, transmits the test command to a BSW tester, and receives a test result from the BSW test. A test manager that transmits to a test system, and a BSW tester that performs testing on a corresponding BSW part according to a test case included in the test command, and transmits a test result to the test manager when the testing is finished. have.

In addition, the test manager, when the test command is input, transmits a BSW test control command for starting the testing and transmits the test command to the BSW tester, the test control runable unit, when the test control command is input, the A BSW service control runable unit that converts the target system to a test mode, and a test result runable unit that transmits the test result to the test system when a test result is received from the BSW tester.

In addition, the BSW tester initializes a memory when the test command is input from the test manager, and a BSW tester control runable unit that executes the BSW tester runable unit based on a test case included in the test command, and a test It is connected to the target BSW part and performs testing for at least one function of the corresponding BSW part according to the command of the BSW tester control runable unit, and when testing is completed, the test result is written to the memory. And at least one BSW tester runable unit to perform testing, and a BSW tester result runable unit that reads a test result from the memory and transmits it to the test manager when testing is completed.

In addition, the BSW tester includes N BSW tester runable units corresponding to one BSW part, and the N (N is 2 or more positive) BSW tester runable units are different within the BSW part. It is connected one-to-one with N BSW modules in charge of detailed functions, so that the detailed functions can be individually tested.

In addition, the BSW may include a plurality of BSW parts, and testing may be sequentially performed for each BSW part.

In addition, the BSW includes a plurality of BSW parts, and the plurality of BSW parts include a controller area network (CAN), an operating system (OS), an input/output interface (I/O interface), and a BSW corresponding to a memory. May contain parts.

According to the present invention, it is possible to automate the test process of Auto's basic software (BSW) using ECU design information, and even if there is no implemented application software component, functions and performance of the basic software can be tested quickly and easily in advance. .

In addition, the test of the BSW is repeated every time the ECU is developed and the design is changed. According to the present invention, it is possible to improve the reliability of the software and shorten the development period by automating such a BSW test.

In addition, it is possible to test the BSW of Auto Corporation in the state that only the BSW is implemented before the application software is integrated, so it provides the advantage of being able to quickly and easily verify the function and performance of the BSW.

1 is a diagram showing the architecture of AUTOSAR, a standard software platform for vehicles.
2 is a diagram showing the configuration of an Autosa basic software testing automation system according to an embodiment of the present invention.
3 is a diagram showing the configuration of the test system generator of FIG. 2.
4 is a diagram illustrating an example of generating a test case module and a tester module in the test system generator of FIG. 2.
5 is a diagram showing the configuration of the test case module of FIG. 2 in detail.
6 is a diagram showing the configuration of the target system of FIG. 2 in detail.
7 is a diagram showing the configuration of the test manager of FIG. 6 in more detail.
8 is a diagram showing the configuration of the BSW tester of FIG. 6 in more detail.

Then, with reference to the accompanying drawings, embodiments of the present invention will be described in detail so that those of ordinary skill in the art can easily implement the present invention.

The present invention proposes a technology for automating the testing of AUTOSAR's Basic Software (BSW) using ECU design information as an Autosa basic software testing automation system and its method. Prior to the detailed description, a brief description of Otto's architecture is as follows.

1 is a diagram showing the architecture of AUTOSAR, a standard software platform for vehicles.

As shown in Fig. 1, Autosa has three main layers (layers), in order from bottom to top, respectively, Basic Software (BSW) (10), and Autosa Real-Time Environment (RTE; Runtime Environment) (20). , And an application software layer (Application SWcs) (30).

The basic software layer 10 is a layer on which'basic software' for the Autosa platform is mounted, and the application layer 30 is'application software', and software (e.g., brakes, brakes, etc.) It is a layer in which a control program such as an air conditioner) is mounted.

An embodiment of the present invention provides an Autosa basic software testing automation system capable of automating function and performance testing of various basic software designed in the basic software layer 10 of the Autosa platform.

In this embodiment of the present invention, before the software (application software) of the actual vehicle electric field is integrated into the application software layer 30 of Auto Corporation, the designed functions and performance parts for the basic software (BSW) layer, which are only basic software parts, are used. Makes it easy and quick to test. According to this, even if there is no actually implemented application software component, it is possible to efficiently test the function and performance of the basic software.

Referring to FIG. 1, the basic software layer 10 inside the Autosa platform includes a variety of controller area network (CAN) communication, hardware input/output (I/0), operating system (OS), memory, etc. A set of basic software (BSW) is included.

As such, the basic software (BSW) of Auto Corporation basically includes a plurality of BSW parts, and as shown, a plurality of BSW parts corresponding to each of CAN, operating system (OS), input/output interface (I/O interface), memory, etc. Includes.

Here, of course, the BSW part again includes a plurality of detailed BSW functions. For example, the basic software designed for the first BSW part, which is a part related to CAN, is again a detailed software element (detailed BSW module) (e.g., CAN TX (transmission related), CAN RX (reception related), TIMING (timing), etc. Related software).

As such, the Autosa standard corresponds to a vehicle software standard platform that enables the design and implementation of basic software (BSW) and application software (Applicaion SW) independently, and in the Autosa standard, BSW is modularized into functional units and services between modules And interfaces are standardized.

Here, when the application software uses the functions and services of the basic software (BSW), a standardized interface is used.

In addition, the design information for each BSW module of Auto Corporation is stored as a standardized XML file. In other words, design information of ECU software developed based on the Autosa standard is stored in XML format.

The following embodiment of the present invention provides a system capable of automatically generating test cases and tester modules by extracting detailed design information of basic software (BSW) from an XML file, and automatically executing testing of basic software based on the generated modules. Suggest.

Hereinafter, a system for automated testing of Autosa basic software according to an embodiment of the present invention will be described in more detail.

2 is a diagram showing the configuration of an Autosa basic software testing automation system according to an embodiment of the present invention.

As shown in FIG. 2, the Autosa basic software testing automation system according to an embodiment of the present invention includes a test system generator 100, a test system 200, and a target system 300.

Based on the information extracted from the ECU design information, the test system generator 100 includes a test case module storing information on a test case and a predetermined BSW part to be tested according to the test case (for example, CAN communication). Each of the tester modules storing test execution information for testing the BSW part related to (BSW part) is created.

Here, the predetermined BSW part is a BSW part that becomes a test target, and may include at least one of the various BSW parts described above. The test case module generated corresponding to the predetermined BSW part is provided to the test system 200, and the generated tester module is provided to the target system 300.

3 is a diagram showing the configuration of the test system generator of FIG. 2.

As shown in FIG. 3, the test system generator 100 includes an information extractor 110, a test case module generator 120, and a test module generator 130.

Referring to FIG. 3, the test system generator 100 extracts information necessary for a test from ECU design information (AUTOSAR XML file).

ECU software design information included in AUTOSAR may be derived in the form of an AUTOSAR XML file as shown in FIG. 1 above. The test system generator 100 extracts information necessary for testing from this XML file.

The test case module generator 120 generates test case information for a function test for a corresponding BSW part and a performance test for a corresponding function based on the extracted information, and builds a test case module based on this. The built test case module is delivered to the test system 200.

Here, the information of the test case includes a case code assigned for each test case, a step code for each test step in the corresponding test case, and a code for generating a test result/evaluation/report.

The tester module generator 130 generates an execution code for executing each function and performance test of a corresponding BSW part corresponding to the generated test case information, and constructs the tester module corresponding to the test case module. The built tester module is delivered to the target system 300.

4 is a diagram illustrating an example of generating a test case module and a tester module in the test system generator of FIG. 2.

4 is an example for testing a BSW part related to CAN communication. From FIG. 4, an example of extracting information necessary for CAN communication from ECU design information, and generating a test case module and a tester module, respectively, can be seen.

Specifically, (a) of FIG. 4 illustrates ECU software designed by the Otto company design tool, and shows a part of the design contents of CAN communication among them. Software design is made through detailed settings such as CAN message name and CAN ID.

FIG. 4(b) shows that FIG. 4(a) is stored in XML format and corresponds to an AUTOSAR XML file. In this way, ECU software design information set in the Autosa design tool is stored and managed as XML data.

4(c) shows a state in which the information extractor 110 extracts information necessary for CAN communication from the AUTOSAR XML file of FIG. 4(b).

4(d) shows a state in which the test case module generator 120 generates a test case module using the extracted information of FIG. 4(c). The test case module generator 120 generates test cases (Testcase 1, Testcase 2, …) for CAN communication functions and performance tests, and test step codes within the test cases, and codes for evaluating test results and generating reports. Create

4(e) shows a state in which the tester module generator 130 generates a tester module using the extraction information of FIG. 4(c) and the test case of FIG. 4(d). When the test case and the test input defined in the test step are received (input) to the test module, the test module generator 130 generates a code for executing a CAN communication function and a performance test corresponding to the test case.

In this way, the test system generator 100 generates a test case module and a tester module, respectively, using an XML file. Of course, each of these modules is implemented in software.

Referring back to FIG. 2, the test system 200 receives, stores, and mounts the test case module generated from the test system generator 100. The test system 200 drives (controls) the test case module 210 to transmit the test case to the target system 300 through the vehicle network CAN, and then receives the test result from the target system 300. To generate a test report.

The target system 300 receives, stores, and mounts the tester module generated from the test system generator 100. The tester module includes a test manager 310 and a BSW tester 320.

The target system 300 drives (controls) the tester module, tests the corresponding BSW part according to the test case received from the test system 200, and transmits the test result again through the vehicle network.

The hatched regions of FIG. 2 correspond to the BSW layer 10 of FIG. 1. That is, the shaded area corresponds to the BSW (Basic Software) part, and the Tested Module located in the BSW corresponds to the BSW part to be tested soon.

In this way, the target system 300 targets the BSW part (for example, a BSW part related to CAN communication) to be tested, executes a test corresponding to the test case for the BSW part, and returns the test result to the test system 200 ) To give feedback.

5 is a diagram showing the configuration of the test case module of FIG. 2 in detail.

2 and 5, the test system 200 includes a test case module 210 and a hardware input/output control module 220.

The test case module 210 is operated to test a target BSW part (Tested Module), and specifically, after transmitting a test command including information of the test case to the target system 300 or the input/output control module 220 , The test result is received from the target system 300 or the input/output control module 220, and the received test result is compared with the expected result to generate a test report.

That is, the test case module 210 transmits a test input to the target system 300 or the input/output control module 220 and receives a test execution result from the target system 300 or the input/output control module 220. Then, by comparing the expected result and the test execution result, the test is evaluated and a test report is generated.

When receiving a test command from the test case module 210, the input/output control module 220 controls an input of hardware required for execution of the test case and measures the output of the hardware derived in response to the input to measure the test case module 210. ) Can be provided as a test result. The input/output control module 220 tests data that does not pass through the vehicle network, such as input/output of hardware, and is used to exchange and test input/output of hardware that does not pass through the vehicle network CAN.

The input/output control module 220 controls ECU hardware inputs required for test execution and measures ECU outputs. Input control includes DIO and ADC, and hardware output measurement includes PWM and DIO.

6 is a diagram showing the configuration of the target system of FIG. 2 in detail.

As shown in FIG. 6, the target system 300 includes a tester module, and the RTE and BSW to be tested. The hatched portions in FIG. 6 correspond to the hatched portions in FIG. 2.

The tester module includes a test manager 310 and a BSW tester 320. The BSW tester 320 may include a CAN tester, a hardware I/O tester, a memory tester, an RTE tester, an OS tester, a diagnostic tester, a system service tester, and the like.

When a test command including test case information is input from the test case module 210, the test manager 310 internally switches the target system 300 to the test mode, and transfers the input test command to the BSW tester 320. Deliver. Also, when the test manager 310 receives a test result from the BSW test, it transmits it to the test case module 210.

When a test command is input from the test manager 310, the BSW tester 320 performs testing on a corresponding BSW part (A) (Tested Module) according to a test case included in the input test command. And when the task is finished, the test result is transmitted to the test manager 310.

The operation of the tester module will be described with reference to FIG. 6 as follows. In Fig. 6, the order of each operation (No. 1 to No. 6) and a further explanation related thereto are disclosed.

First, the test manager 310 receives a test input from the test system 200 (1). When the test input is received, execution of the BSW testing task starts. In addition, when a test input is received, the ECU enters the test mode (2). At this time, the state of the BSW is controlled according to the conditions of the test case and the test stage. And when the test manager 310 transmits a test input to the BSW tester 320, the BSW tester 320 starts execution (3).

The BSW tester 320 performs BSW testing according to the test case and the test step (4). When the BSW testing is finished, the BSW tester 320 transmits the result to the test manager 310 (5). Then, the test manager 310 transmits the BSW test result to the test system 200 (6).

Next, detailed configurations of the test manager 310 and the BSW tester 320 will be described in detail.

7 is a diagram showing the configuration of the test manager of FIG. 6 in more detail.

As shown in FIG. 7, the test manager 310 includes a test control runable unit 311, a BSW service control runable unit 312, and a test result runable unit 313.

When a test command is input, the test control runable unit 311 transmits a BSW test control command for starting testing and transmits the test command to the BSW tester 320.

When a test control command is input, the BSW service control runable unit 312 waits for the target system 300 in the test mode.

Test result The runable unit 313 transmits the test result to the test system 200 when the test result is received from the BSW tester 320. Each of these runable units may be executed or activated according to input information to perform a related operation.

The operation of the test manager 310 will be described with reference to FIG. 7 as follows. In FIG. 7, the order of each operation (No. 1 to No. 7) and a further explanation related thereto are disclosed.

First, when a test input is received to the test control runable unit 311, the BSW test task is started, and execution of the test control runable is started (1).

The test control runable unit 311 executes the BSW service control runable, and sends a command for controlling the BSW (2). The BSW service control runable unit 312 enters the ECU into the test mode (3). And it controls the state of the BSW according to the test case and test stage.

The test control runable unit 311 transmits commands and inputs for BSW testing (4). Then, the BSW tester 320 executes the BSW testing, and when the BSW testing is completed, the test result receives the BSW test result from the runable unit 313 (6). The test result runable unit 313 transmits the test result to the test system 200 (7).

8 is a diagram showing the configuration of the BSW tester of FIG. 6 in more detail.

As shown in FIG. 8, the BSW tester 320 includes a BSW tester control runable unit 322, a BSW tester runable unit 323, a BSW test result runable unit 321, and a memory 324.

The BSW tester control runable unit 322 initializes the memory 324 when a test command is input from the test manager 310, and executes the BSW tester runable unit 323 based on the test case included in the test command. .

The BSW tester runable unit 323 is connected to the BSW part (A; Tested Module) to be tested, and the corresponding BSW part (ex, BSW part related to CAN communication) according to the command of the BSW tester control runable unit 322 At least one is provided in the BSW tester 320 to perform testing for each of the at least one function.

If there are three testing target functions corresponding to the corresponding BSW part, the BSW tester runable unit 323 is composed of three as shown in FIG. 8. For example, corresponding to the BSW part (A) related to CAN, the BSW tester runable unit 323 is individually provided for each of the TX function, RX function, and timing function.

As such, the BSW tester 320 includes N BSW tester runable units 323 corresponding to one BSW part (A). At this time, N (N is 2 or more government) BSW tester runable units 323, N BSW modules (A-1, A-2, A-) responsible for different detailed functions within the BSW part (A). It is connected one-to-one with 3), and each detailed function of the BSW module (A-1, A-2, A-3) can be individually tested. Here, the BSW module (A-1, A-2, A-3) is also a software element that implements the detailed functions of the corresponding BSW part (A) in the BSW layer of Auto Corporation.

When the testing is completed, the BSW tester runable unit 323 writes the test result to the memory 324. That is, the test result is stored in the memory. At this time, the memory 324 may also be provided to correspond to the number corresponding to the BSW tester runable unit 323 in one correspondence.

In addition, when testing is completed, the BSW test result runable unit 321 reads the test result from the memory 324 and transmits it to the test manager 310.

Of course, according to the above-described configuration, the testing automation system of the present invention can sequentially perform testing for each BSW part. That is, by sequentially performing the above-described testing operation for each BSW part, detailed functions of all BSW parts may be tested.

The operation of the BSW tester 320 will be described with reference to FIG. 8 as follows. In Fig. 8, the order of each operation (No. 1 to No. 7) and a further explanation related thereto are disclosed.

First, when an input for BSW tester testing is received in the BSW tester control runable unit 322, the BSW tester task is started and the BSW tester control runable is executed (1).

The BSW tester control runable unit 322 initializes the memory 324 in which the test result is stored (2). The BSW tester control runable unit 322 executes the BSW tester runable units 323 according to the test case and the test step (3).

Then, the BSW tester runable unit 323 performs BSW testing (4). When the test is completed, the BSW tester runable unit 323 stores the test result in the memory 324 (5). When the BSW testing is completed, the BSW test result runable is executed, and the BSW tester result runable unit 321 reads the test result from the memory 324 (6) and sends it to the test manager 310 (7).

According to the present invention as described above, it is possible to automate the testing process of Auto's basic software (BSW) using ECU design information, and quickly and easily test functions and performance of basic software in advance even if there is no implemented application software component. can do.

In addition, the present invention can automate a BSW module test related to hardware input/output by using a hardware input/output control module.

In addition, the BSW test is basically repeated every time ECU development and design change. According to the present invention, the reliability of the software can be improved and the development period can be shortened by automating the BSW test.

Moreover, before the application software (automobile electronic software) is integrated into the Autosa platform, it is possible to test the BSW in the state that only the BSW is implemented, thus providing the advantage of being able to quickly and easily verify the function and performance of the BSW.

The present invention has been described with reference to the embodiments shown in the drawings, but these are merely exemplary, and those of ordinary skill in the art will understand that various modifications and equivalent other embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the appended claims.

100: test system generator 110: information extractor
120: test case module generator 130: tester module generator
200: test system 210: test case module
220: input/output control module 300: target system
310: Test Manager 311: Test Control Runable Unit
312: BSW service control runable unit 313: test result runable unit
320: BSW tester 321: BSW tester result runable unit
322: BSW tester control runable unit 323: BSW tester runable unit
324: memory

Claims (9)

In the system for testing the basic software (BSW) of AUTOSAR, which is a standard software platform for vehicles,
Based on the information extracted from the ECU design information, a test case module storing information on the test case and a tester module storing test execution information for testing a predetermined BSW part to be tested according to the test case are respectively generated. Test system generator;
A test system for storing the generated test case module, driving the test case module to transmit the test case to a target system through a vehicle network, and receiving a test result from the target system to generate a test report; And
Autosa including a target system that stores the generated tester module, drives the tester module, tests the BSW part according to the test case received from the test system, and transmits the test result through the vehicle network. Basic software testing automation system. The method according to claim 1,
The test system generator,
An information extractor for extracting information necessary for a test from the ECU design information;
Based on the extracted information, information on the test case for a function test for a corresponding BSW part and a performance test for a corresponding function-Here, the information of the test case is a case code for each test case, and for each test step within the corresponding test case. A test case module generator for constructing the test case module by generating a step code and a code for generating a test result/evaluation/report; And
Autosa including a tester module generator for constructing the tester module corresponding to the test case module by generating execution code for each of the function and performance tests of the corresponding BSW part corresponding to the generated test case information Basic software testing automation system. The method according to claim 1,
The test system,
Operated to test the BSW part, transmits a test command including information of the test case to the target system or input/output control module, receives a test result from the target system or input/output control module, and receives the received test result. A test case module for generating a test report by comparing with the expected result; And
In the case of receiving the test command from the test case module, including an input/output control module that controls an input of hardware required for execution of the test case, measures an output of the hardware derived in response to the input, and provides the test result as the test result. Autosa Basic Software Testing Automation System. The method according to claim 1,
The target system,
When a test command including the information of the test case is input, the target system is switched to a test mode, the test command is transmitted to a BSW tester, and a test manager receives a test result from the BSW test and transmits it to the test system. ; And
Autosa basic software testing automation system comprising a BSW tester that performs testing on a corresponding BSW part according to a test case included in the test command, and transmits a test result to the test manager when the testing is finished. The method of claim 4,
The test manager,
A test control runable unit that transmits a BSW test control command for starting the testing when the test command is input and transmits the test command to the BSW tester;
A BSW service control runable unit for converting the target system to a test mode when the test control command is input; And
Autosa basic software testing automation system comprising a test result runable unit for transmitting the test result to the test system when a test result is received from the BSW tester. The method of claim 4,
The BSW tester,
A BSW tester control runable unit that initializes a memory when the test command is input from the test manager and executes a BSW tester runable unit based on a test case included in the test command;
It is connected to the BSW part to be tested, and performs testing for at least one function of the corresponding BSW part according to the command of the BSW tester control runable unit, and when testing is completed, the test result is written to the memory. ) At least one BSW tester runable unit; And
Autosa basic software testing automation system comprising a BSW tester result runable unit that reads a test result from the memory and transmits it to the test manager when testing is completed. The method of claim 6,
The BSW tester,
Includes N BSW tester runable units corresponding to one BSW part,
The N (N is 2 or more positive) BSW tester runable units,
Autosa basic software testing automation system that is connected one-to-one with N BSW modules in charge of different detailed functions within the BSW part to individually test the detailed functions. The method of claim 7,
The BSW includes a plurality of BSW parts,
Autosa basic software testing automation system that performs testing sequentially for each BSW part. The method according to claim 1,
The BSW includes a plurality of BSW parts,
The plurality of BSW parts,
Autosa basic software testing automation system including CAN (Controller Area Network), operating system (OS), input/output interface (I/O interface), and BSW parts respectively corresponding to memory.

Images