A code testing system and method of a screen menu type adjustment

Abstract

The application discloses a code testing system and method of a screen menu type adjustment mode, relates to the technical field of OSD testing, and mainly aims to realize verification testing on the screen menu type adjustment mode in the development stage of the screen menu type adjustment mode. The main technical scheme comprises the following steps: a testing platform is used for deploying to-be-tested codes of to-be-tested OSD, generating OSD data in response to an OSD request, wherein the OSD request corresponds to a function point of the to-be-tested codes, and the OSD is the screen menu type adjustment mode; a format conversion device is used for converting the data format of the OSD data into a target format required by a display device; and the display device is used for performing display corresponding to the OSD data.

Description

Technical Field

[0001] This invention relates to the field of OSD testing technology, and in particular to a code testing system and method with a screen menu-based adjustment method. Background Technology

[0002] On-screen display (OSD) is used in display devices such as LCD and LED, and refers to the generation of special characters or graphics on the screen of the display device.

[0003] To ensure the quality of the OSD (On-Screen Display), it needs to be tested. During OSD development, because the OSD output belongs to the icon layer (ICON layer) and the OSD outputs digital signals that cannot be directly displayed on the screen, OSD testing is typically performed after the chip to be deployed has been fabricated. That is, after receiving the chip, the OSD code is burned into it, the chip is placed on the corresponding FPGA development board, and then connected to the screen before OSD testing can be conducted.

[0004] It is evident that the existing OSD testing method can only be carried out after the chip is fabricated, making it difficult to verify and test the OSD during the OSD development stage. Summary of the Invention

[0005] In view of this, the present invention proposes a code testing system and method for screen menu-based adjustment methods, the main purpose of which is to realize the verification test of screen menu-based adjustment methods during the research and development stage.

[0006] To achieve the above objectives, the present invention mainly provides the following technical solutions:

[0007] In a first aspect, the present invention provides a code testing system with a screen menu-based adjustment method, the system comprising:

[0008] The testing platform is used to deploy the code to be tested in the OSD to be tested, and to generate OSD data in response to OSD requests. The OSD requests correspond to the functional points of the code to be tested, and the OSD is adjusted in a screen menu manner.

[0009] A format conversion device for converting the OSD data format into a target format required by the display device;

[0010] The display device is used to perform a display corresponding to the OSD data.

[0011] Secondly, this invention provides a code testing method for a screen menu-based adjustment method, the method comprising:

[0012] The test platform responds to the OSD request and generates OSD data. The test platform deploys the test code of the OSD to be tested. The OSD request corresponds to the function point of the test code. The OSD is adjusted in a screen menu manner.

[0013] The format conversion device converts the OSD data format into the target format required by the display device;

[0014] The display device performs a display corresponding to the OSD data.

[0015] Thirdly, the present invention provides a computer-readable storage medium comprising a stored program, wherein, when the program is executed, the device on which the storage medium is located executes the code testing method of the screen menu-based adjustment method described in the second aspect.

[0016] By employing the above technical solution, the code testing system and method for screen menu-based adjustment methods provided by this invention, when testing the code for screen menu-based adjustment methods is required, the test platform deploys the test code of the OSD to be tested, and the test platform generates OSD data in response to the OSD request corresponding to the function point of the test code. A format conversion device converts the data format of the OSD data into the target format required by the display device. Then, the display device executes the display corresponding to the OSD data. It is evident that, in the solution provided by this invention, when testing the code for screen menu-based adjustment methods is required, there is no need to wait for the chip tape-out of the screen menu-based adjustment method. Through the interaction between the test platform, the format conversion device, and the display device, the OSD data of the function point corresponding to the screen menu-based adjustment method code can be displayed on the display device, thereby completing the testing of the screen menu-based adjustment method code. Therefore, the solution provided by this invention can realize the verification testing of screen menu-based adjustment methods during the development stage.

[0017] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1This diagram illustrates the structure of a code testing system with a screen menu-based adjustment method according to an embodiment of the present invention.

