Multi-language text testing method and device for vehicle-mounted application, testing platform and medium

Abstract

The invention relates to the technical field of testing, in particular to a multi-language text testing method and device for a vehicle-mounted application, a testing platform and a medium, and the method comprises the steps that the vehicle-mounted application to be tested is acquired, and the vehicle-mounted application to be tested has multiple language versions; calling a webpage editing tool to carry out operation recording and interface element collection on a plurality of pages of the to-be-tested vehicle-mounted application under each language version, and generating an operation script containing a page traversal path and language switching logic; and running the operation script to extract a plurality of pieces of in-vehicle text content of the to-be-tested in-vehicle application in each language version, comparing the plurality of pieces of in-vehicle text content with pre-stored standard text content, and generating a test report of the to-be-tested in-vehicle application in each language version. Therefore, the problems of long test period, low manual checking efficiency, low test accuracy and the like when the vehicle-mounted application is subjected to multi-language localization test for the overseas market in the related technology are solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of testing, in particular to a multi-language text testing method and device for vehicle applications, a testing platform and a medium. BACKGROUND

[0002] In recent years, more and more car companies have launched vehicle models equipped with intelligent cockpit systems in overseas markets such as Europe and Southeast Asia. In order to meet the usage habits and regulatory requirements of users in different countries and regions, vehicle applications (such as navigation, entertainment, voice assistants, vehicle settings, etc.) need to be developed for multi-language localization.

[0003] In the related art, the testing of multi-language text for vehicle applications mainly relies on manual methods. In actual execution, the tester needs to switch languages page by page on the real vehicle or the vehicle device and manually check whether the text displayed on the screen is consistent with the standard text provided by the translation department. This method has obvious defects: on the one hand, the same application package needs to be compatible with multiple languages, resulting in more manpower for language text checking and longer testing period, which is difficult to match the rhythm of rapid iteration and delivery of overseas projects; on the other hand, the tester often does not have professional language skills in all target languages, which can easily lead to misjudgment or missed detection, seriously affecting the accuracy and reliability of the test results. SUMMARY

[0004] The present application provides a multi-language text testing method, device, testing platform and medium for vehicle applications to solve the problems of long testing period, low efficiency of manual checking and low testing accuracy when testing vehicle applications for multi-language localization in overseas markets in the related art.

[0005] The first aspect embodiment of the present application provides a multi-language text testing method for vehicle applications. The method is applied to a testing platform, the testing platform is integrated with a web editing tool, the testing platform and a vehicle device are in communication connection, and the method comprises the following steps: obtaining a vehicle application to be tested, wherein the vehicle application to be tested has multiple language versions; calling the web editing tool to record operations and collect interface elements on multiple pages of the vehicle application to be tested in each language version, and generating an operation script containing page traversal paths and language switching logic; running the operation script to extract multiple pieces of vehicle text content of the vehicle application to be tested in each language version, comparing the multiple pieces of vehicle text content with pre-stored standard text content, and generating a test report of the vehicle application to be tested in each language version.

[0006] Optionally, the operation script is run to extract the plurality of car machine text contents of the vehicle-mounted application to be tested in each language version, comprising: running the operation script to obtain layout information of each page; extracting text fields in the layout information of each page; and performing deduplication, filtering of non-business text, and coding standardization processing on the text fields to obtain the car machine text contents.

[0007] Optionally, the plurality of car machine text contents and the pre-stored standard text contents are compared to generate a test report of the vehicle-mounted application to be tested in each language version, comprising: sorting the plurality of car machine text contents in page traversal order; performing complete matching query on each car machine text content after sorting with all entries in the standard text contents; if there is a matching entry in the standard text contents, marking the corresponding car machine text content as a first type, otherwise marking as a second type; and generating the test report of the vehicle-mounted application to be tested in each language version according to the marking result.

[0008] Optionally, the web page editing tool is a weditor tool, and at least one of the following functions is provided: auxiliary script writing, element positioning, and code debugging.

[0009] Optionally, before obtaining the vehicle-mounted application to be tested, the method further comprises: listening to a connection state between the test platform and the car machine; and if the connection state is a failure state, triggering an automatic reconnection mechanism.

[0010] Optionally, after generating the test report of the vehicle-mounted application to be tested in each language version, the method further comprises: visually displaying the test report on a graphical user interface of the test platform, wherein the test report is in a table format file.

[0011] The second aspect embodiment of the application provides a multi-language text testing device for a vehicle-mounted application, which is applied to a test platform, the test platform is integrated with a web page editing tool, the test platform and a car machine are in communication connection, and the device comprises: an obtaining module, configured to obtain a vehicle-mounted application to be tested, wherein the vehicle-mounted application to be tested has a plurality of language versions; a processing module, configured to call the web page editing tool to perform operation recording and interface element collection on a plurality of pages of the vehicle-mounted application to be tested in each language version, and generate an operation script containing page traversal paths and language switching logic; and a testing module, configured to run the operation script to extract a plurality of car machine text contents of the vehicle-mounted application to be tested in each language version, compare the plurality of car machine text contents with pre-stored standard text contents, and generate a test report of the vehicle-mounted application to be tested in each language version.

[0012] Optionally, the processing module is further configured to: run the operation script to obtain layout information of each page; extract text fields in the layout information of each page; and perform deduplication, filtering of non-business text, and coding standardization processing on the text fields to obtain the car machine text contents.

[0013] Optionally, the test module is further configured to sort the plurality of pieces of vehicle machine text content in a page traversal order; perform a full match query on each piece of sorted vehicle machine text content and all entries in the standard text content; if there is a matching entry in the standard text content, mark the corresponding vehicle machine text content as the first type, otherwise mark it as the second type; and generate a test report of the vehicle application in each language version according to the marking result.

[0014] Optionally, the web page editing tool is a weditor tool, and has at least one function of assisting in writing a script, locating an element, and debugging code.

[0015] Optionally, the multilingual text testing device of the vehicle application further includes a listening module configured to listen to a connection state between the test platform and the vehicle machine before obtaining the vehicle application to be tested; and if the connection state is a failure state, trigger an automatic reconnection mechanism.

[0016] Optionally, the multilingual text testing device of the vehicle application further includes a display module configured to visually display the test report on a graphical user interface of the test platform after generating the test report of the vehicle application in each language version to be tested, wherein the test report is a table format file.

[0017] The third aspect of the present application provides a test platform, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the program to implement the multilingual text testing method of the vehicle application as described in the above embodiments.

[0018] The fourth aspect of the present application provides a computer readable storage medium, which stores a computer program or instructions, and the computer program or instructions are executed to implement the multilingual text testing method of the vehicle application as described in the above embodiments.

[0019] The fifth aspect of the present application provides a computer program product, including a computer program or instructions, and the computer program or instructions are executed to implement the multilingual text testing method of the vehicle application as described in the above embodiments.

[0020] Therefore, the present application has at least the following beneficial effects: The embodiment of the application automatically generates an operation script containing a page traversal path and language switching logic by calling a webpage editing tool to operate and record the interface of the to-be-tested vehicle-mounted application in multiple language versions, and automatically extracts the vehicle machine text content in each language version by executing the operation script, and performs accurate comparison with the pre-stored standard text, and automatically generates a test report, effectively shortening the manual testing time, and significantly improving the testing efficiency and accuracy. Therefore, the problems of long testing period, low efficiency of manual checking and low testing accuracy of vehicle-mounted applications in the related art when performing multilingual localization testing for overseas markets are solved.

[0021] Additional aspects and advantages of the application will be made apparent by the following description and the appended claims. BRIEF DESCRIPTION OF DRAWINGS