[0020] Figure 2 This diagram illustrates the structure of a code testing system with a screen menu-based adjustment method according to another embodiment of the present invention.

[0021] Figure 3 A flowchart of a code testing method for a screen menu-based adjustment mode provided in an embodiment of the present invention is shown;

[0022] Figure 4 A flowchart of a code testing method for a screen menu-based adjustment mode provided by another embodiment of the present invention is shown. Detailed Implementation

[0023] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0024] On-screen display (OSD) is used in display devices such as LCD and LED displays. It involves displaying special characters or graphics on the screen. These characters or graphics represent the display device's performance parameters, such as color, volume, and image quality. Users can adjust these parameters to optimize the display's performance.

[0025] To ensure OSD quality, testing is necessary. During OSD development, because OSD output belongs to the icon layer (ICON layer) and outputs digital signals that cannot be directly displayed on the screen, OSD testing is typically performed after the chip to be deployed has been fabricated. That is, after receiving the chip, the OSD code is burned into it, the chip is placed on the corresponding FPGA development board, and then connected to the screen before testing can be conducted. Therefore, this existing OSD testing method requires chip fabrication, making verification testing during the OSD development phase difficult.

[0026] To enable verification testing of screen menu-based adjustment methods during the development phase, this invention provides a code testing system and method for screen menu-based adjustment methods. This allows for early verification testing during the development phase, accelerating the development progress of the screen menu-based adjustment method and the firmware development of the corresponding chip. The code testing system and method for screen menu-based adjustment methods provided in this invention are described in detail below.

[0027] like Figure 1 As shown, this embodiment of the invention provides a code testing system with a screen menu-based adjustment method. The system mainly includes:

[0028] Test platform 11 is used to deploy the test code of the OSD to be tested, and to generate OSD data in response to OSD requests, wherein the OSD request corresponds to the function point of the test code, and the OSD is a screen menu-style adjustment method.

[0029] The format conversion device 12 is used to convert the data format of the OSD data into the target format required by the display device 33;

[0030] The display device 13 is used to perform a display corresponding to the OSD data.

[0031] The following is a detailed description of the test platform 11, format conversion device 12, and display device 13 in the code testing system for screen menu-based adjustment:

[0032] Test Platform 11:

[0033] The OSD to be tested is the OSD that needs to undergo verification testing. It can be any OSD in the development stage that requires verification testing. The main verification object of the OSD to be tested is its test code. The test code is the code used to implement the functionality of the OSD to be tested, and therefore needs to be tested. The test code includes multiple functional points, and the purpose of testing it is to verify whether each functional point can successfully complete its corresponding function.

[0034] Test platform 11 is a platform for deploying the OSD to be tested and implementing the functionality of the OSD. The specific type of test platform 11 is not specifically limited in this embodiment of the invention and can be selected based on specific business requirements. For example, the test platform is a HAPS platform, and the OSD to be tested is deployed in the test layer of the HAPS platform, i.e., the TB layer.

[0035] like Figure 2As shown, the test platform 11 includes a deployment unit 111, which is responsible for deploying the test code of the OSD to be tested. The deployment unit 111 is used to compile the test code of the OSD to be tested, generate an executable file for OSD code testing, and deploy the executable file.

[0036] The purpose of deployment unit 111 in compiling the code to be tested is to translate the code written in a programming language into equivalent machine language code, so that the testing platform can read and execute the code. After compilation, the compiled code forms an executable file, which is a file that the testing platform's system can load and execute. The specific type of the executable file is not specifically limited in this embodiment and can be selected based on specific business requirements. For example, executable files can be .exe, .sys, .com, etc. After generating the executable file for OSD code testing, deployment unit 111 executes the executable file to deploy the code to be tested, thereby enabling the testing platform 11 to implement the functionality of the code to be tested.