[0022] The above and / or additional aspects and advantages of the application will become apparent and be readily appreciated from the following description, including the accompanying drawings, wherein: Figure 1 A flowchart of a multilingual text testing method of a vehicle-mounted application according to an embodiment of the application is provided. Figure 2 A script recording and running flowchart according to an embodiment of the application is provided. Figure 3 A flowchart of obtaining vehicle machine text content according to an embodiment of the application is provided. Figure 4 A flowchart of comparing vehicle machine text content with standard text content according to an embodiment of the application is provided. Figure 5 An example diagram of a multilingual text testing method of a vehicle-mounted application according to an embodiment of the application is provided. Figure 6 A block diagram of a multilingual text testing device of a vehicle-mounted application according to an embodiment of the application is provided. Figure 7 A structural diagram of a testing platform according to an embodiment of the application is provided. DETAILED DESCRIPTION

[0023] The embodiments of the application are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference signs represent the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the accompanying drawings are exemplary and are intended to explain the application, and cannot be understood as a limitation of the application.

[0024] The following description, with reference to the accompanying drawings, outlines a multilingual text testing method, apparatus, testing platform, and medium for in-vehicle applications according to embodiments of this application. Addressing the problems mentioned in the background section, this application provides a multilingual text testing method for in-vehicle applications. This method involves using a webpage editing tool to record operations and collect elements from the interface of the in-vehicle application under multiple language versions. An operation script containing page traversal paths and language switching logic is automatically generated. The operation script is then executed to automatically extract the in-vehicle infotainment system text content for each language version, accurately compare it with pre-stored standard text, and automatically generate a test report. This effectively shortens manual testing time and significantly improves testing efficiency and accuracy. Therefore, it solves the problems of long testing cycles, low efficiency of manual verification, and low testing accuracy that exist in related technologies when conducting multilingual localization testing of in-vehicle applications for overseas markets.

[0025] Specifically, Figure 1 This is a flowchart illustrating a multilingual text testing method for an in-vehicle application provided in an embodiment of this application.

[0026] like Figure 1 As shown, this multilingual text testing method for in-vehicle applications is applied to a test platform that integrates web page editing tools. The test platform and the vehicle's infotainment system are connected, and the method includes the following steps: In step S101, the in-vehicle application to be tested is obtained, wherein the in-vehicle application to be tested has multiple language versions.

[0027] In this embodiment of the application, the in-vehicle application to be tested has multiple language versions to adapt to the usage needs of users in different countries and regions, and supports mainstream and less common languages ​​including but not limited to English, German, French, Spanish, Japanese, and Thai.

[0028] In one embodiment of this application, before obtaining the in-vehicle application to be tested, the method further includes: monitoring the connection status between the test platform and the vehicle system; if the connection status is a failure, an automatic reconnection mechanism is triggered.

[0029] It is understandable that the vehicle infotainment system and the test platform tools can be connected via ADB communication. In actual execution, the embodiments of this application can configure the ADB environment on the computer, enable ADB debugging on the vehicle infotainment system, and achieve communication via a USB duplex cable, which is simple to operate.

[0030] Furthermore, this application embodiment can also monitor the connection status between the test platform and the vehicle-mounted device via ADB (Automatic Data Controller) protocol; if a connection failure is detected (such as USB communication interruption, ADB service abnormality, or unauthorized device), a reconnection mechanism is automatically triggered to attempt to re-establish the communication connection, ensuring the stability of the device connection and thus guaranteeing the continuity of the subsequent automated testing process, avoiding test interruption due to device connection abnormalities.

[0031] In step S102, a web page editing tool is invoked to record operations and collect interface elements on multiple pages of the in-vehicle application under each language version, generating an operation script that includes page traversal paths and language switching logic.

[0032] Among them, the web page editing tool is the weditor tool, which provides at least one of the following functions: assisting in writing scripts, locating elements, and debugging code.

[0033] Specifically, the weditor tool, a UI element viewing and scripting tool developed based on Python, can parse the UI hierarchy of the current application on the vehicle's infotainment screen in real time via USB connection and display the attributes of each control in a visual manner. For example... Figure 2 As shown, this embodiment of the application can call the weditor tool to record and collect page information and compatible languages ​​involved in the ecosystem application to be tested, optimize the processing, and generate an operation script in txt format. In actual execution, the tester manually operates the application on the vehicle's infotainment system (such as clicking menus, switching language settings, swiping pages, etc.), and calls the weditor tool to synchronously capture the node changes and interaction events involved in the operation, and saves these operation sequences as a replayable operation script (usually saved in .txt format).