[0037] After deploying the test code to the OSD to be tested on test platform 11, testing of the test code can begin. Test platform 11 needs to perform test-related operations based on OSD requests; therefore, test platform 11 needs to listen for OSD requests. The following describes the initiation of OSD requests, which includes the following two scenarios: First, business personnel initiate OSD requests to test platform 11 based on specific test requirements. Second, to improve the automation of testing, multiple OSD request test cases are preset, and when starting the test, OSD requests corresponding to each OSD request test case are initiated sequentially.

[0038] The code under test includes multiple functionalities. The purpose of testing it is to verify whether each functionality can successfully perform its corresponding function. The process of verifying the test functionalities is based on OSD requests. Therefore, after the test platform listens for OSD requests, it needs to check whether the corresponding functionalities exist in the code under test within the OSD being tested.

[0039] When the test platform 11 detects that there are corresponding functional points in the test code of the OSD to be tested, it means that the test platform 11 can respond to the OSD request. Therefore, the test platform 11 generates OSD data in response to the OSD request.

[0040] like Figure 2As shown, the test platform 11 also includes a second prompting unit 112, used to issue an exception prompt for the OSD request when it is detected that the received OSD request does not have a corresponding functional point in the code under test. When it is detected that the OSD request does not have a corresponding functional point in the code under test of the OSD being tested, the following two exceptions may occur: First, the OSD request is an erroneous request. Second, the code under test may have omitted the functional point corresponding to the OSD request. The prompt for the first type of exception allows business personnel to promptly replace the OSD request with an available one. The prompt for the second type of exception allows business personnel to promptly confirm whether the code corresponding to the OSD request has been omitted.

[0041] When the test platform 11 detects an OSD request and finds that the corresponding functional point exists in the test code of the OSD to be tested, it needs to check whether there is OSD display content corresponding to the OSD request in the screen menu display storage device, and perform corresponding processing based on the detection result. The screen menu display storage device stores the display content involved in the use of the OSD to be tested, which includes, but is not limited to, fonts or graphics related to the display device's operating indicators. For example, the display content may be fonts and graphics related to color adjustment.

[0042] like Figure 2 As shown, the test platform 11 includes a first prompting unit 113, which is used to issue a prompt that OSD display content is missing in the screen menu display storage device when it is detected that there is no OSD display content corresponding to the OSD request in the screen menu display storage device.

[0043] The absence of OSD display content corresponding to the OSD request in the on-screen menu storage device indicates one of two possible anomalies: First, the test code for the OSD contains the functionality to execute the OSD request, but the on-screen menu storage device has omitted storing the corresponding display content. Second, the test code for the OSD does not contain the functionality to execute the OSD request, therefore the on-screen menu storage device has not stored the corresponding display content. The notification for the first anomaly allows business personnel to promptly add the corresponding OSD display content to the on-screen menu storage device. The notification for the second anomaly allows business personnel to promptly confirm whether the code corresponding to the OSD request has been omitted.

[0044] When the test platform detects that there is OSD display content in the storage device that corresponds to the OSD request in the screen menu, it means that the test platform can generate OSD data corresponding to the OSD request. In this case, the test platform responds to the OSD request by generating OSD data.

[0045] like Figure 2 As shown, the test platform 11 includes a generation unit 114. The generation unit 114 is used to extract the OSD display content corresponding to the OSD request from the screen menu display storage device, and determine the OSD display parameters of the OSD display content based on the OSD request.

[0046] OSD data consists of OSD display content and OSD display parameters. The display parameters are used to control how the OSD display content is displayed on the display image of the display device. The display method may include, but is not limited to, display size, display position, and display resolution.

[0047] The OSD request includes OSD type and display requirements. The displayed content is determined based on the OSD type and display requirements. The OSD display parameters are also determined based on these requirements. If the OSD type requirement in the request is "color adjustment," the test platform will extract the corresponding OSD display content—"color adjustment fonts and graphics"—from the screen menu display storage device. If the OSD display requirement in the request is "display size 16×16," then the OSD display parameters for determining the OSD display content will be "display size 16×16."

[0048] After generating OSD data, the test platform transmits the OSD data to a format conversion device so that the format conversion device can convert the OSD data into the data format required by the display device.

[0049] Format conversion device 12:

[0050] During the OSD development process, OSD data belongs to the icon layer, and since OSD data is a digital signal that cannot be directly output to the screen of display device 13 for display, in order to facilitate verification and testing, the format conversion device needs to convert the OSD data format into the target format required by display device 13.

[0051] For example, the target format required by the display device 13 is generally HDMI (High Definition Multimedia Interface) format. Therefore, regardless of the data format of the OSD data, the format conversion device 12 converts its data format to HDMI format so that the display device can read the OSD data and perform the corresponding display.

[0052] The specific type of the format conversion device 12 is not limited in this invention, as long as it can convert the OSD data format into the target format required by the display device 13. For example, the format conversion device is a VBYONE2 HDMI daughter card.

[0053] Display device 13:

[0054] After receiving the target data transmitted by the format conversion device, the display device 13 can perform the display corresponding to the OSD data because the data format of the target data has been converted to the target format by the format conversion device.

[0055] The display device 13 is specifically used to overlay OSD display content onto a display image based on OSD display parameters, wherein the display image is the image currently displayed by the display device.

[0056] For example, if the OSD display content is "color-adjusted fonts and graphics" and the OSD display parameter is "display size is 16×16", then the display device will display color-adjusted fonts and graphics of size 16×16 on the display image.

[0057] The code testing system for screen menu-based adjustment methods provided in this embodiment of the invention, when testing the code for screen menu-based adjustment methods is required, deploys the test code of the OSD to be tested on the test platform. The test platform generates OSD data in response to OSD requests corresponding to the function points of the test code. A format conversion device converts the data format of the OSD data into the target format required by the display device. Then, the display device executes the display corresponding to the OSD data. Therefore, in the solution provided in this embodiment of the invention, when testing the code for screen menu-based adjustment methods is required, there is no need to wait for the chip tape-out of the screen menu-based adjustment method. Through the interaction between the test platform, the format conversion device, and the display device, the OSD data of the function points corresponding to the screen menu-based adjustment method code can be displayed on the display device, thereby completing the testing of the screen menu-based adjustment method code. Therefore, the solution provided in this embodiment of the invention can realize the verification testing of screen menu-based adjustment methods during the development stage.

[0058] Furthermore, according to Figure 1 The system shown in the figure, another embodiment of the present invention also provides a code testing system with a screen menu-based adjustment method, such as Figure 2 As shown, the system includes, in addition to Figure 1 In addition to the test platform 11, format conversion device 12, and display device 13 shown, there is also an inspection device 14. The inspection device 14 will be described below:

[0059] The main functions of the testing equipment 14 include the following two points:

[0060] First, the testing device 14 is used to mark the corresponding functional points in the code to be tested that have passed the test when the display of the testing display device 13 matches the OSD request.

[0061] Second, the testing device 14 is used to mark the corresponding function point in the code to be tested that failed the test when the display on the testing display device 14 does not match the OSD request.

[0062] Display device 13 performs the display corresponding to OSD data, which can reflect the response result of test platform 11 to OSD request. Therefore, in order to verify whether the function point under test can successfully implement its corresponding function, after display device 13 performs the display corresponding to OSD data, it is necessary to check whether the display of display device 13 matches the OSD request.

[0063] The process of testing equipment 14 to check whether the display of display device 13 matches the OSD request mainly involves: checking whether the display content of the display device is consistent with the OSD type requirements and OSD display requirements in the OSD request.

[0064] For example, the display content obtained from the display device 13 involves the display graphics "color-adjusted fonts and graphics" and the size of the display graphics "display size is 16×16". If the OSD type requirement in the OSD request is "color-adjusted fonts and graphics" and the OSD display requirement is "display size is 16×16", then it is checked whether the display content involving the display graphics "color-adjusted fonts and graphics" and the size of the display graphics "display size is 16×16" are consistent with the OSD type requirement "color-adjusted fonts and graphics" and the OSD display requirement "display size is 16×16" in the OSD request.