[0034] It should be noted that the operation script in this embodiment includes the page navigation order, page information, and control click paths. It also explicitly records key nodes for language switching (e.g., entering "System Settings → Language and Input Method → ​​Select Target Language"), ensuring that the complete user path in a multilingual environment can be accurately reproduced during the subsequent automated execution phase. The generated operation script can be directly loaded and parsed by the automated testing tool described in this application, serving as the basis for subsequent text comparison.

[0035] In step S103, the operation script is run to extract multiple pieces of in-vehicle text content for the in-vehicle application under each language version, compare the multiple pieces of in-vehicle text content with the pre-stored standard text content, and generate a test report for the in-vehicle application under each language version.

[0036] In one embodiment of this application, an operation script is run to extract multiple pieces of in-vehicle text content for the in-vehicle application under each language version, including: running the operation script to obtain the layout information of each page; extracting the text fields from the layout information of each page; and performing deduplication, filtering of non-business text, and encoding standardization on the text fields to obtain the in-vehicle text content.

[0037] Specifically, such as Figure 3 As shown, in this embodiment of the application, the operation script recorded in the above embodiment can be added to the test platform for running. During the running process, the user's operation path on the vehicle system (such as page jump, language switching, etc.) is automatically reproduced, and the complete layout information of the current page is obtained in a loop, and the corresponding XML file is generated. Then, the text field (text text) is extracted from the XML file to obtain the original text set.

[0038] Furthermore, to improve the accuracy and efficiency of the comparison, this embodiment of the application can also preprocess the original text set: such as deduplication to remove duplicate interface text, or encoding standardization to unify the character encoding format of the text and standardize spaces, line breaks, and special symbols to ensure that the vehicle-mounted text and the standard text are consistent in format. After processing, a vehicle-mounted text content with a clear structure and complete semantics is obtained, which serves as the input data for subsequent comparisons.

[0039] In one embodiment of this application, multiple pieces of in-vehicle infotainment text content are compared with pre-stored standard text content to generate a test report for the in-vehicle application under each language version. This includes: sorting the multiple pieces of in-vehicle infotainment text content according to the page traversal order; performing a complete match query between each sorted piece of in-vehicle infotainment text content and all entries in the standard text content; if a matching entry exists in the standard text content, the corresponding in-vehicle infotainment text content is marked as a first type, otherwise it is marked as a second type; and generating a test report for the in-vehicle application under each language version based on the marking results.

[0040] It is understood that, in this embodiment of the application, the extracted in-vehicle text content is sorted chronologically according to the page traversal order recorded in the operation script to maintain a logical order consistent with the user's actual operation path; subsequently, as Figure 4As shown, each sorted piece of in-vehicle text content is matched against the corresponding language version of the standard text content stored locally. If a piece of in-vehicle text has a completely matching entry in the standard text library, it is marked as Type 1 (Pass), indicating that the text translation is correct and conforms to the standard. If no matching entry is found, it is marked as Type 2 (Fail), and the specific missing or inconsistent text content is recorded. Simultaneously, this embodiment can also perform preliminary cause analysis on Fail entries. Finally, based on the marking results of all text items, a structured test report is automatically generated.

[0041] Furthermore, after generating test reports for the in-vehicle application under each language version, the process also includes: visually displaying the test reports on the graphical user interface of the test platform, wherein the test reports are in tabular format.

[0042] For example, suppose this application records two applications, application A and application B, in sequence. For each application, five pages are recorded, switching between two languages. The tool replicates the script to extract text for comparison in the following order: Application A - Language 1 - Page 1: Extract text information from XML, compare, record, and display the results; Application A-Language 1-Page 5: Extract text information from XML, compare, record, and display the results; Application A-Language 2-Page 1: Extract text information from XML, compare, record, and display the results; Application A-Language 2-Page 5: Extract text information from XML, compare, record, and display the results; Application of B-language 1-Page 1: Extract text information from XML, compare, record, and display the results; Application of B-language 2-page 5: Extract text information from XML, compare, record, and display the results; Test results presentation: Pass and Fail items are categorized and filtered, with test results noted. For Fail items, the reasons for the failures are analyzed. An Excel-formatted test report is automatically generated, and the results are simultaneously presented to the tester in the tool interface.