[0065] If the testing device 14 detects that the display of the display device 13 matches the OSD request, it means that the testing platform 11 has correctly responded to the OSD request. The function point in the test code of the OSD under test that corresponds to the OSD request has successfully responded to the OSD request, and its function can be successfully implemented. Therefore, the function point in the test code corresponding to the OSD request has passed the test.

[0066] If the testing device 14 detects that the display of the display device 13 does not match the OSD request, it indicates that the testing platform 11 did not respond to the OSD request correctly. The functional point in the test code of the OSD under test, which corresponds to the OSD request, failed to respond to the OSD request, and its functional implementation is abnormal. Therefore, the functional point corresponding to the OSD request in the test code is marked as failing the test so that business personnel can handle the abnormality based on the marking.

[0067] Since the code under test includes multiple functionalities, and each functionality requires an OSD request to complete the test, the verification device 14 determines whether the test of the code under test is complete by: verifying whether all functionalities of the code under test are marked. If all functionalities are marked, the test of the code under test is complete. If there are still functionalities that are not marked, the test of the code under test is incomplete, and subsequent tests continue.

[0068] When the testing equipment 14 determines that the testing of the code under test is complete, it compiles the annotations for each functional point in the code under test and generates a test report. The purpose of generating the test report is to enable business personnel to more intuitively understand the test results.

[0069] The code testing system with a screen menu-based adjustment method provided in this embodiment of the invention can mark OSD requests based on the matching between the display of the display device and the OSD request, thereby enabling testers to intuitively understand the OSD test status based on the marked OSD requests.

[0070] like Figure 3 As shown, this embodiment of the invention provides a code testing method for a screen menu-based adjustment method, which mainly includes:

[0071] 201. The test platform responds to the OSD request and generates OSD data, wherein the test platform deploys the test code of the OSD to be tested, the OSD request corresponds to the function point of the test code, and the OSD is adjusted in a screen menu manner.

[0072] 202. The format conversion device converts the data format of the OSD data into the target format required by the display device.

[0073] 203. The display device performs a display corresponding to the OSD data.

[0074] The code testing method for screen menu-based adjustment methods provided in this embodiment of the invention involves the following steps: When testing the code for a screen menu-based adjustment method is required, the test platform deploys the test code for the OSD to be tested. The test platform generates OSD data in response to OSD requests corresponding to the function points of the test code. A format conversion device converts the data format of the OSD data into the target format required by the display device. Then, the display device executes the display corresponding to the OSD data. Therefore, the solution provided in this embodiment of the invention eliminates the need to wait for the chip tape-out of the screen menu-based adjustment method when testing the code. Through the interaction between the test platform, the format conversion device, and the display device, the OSD data corresponding to the function points of the screen menu-based adjustment method code can be displayed on the display device, thereby completing the testing of the screen menu-based adjustment method code. Therefore, the solution provided in this embodiment of the invention can achieve verification testing of screen menu-based adjustment methods during the development stage.

[0075] Optionally, step 201, in which the test platform responds to the OSD request and generates OSD data, includes the following specific process: the test platform extracts the OSD display content corresponding to the OSD request from the screen menu display storage device, and determines the OSD display parameters of the OSD display content based on the OSD request, wherein the OSD display content and the OSD display parameters constitute the OSD data.

[0076] Optionally, the method further includes the following step: when the test platform detects that there is no OSD display content corresponding to the OSD request in the screen menu display storage device, it issues a prompt that there is a lack of OSD display content in the screen menu display storage device.

[0077] Optionally, step 201, the specific process of the display device performing the display corresponding to the OSD data, includes: the display device overlaying the OSD display content onto the display image based on the OSD display parameters, wherein the display image is the image currently displayed by the display device.