[0043] For example, as shown in Table 1, the number of texts on the vehicle's infotainment system is n, specifically A1-An, and the number of standard texts is n, specifically B1-Bn. A1-An are compared with B1-Bn respectively. The texts A1, A2...An on the vehicle's infotainment system are obtained in sequence and compared with the texts B1-Bn in the standard text. If A1 and B1-Bn have matching content, mark them as Pass and present them to the tester on the tool page, while also marking them as Pass in the test report.

[0044] If there is no match between A1 and B1-Bn, mark it as Fail, provide the reason, and present it to the tester on the tool page, while also marking it as Fail in the test report. ... If An and B1-Bn have matching content, mark them as Pass and present them to the tester on the tool page, while also marking them as Pass in the test report.

[0046] If there is no match between An and B1-Bn, mark it as Fail, provide the reason, and present it to the tester on the tool page, while also marking it as Fail in the test report.

[0047] Table 1

[0048] The following is combined Figure 5 This application provides a detailed description of the overall process of the multilingual text testing method for in-vehicle applications, which mainly consists of four parts: device connection, information collection, language and text comparison, and presentation of test results. Utilizing automation tools, the method automates the testing of multilingual translation terminology verification for overseas ecosystem applications. The details are as follows: Step 1: Device connection: The vehicle's infotainment system and the tool are connected via ADB communication.

[0049] The computer is configured with an ADB environment, and the car's infotainment system is enabled for ADB debugging. Communication can be achieved via a USB full-duplex cable, making the operation simple. Additionally, the tool includes an ADB connection listener; if a connection failure is detected, it will automatically attempt to reconnect, ensuring device connection stability.

[0050] Step 2: Information collection (recording script).

[0051] The automation tool integrates the weditor tool, a Python-based tool for viewing app elements. Weditor provides functions such as assisting in script writing, element location, and code debugging. It records and collects page information and language compatibility data for the ecosystem application being tested, optimizes the data, and generates a TXT format operation script.

[0052] Step 3: Language and text comparison.

[0053] Add the operation script recorded in step 2 to the automation tool. During operation, the tool will replicate all the script content involved in step 2 in the background, continuously retrieve information from each page, generate an XML file, extract the text involved in the XML file, optimize the text sorting, and store it. Place the standard copy locally. During runtime, the tool reads the text in the standard copy in real time, compares the text information extracted by the vehicle's system with the standard copy sequentially, categorizes the results, and records complete matches as "Pass" and non-matches as "Fail".

[0054] Step 4: Presentation of test results.

[0055] The system categorizes and filters Pass and Fail items, noting the test results, providing analysis and reasons for Fail items, automatically generating an Excel test report, and presenting the results to the tester in the tool interface.

[0056] The multilingual text testing method for in-vehicle applications proposed in this application involves using a web page editing tool to record operations and collect elements from the interface of the in-vehicle application under multiple language versions. This automatically generates an operation script containing page traversal paths and language switching logic. The script is then executed to automatically extract the in-vehicle infotainment text content for each language version, accurately compare it with pre-stored standard text, and automatically generate a test report. This effectively shortens manual testing time and significantly improves testing efficiency and accuracy. Therefore, it solves the problems of long testing cycles, low efficiency of manual verification, and low testing accuracy that exist in related technologies when conducting multilingual localization testing of in-vehicle applications for overseas markets.

[0057] It should be noted that the multilingual text testing method for in-vehicle applications in this application is compatible with mainstream in-vehicle host system suppliers such as Neusoft, Desay, and Magnesium, as well as in-vehicle chip platforms such as 8155 and 8255. It supports translation comparison testing of monolingual or multilingual text, and supports different applications and screen sizes (achieving automatic adjustment for different screens), and can be reused across projects.

[0058] Next, referring to the accompanying drawings, a multilingual text testing device for in-vehicle applications according to an embodiment of this application is described. The device is applied to a testing platform that integrates web page editing tools and is connected to the vehicle's infotainment system.

[0059] Figure 6 This is a block diagram of a multilingual text testing device for an in-vehicle application according to an embodiment of this application.

[0060] like Figure 6 As shown, the multilingual text testing device 10 for the vehicle application includes: an acquisition module 100, a processing module 200, and a testing module 300.

[0061] The acquisition module 100 is used to acquire the in-vehicle application to be tested, which has multiple language versions. The processing module 200 is used to call a web page editing tool to record operations and collect interface elements of multiple pages of the in-vehicle application to be tested in each language version, and generate an operation script containing page traversal paths and language switching logic. The testing module 300 is used to run the operation script to extract multiple pieces of in-vehicle text content of the in-vehicle application to be tested in each language version, compare the multiple pieces of in-vehicle text content with pre-stored standard text content, and generate a test report of the in-vehicle application to be tested in each language version.

[0062] In one embodiment of this application, the processing module 200 is further configured to run an operation script to obtain the layout information of each page; extract the text fields from the layout information of each page; and perform deduplication, filtering of non-business text, and encoding standardization processing on the text fields to obtain the vehicle-mounted text content.

[0063] In one embodiment of this application, the testing module 300 is further configured to sort multiple vehicle-mounted text contents according to the page traversal order; perform a complete match query between each sorted vehicle-mounted text content and all entries in the standard text content; if a matching entry exists in the standard text content, the corresponding vehicle-mounted text content is marked as a first type, otherwise it is marked as a second type; and generate a test report for the vehicle application to be tested in each language version based on the marking results.

[0064] In one embodiment of this application, the web page editing tool is a web editor tool, which has at least one of the functions of assisting in script writing, locating elements, and debugging code.

[0065] In one embodiment of this application, the multilingual text testing device 10 for in-vehicle applications further includes: a monitoring module, used to monitor the connection status between the testing platform and the vehicle system before acquiring the in-vehicle application to be tested; if the connection status is a failure status, an automatic reconnection mechanism is triggered.

[0066] In one embodiment of this application, the multilingual text testing device 10 for in-vehicle applications further includes: a display module, used to visually display the test reports on the graphical user interface of the testing platform after generating test reports for the in-vehicle application to be tested in each language version, wherein the test reports are tabular format files.

[0067] It should be noted that the foregoing explanation of the multilingual text testing method embodiment for in-vehicle applications also applies to the multilingual text testing device for in-vehicle applications in this embodiment, and will not be repeated here.

[0068] The multilingual text testing device for in-vehicle applications proposed in this application, by calling a web page editing tool to record operations and collect elements from the interface of the in-vehicle application under test in multiple language versions, automatically generates an operation script containing page traversal paths and language switching logic, and executes the operation script to automatically extract the in-vehicle text content in each language version, accurately compares it with pre-stored standard text, and automatically generates a test report. This effectively shortens manual testing time and significantly improves testing efficiency and accuracy. Therefore, it solves the problems of long testing cycles, low efficiency of manual verification, and low testing accuracy in related technologies when conducting multilingual localization testing of in-vehicle applications for overseas markets.

[0069] Figure 7 A schematic diagram of the structure of the test platform provided in an embodiment of this application. The test platform may include: The memory 701, the processor 702, and the computer program stored on the memory 701 and executable on the processor 702.

[0070] When the processor 702 executes the program, it implements the multilingual text testing method for in-vehicle applications provided in the above embodiments.

[0071] Furthermore, the testing platform also includes: Communication interface 703 is used for communication between memory 701 and processor 702.

[0072] The memory 701 is used to store computer programs that can run on the processor 702.