[0078] Optionally, the deployment of the test code of the OSD to be tested on the test platform involved in step 201 includes: the test platform compiling the test code to be tested, generating an executable file for OSD code testing, and deploying the executable file.

[0079] Optionally, the method further includes the following step: when the test platform detects that the received OSD request does not have a corresponding function point in the code to be tested, it issues an exception prompt for the OSD request.

[0080] Optionally, after the display device performs the display corresponding to the OSD data in step 203, the method further includes: when the verification device verifies that the display of the display device matches the OSD request, marking that the function point corresponding to the OSD request in the code to be tested has passed the test; and / or, when the verification device verifies that the display of the display device does not match the OSD request, marking that the function point corresponding to the OSD request in the code to be tested has failed the test.

[0081] Optionally, the method further includes the following steps: when the testing device determines that the test for the code to be tested is completed, it statistically analyzes the annotations of each functional point in the code to be tested and forms a test report.

[0082] Furthermore, according to Figure 3 The method shown in this invention, in another embodiment, also provides a code testing method for screen menu-based adjustment, such as... Figure 4 As shown, the method mainly includes:

[0083] 301. Deploy the test code of the OSD to be tested on the test platform.

[0084] 302. The test platform listens for OSD requests.

[0085] 303. When the test platform receives an OSD request, it checks whether the OSD request has a corresponding functional point in the test code of the OSD to be tested; if it does, proceed to step 304; otherwise, proceed to step 312.

[0086] The code under test includes multiple functionalities. The purpose of testing it is to verify whether each functionality can successfully perform its corresponding function. The process of verifying the test functionalities is based on OSD requests. Therefore, after the test platform listens for OSD requests, it checks whether the corresponding functionalities exist in the code under test within the OSD being tested.

[0087] 304. The test platform responds to the OSD request and generates OSD data.

[0088] When the OSD request detects that the corresponding functional point exists in the code to be tested within the OSD to be tested, it indicates that the testing platform can respond to the OSD request. Therefore, the testing platform generates OSD data in response to the OSD request. The specific description of generating OSD data is basically the same as that in step 101 above, so it will not be repeated here.

[0089] 305. The format conversion device converts the OSD data format into the target format required by the display device.

[0090] 306. The display device performs the display corresponding to the OSD data.

[0091] 307. Check whether the display of the testing equipment matches the OSD request; if it matches, proceed to step 308; otherwise, proceed to step 309.

[0092] The display device executes the display corresponding to the OSD data, which can reflect the response result of the test platform to the OSD request. Therefore, in order to verify whether the function point under test can successfully implement its corresponding function, after the display device executes the display corresponding to the OSD data, it is necessary to check whether the display device's display matches the OSD request.

[0093] The process of verifying whether the display of the testing equipment matches the OSD request mainly involves: checking whether the display content of the display equipment is consistent with the OSD type requirements and OSD display requirements in the OSD request.

[0094] For example, obtaining the display content of the display device involves display graphics "color-adjusted fonts and graphics" and the size of the display graphics "display size is 16×16". If the OSD type requirement in the OSD request is "color-adjusted fonts and graphics" and the OSD display requirement is "display size is 16×16", then it is checked whether the display content involving display graphics "color-adjusted fonts and graphics" and the size of the display graphics "display size is 16×16" are consistent with the OSD type requirement "color-adjusted fonts and graphics" and the OSD display requirement "display size is 16×16" in the OSD request.

[0095] 308. The OSD request corresponding to the functional point in the code under test has passed the test.

[0096] If the testing equipment detects that the display of the display device matches the OSD request, it indicates that the testing platform has correctly responded to the OSD request. The functional points in the test code of the OSD under test that correspond to the OSD request have successfully responded to the OSD request, and their functions can be successfully implemented. Therefore, the functional points in the test code corresponding to the OSD request have passed the test.

[0097] 309. The OSD request function in the code under test failed the test.