[0073] The memory 701 may include high-speed RAM (Random Access Memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0074] If the memory 701, processor 702, and communication interface 703 are implemented independently, then the communication interface 703, memory 701, and processor 702 can be interconnected via a bus to complete communication between them. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0075] Optionally, in a specific implementation, if the memory 701, processor 702, and communication interface 703 are integrated on a single chip, then the memory 701, processor 702, and communication interface 703 can communicate with each other through an internal interface.

[0076] The processor 702 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of this application.

[0077] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described multilingual text testing method for in-vehicle applications.

[0078] This application also provides a computer program product, including: a computer program or instructions, which, when executed, implement the multilingual text testing method for in-vehicle applications as described in the above embodiments.

[0079] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0080] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0081] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0082] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0083] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0084] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A multilingual text testing method for in-vehicle applications, characterized in that, The method is applied to a test platform that integrates a web page editing tool and is connected to an in-vehicle infotainment system. The method includes the following steps: Obtain the in-vehicle application to be tested, wherein the in-vehicle application to be tested has multiple language versions; The web page editing tool is invoked to record operations and collect interface elements on multiple pages of the in-vehicle application under each language version, generating an operation script that includes page traversal paths and language switching logic. The operation script is run to extract multiple pieces of in-vehicle text content for the in-vehicle application under each language version. The multiple pieces of in-vehicle text content are compared with pre-stored standard text content to generate a test report for the in-vehicle application under each language version.

2. The multilingual text testing method for vehicle applications according to claim 1, characterized in that, Run the operation script to extract multiple pieces of in-vehicle text content for each language version of the in-vehicle application under test, including: Run the operation script to obtain the layout information of each page; Extract the text fields from the layout information of each page; The text field is deduplicated, non-business text is filtered, and the encoding is standardized to obtain the in-vehicle infotainment text content.

3. The multilingual text testing method for vehicle applications according to claim 1, characterized in that, The multiple pieces of in-vehicle text content are compared with pre-stored standard text content to generate a test report for the in-vehicle application under test in each language version, including: The multiple pieces of text content from the vehicle's infotainment system are sorted according to the page traversal order; Perform a full match query between each sorted piece of in-vehicle text content and all entries in the standard text content; If a matching entry exists in the standard text content, the corresponding vehicle-mounted text content is marked as the first type; otherwise, it is marked as the second type. Based on the labeling results, a test report is generated for the in-vehicle application under each language version.

4. The multilingual text testing method for vehicle applications according to claim 1, characterized in that, The webpage editing tool is a web editor, which has at least one function: assisting in script writing, locating elements, and debugging code.

5. The multilingual text testing method for vehicle applications according to claim 1, characterized in that, Before obtaining the in-vehicle application to be tested, the following is also included: Monitor the connection status between the test platform and the vehicle system; If the connection status is in a failed state, an automatic reconnection mechanism is triggered.

6. The multilingual text testing method for vehicle applications according to claim 1, characterized in that, After generating test reports for the in-vehicle application under test in each language version, the following is also included: The test report is visualized on the graphical user interface of the test platform, wherein the test report is a tabular file.

7. A multilingual text testing device for vehicle applications, characterized in that, The device is applied to a test platform, which integrates a web page editing tool. The test platform is communicatively connected to an in-vehicle infotainment system. The device includes: The acquisition module is used to acquire the in-vehicle application to be tested, wherein the in-vehicle application to be tested has multiple language versions; The processing module is used to call the web page editing tool to record operations and collect interface elements on multiple pages of the in-vehicle application under each language version, and generate an operation script containing page traversal paths and language switching logic. The testing module is used to run the operation script to extract multiple pieces of in-vehicle text content of the in-vehicle application under each language version, compare the multiple pieces of in-vehicle text content with pre-stored standard text content, and generate a test report of the in-vehicle application under each language version.

8. A testing platform, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the multilingual text testing method for an in-vehicle application as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they implement the multilingual text testing method for in-vehicle applications as described in any one of claims 1-6.

10. A computer program product comprising: A computer program or instruction, characterized in that, when executed, the computer program or instruction implements the multilingual text testing method for vehicle applications as described in any one of claims 1-6.

Images