[0098] If the testing equipment detects a mismatch between the display on the display device and the OSD request, it indicates that the testing platform has not responded correctly to the OSD request. The functional point in the code under test of the OSD under test, which corresponds to the OSD request, has failed to respond to the OSD request, and its functional implementation is abnormal. Therefore, the functional point in the code under test corresponding to the OSD request is marked as failing the test so that business personnel can handle the abnormality based on this mark.

[0099] 310. The testing equipment determines whether the test on the code to be tested is complete. If it is complete, proceed to step 311; otherwise, proceed to step 302.

[0100] Since the code under test includes multiple functionalities, and each functionality requires an OSD request to complete the test, the process for the verification device to determine whether the test of the code under test is complete can be as follows: Verify whether all functionalities of the code under test have been marked. If all functionalities are marked, it means that the test of the code under test is complete, and proceed to step 311. If there are still functionalities that have not been marked, it means that the test of the code under test is not complete, and proceed to step 302 to continue with subsequent tests.

[0101] 311. Compile the annotations for each functional point in the code to be tested, generate a test report, and end the current process.

[0102] After all tests on the code to be tested are completed, in order to enable business personnel to have a more intuitive understanding of the test results, the annotations of each functional point in the code to be tested are compiled to form a test report.

[0103] 312. Issue an exception message for the OSD request.

[0104] If it's detected that the OSD request lacks a corresponding functionality in the test code of the OSD under test, two types of exceptions may occur: First, the OSD request is an erroneous request. Second, the test code may have omitted the functionality corresponding to the OSD request. The alert for the first type of exception allows business personnel to promptly replace the OSD request with a usable one. The alert for the second type of exception allows business personnel to promptly confirm whether the corresponding functionality of the OSD request has been omitted from the code.

[0105] For a detailed explanation of the code testing method for the screen menu-based adjustment method provided in this embodiment of the invention, please refer to [link to relevant documentation]. Figures 1-2 Detailed explanations of the corresponding system implementation examples will not be repeated here.

[0106] Furthermore, according to the above embodiments, another embodiment of the present invention also provides a computer-readable storage medium, the storage medium including a stored program, wherein the program controls the device where the storage medium is located to execute [the program]. Figures 3-4 The code testing method for the aforementioned screen menu-based adjustment method.

[0107] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0108] It is understood that the relevant features in the above methods and apparatus can be referenced interchangeably. Furthermore, the terms "first," "second," etc., in the above embodiments are used to distinguish between embodiments and do not represent the superiority or inferiority of any particular embodiment.

[0109] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0110] The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used in conjunction with the teachings herein. The required structure for constructing such systems is apparent from the above description. Furthermore, this invention is not directed to any particular programming language. It should be understood that the contents of the invention described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing the best mode of implementation of the invention.

[0111] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0112] Furthermore, those skilled in the art will understand that although some embodiments described herein include certain features but not others included in other embodiments, combinations of features from different embodiments are intended to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0113] The various component embodiments of the present invention can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some or all of the components in the method, apparatus, and framework for operating the deep neural network model according to embodiments of the present invention. The present invention can also be implemented as a device or apparatus program (e.g., a computer program and computer program product) for performing part or all of the methods described herein. Such programs implementing the present invention can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0114] It should be noted that the above embodiments are illustrative of the invention and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

Claims

1. A code testing system with a screen menu-based adjustment method, characterized in that, The system includes: The testing platform is used to preset multiple OSD request test cases; deploy the test code of the OSD to be tested, which includes multiple functional points; when starting the test, OSD requests corresponding to each OSD request test case are initiated sequentially; after listening to the OSD request, it checks whether the OSD request has a corresponding functional point in the test code of the OSD to be tested. If the corresponding functional point exists, it checks whether the screen menu display storage device includes OSD display content corresponding to the OSD request. If it does, OSD data is generated in response to the OSD request; if it does not, a prompt is issued indicating that OSD display content is missing from the screen menu display storage device. This prompt is used to remind business personnel to confirm whether the code corresponding to the OSD request has been omitted. If the corresponding functional point does not exist, an exception prompt is issued for the OSD request. This exception prompt is used to remind business personnel to confirm whether the code corresponding to the OSD request has been omitted. The OSD request corresponds to the functional point of the test code, and the OSD is adjusted via a screen menu. A format conversion device for converting the OSD data format into a target format required by the display device; The display device is used to perform a display corresponding to the OSD data; The system further includes: a testing device, used to mark the function point corresponding to the OSD request in the code under test as having passed the test when the display of the display device matches the OSD request; and to mark the function point corresponding to the OSD request in the code under test as having failed the test when the display of the display device does not match the OSD request. The test platform includes: a generation unit, configured to extract OSD display content corresponding to the OSD request from the screen menu display storage device, and determine OSD display parameters of the OSD display content based on the OSD request, wherein the OSD display content and OSD display parameters constitute the OSD data; the OSD request carries OSD type requirements and OSD display requirements, the display content is determined based on the OSD type requirements, the OSD display parameters are determined based on the OSD display requirements, and the OSD display parameters are used to control the display mode of the OSD display content on the display image of the display device, the display mode including display size, display position, and display resolution.

2. The system according to claim 1, characterized in that, The display device is specifically used to overlay the OSD display content onto a display image based on the OSD display parameters, wherein the display image is the image currently displayed by the display device.

3. The system according to claim 1, characterized in that, The testing platform includes: The deployment unit is used to compile the code to be tested, generate an executable file for OSD code testing, and deploy the executable file.

4. The system according to claim 1, characterized in that, The testing equipment is also used to, when determining that the test for the code to be tested is completed, statistically analyze the annotations of each functional point in the code to be tested and generate a test report.

5. A code testing method for a screen menu-based adjustment mode, characterized in that, The method includes: When the test platform starts testing, it sequentially initiates OSD requests corresponding to each OSD request test case. After listening to an OSD request, it checks whether the OSD request has a corresponding functional point in the test code of the OSD to be tested. If the corresponding functional point exists, it checks whether the screen menu display storage device includes OSD display content corresponding to the OSD request. If it does, it generates OSD data in response to the OSD request. If it does not, it issues a prompt indicating that the screen menu display storage device lacks OSD display content. This prompt is used to remind business personnel to confirm whether the code corresponding to the OSD request has been omitted. If the corresponding functional point does not exist, it issues an exception prompt for the OSD request. This exception prompt is used to remind business personnel to confirm whether the code corresponding to the OSD request has been omitted. The test code includes multiple functional points. The test platform presets multiple OSD request test cases and deploys the test code of the OSD to be tested. The OSD request corresponds to the functional point of the test code, and the OSD is adjusted via a screen menu. The format conversion device converts the OSD data format into the target format required by the display device; The display device performs a display corresponding to the OSD data; When the testing equipment verifies that the display of the display device matches the OSD request, it marks that the function point corresponding to the OSD request in the code under test has passed the test. When the testing equipment verifies that the display of the display device does not match the OSD request, it marks that the function point corresponding to the OSD request in the code under test has failed the test. Responding to an OSD request to generate OSD data includes: the test platform extracting OSD display content corresponding to the OSD request from the screen menu display storage device, and determining OSD display parameters of the OSD display content based on the OSD request, wherein the OSD display content and OSD display parameters constitute the OSD data; the OSD request carries OSD type requirements and OSD display requirements, the display content is determined based on the OSD type requirements, the OSD display parameters are determined based on the OSD display requirements, and the OSD display parameters are used to control the display mode of the OSD display content on the display image of the display device, the display mode including display size, display position, and display resolution.

6. A computer-readable storage medium, characterized in that, The storage medium includes a stored program, wherein, when the program is running, it controls the device where the storage medium is located to execute the code testing method of the screen menu adjustment method as described in claim 5.

Images