Processor operation scene verification method based on unified verification method verification platform
By optimizing processor test cases and generating, filtering, and modifying test request packets, the problem of poor processor flexibility in verification under different operating scenarios is solved, achieving efficient verification and resource conservation.
Patent Information
- Application Number
- CN202510869653.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-26
- Publication Date
- 2025-10-31
AI Technical Summary
The processor has poor flexibility in verification under different operating scenarios, and existing technologies result in low verification efficiency and waste of server resources.
By receiving initial test cases, test request packets are generated, filtered, and modified using preset test case optimization strategies to form optimized test cases suitable for different operating scenarios, driving the processor to perform tests and comparing them with expected results.
It improves the flexibility and efficiency of processor verification in different operating scenarios, reduces the number of initial test cases, and saves server resources.
Smart Images
Figure CN120872702A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of integrated circuit verification technology, and in particular to a processor operation scenario verification method, apparatus, electronic device and readable storage medium based on a unified verification method verification platform. Background Technology
[0002] Processors support a complete instruction set, and their functionality is complex and applicable to numerous scenarios. In verification platforms based on the Universal Verification Methodology (UVM), during the processor verification process, a test case often focuses on one or more stresses.
[0003] The CPU core operates in a complex and diverse range of scenarios. Test cases used to verify the processor in one scenario may not be applicable in another scenario, resulting in poor flexibility in verifying the processor in different operating scenarios. Summary of the Invention
[0004] In view of this, embodiments of this application provide a processor runtime scenario verification method, apparatus, electronic device, and readable storage medium based on a unified verification method verification platform, which facilitates improved flexibility in verifying processors for different runtime scenarios.
[0005] In a first aspect, embodiments of this application provide a processor runtime scenario verification method based on a unified verification method verification platform, comprising: receiving initial test cases for testing the runtime scenario of the processor to be verified; optimizing the initial test cases according to a preset test case optimization strategy to obtain optimized test cases; performing runtime scenario testing on the processor to be verified according to the optimized test cases to obtain test results; and comparing the test results with expected results to verify the runtime scenario of the processor to be verified.
[0006] According to a specific implementation of an embodiment of this application, optimizing the initial test cases according to a preset test case optimization strategy to obtain optimized test cases includes: generating new test cases according to a test case generation strategy in the preset test case optimization strategy; and inserting the new test cases into the test request packet sequence of the initial test cases to form optimized test cases.
[0007] According to a specific implementation of an embodiment of this application, the test case generation strategy includes the type of test cases to be generated; the step of generating new test cases according to the test case generation strategy in the preset test case optimization strategy includes: generating new test cases consistent with the specified test case type according to the specified test case type in the preset test case optimization strategy.
[0008] According to a specific implementation of an embodiment of this application, optimizing the initial test cases according to a preset test case optimization strategy to obtain optimized test cases includes: filtering the test request packets of the initial test cases according to a test request packet filtering strategy in the preset test case optimization strategy to obtain test cases that meet the current test requirements.
[0009] According to a specific implementation of an embodiment of this application, the test request packet filtering strategy includes filtering the type of test request packets and / or filtering the number of test request packets; the step of filtering the test request packets of the initial test cases according to the test request packet filtering strategy in the preset test case optimization strategy to obtain test cases that meet the current test requirements includes: filtering the test request packets of the initial test cases according to the type of test request packets and / or the number of test request packets to be filtered in the preset test case optimization strategy to obtain test cases that meet the current test requirements.
[0010] According to a specific implementation of an embodiment of this application, optimizing the initial test cases according to a preset test case optimization strategy to obtain optimized test cases includes: modifying the attributes of the test request packet of the initial test cases according to the attribute modification strategy in the preset test case optimization strategy, so as to optimize the initial test cases and obtain optimized test cases.
[0011] Secondly, embodiments of this application provide a verification platform based on a unified verification method, comprising: an optimization module, configured to receive initial test cases for testing the runtime scenarios of the processor to be verified; optimize the initial test cases according to a preset test case optimization strategy to obtain optimized test cases; a driving module, configured to drive the optimized test cases to the input interface of the processor to be verified, so as to perform runtime scenario testing on the processor to be verified according to the optimized test cases and obtain test results; and a comparison module, configured to compare the test results with expected results to perform runtime scenario verification on the processor to be verified.
[0012] According to a specific implementation of an embodiment of this application, the optimization module includes a generator; the generator is used to: generate new test cases according to a test case generation strategy in a preset test case optimization strategy; and insert the new test cases into the test request packet sequence of the initial test cases to form optimized test cases.
[0013] According to a specific implementation of an embodiment of this application, the test case generation strategy includes the type of test cases to be generated; the generator is specifically used to: generate new test cases consistent with the specified test case type according to the specified test case type in the preset test case optimization strategy.
[0014] According to a specific implementation of an embodiment of this application, the optimization module includes a filter; the filter is used to: filter the test request packets of the initial test cases according to the test request packet filtering strategy in the preset test case optimization strategy, so as to obtain test cases that meet the current test requirements.
[0015] According to a specific implementation of an embodiment of this application, the test request packet filtering strategy includes filtering the type of test request packets and / or filtering the number of test request packets; the filter is specifically used to: filter the test request packets of the initial test cases according to the type of test request packets and / or the number of test request packets in the preset test case optimization strategy, so as to obtain test cases that meet the current test requirements.
[0016] According to a specific implementation of an embodiment of this application, the optimization module includes a modifier; the modifier is used to: modify the attributes of the test request package of the initial test case according to the attribute modification strategy in the preset test case optimization strategy, so as to optimize the initial test case and obtain the optimized test case.
[0017] Thirdly, embodiments of this application provide an electronic device, the electronic device comprising: a processor and a memory, wherein the memory is used to store executable program code; the processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, for executing the processor running scenario verification method based on the unified verification method verification platform described in any of the foregoing implementations.
[0018] Fourthly, embodiments of this application provide a computer-readable storage medium storing one or more programs, which can be executed by one or more processors to implement the processor runtime scenario verification method based on a unified verification method verification platform as described in any of the foregoing implementations.
[0019] This embodiment of a processor runtime scenario verification method, apparatus, electronic device, and readable storage medium based on a unified verification method verification platform receives initial test cases for testing the runtime scenarios of the processor to be verified. According to a preset test case optimization strategy, the initial test cases are optimized to obtain optimized test cases. Then, the processor to be verified is tested in the runtime scenarios using the optimized test cases to obtain test results. Finally, the test results are compared with the expected results to verify the runtime scenarios of the processor. Because the initial test cases are optimized according to the preset test case optimization strategy to obtain optimized test cases, test cases suitable for different runtime scenarios can be obtained by optimizing the initial test cases. That is, different runtime scenarios can be optimized to obtain corresponding test cases, thereby improving the flexibility of verifying the processor in different runtime scenarios. Attached Figure Description
[0020] To more clearly illustrate the technical solutions in the embodiments of this application 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 only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 A flowchart illustrating a processor runtime scenario verification method based on a unified verification method verification platform, provided as an embodiment of this application; Figure 2 This is a structural diagram of a verification platform based on a unified verification method in one embodiment of this application; Figure 3 This is a structural diagram of a verification platform based on a unified verification method in a specific embodiment of this application; Figure 4 for Figure 3 The flowchart of the optimization module in a specific embodiment optimizes the initial test cases; Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0022] The embodiments of this application will now be described in detail with reference to the accompanying drawings. It should be understood that the described embodiments are merely some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0023] To enable those skilled in the art to better understand the technical concept, implementation scheme and beneficial effects of the embodiments of this application, detailed descriptions are provided below through specific embodiments.
[0024] Figure 1 This is a flowchart illustrating a processor runtime scenario verification method based on a unified verification method verification platform, as provided in an embodiment of this application. Figure 1 As shown in this embodiment, the processor runtime scenario verification method is based on a unified verification method verification platform.
[0025] The Universal Verification Methodology (UVM) is a widely used hardware verification method in the field of electronic design automation (EDA). It defines a unified set of classes and interfaces, as well as rules for building verification platforms, aiming to improve verification efficiency and quality.
[0026] The unified verification methodology verification platform in this embodiment can verify the processor's operating scenarios.
[0027] The processor runtime scenario verification method based on the unified verification method verification platform in this embodiment may include: S101. Receive initial test cases for testing the operating scenarios of the processor to be verified.
[0028] Processor operating scenarios can include low-temperature operating scenarios, high-temperature operating scenarios, stress operating scenarios, and so on.
[0029] Test cases are test plans and methods developed to test a test target, used to verify whether the test target meets specific requirements. In this embodiment, test cases can also be called test stimuli.
[0030] In practical applications, test cases can be sent in the form of test packet request sequences.
[0031] S102. Optimize the initial test cases according to the preset test case optimization strategy to obtain optimized test cases.
[0032] It is understood that the test case optimization strategy in this embodiment can be determined based on the verification requirements of verifying the processor to be verified in a specific scenario.
[0033] The optimized test cases can meet the requirements of the processor to be verified for runtime scenario testing.
[0034] The preset test case optimization strategy in this embodiment can be configured according to the test requirements of the processor running scenario to be verified.
[0035] S103. Based on the optimized test cases, perform runtime scenario tests on the processor to be verified and obtain the test results.
[0036] The optimized test cases are provided to the processor to be verified, and the processor is subjected to runtime scenario testing to obtain the corresponding test results.
[0037] S104. Compare the test results with the expected results to verify the processor to be verified by running the scenario.
[0038] The expected result of this embodiment is to provide optimized test cases to a reference model, which is a model that mimics the processor to be verified and has the same functionality as the processor to be verified.
[0039] Based on the optimized test cases, the corresponding results, i.e., the expected results, are obtained from the reference model.
[0040] By comparing the obtained test results with the expected results, the processor to be verified can be tested in a running scenario, that is, to determine whether the processor to be verified can work normally.
[0041] Specifically, when the test results are consistent with the expected results, the processor under test can work normally; when the test results are inconsistent with the expected results, the processor under test cannot work normally.
[0042] In this embodiment, initial test cases for testing the operating scenarios of the processor to be verified are received. Based on a preset test case optimization strategy, the initial test cases are optimized to obtain optimized test cases. Then, the processor to be verified is tested against the operating scenarios using the optimized test cases to obtain test results. Finally, the test results are compared with the expected results to verify the processor's operating scenarios. Because the initial test cases are optimized according to the preset test case optimization strategy, optimized test cases can be obtained based on different operating scenarios of the processor. That is, different operating scenarios can be optimized to obtain corresponding test cases, thereby improving the flexibility of verifying the processor in different operating scenarios. Furthermore, it can improve the verification efficiency of verifying the processor in different operating scenarios, reduce the number of initial test cases, save server resources used in daily regression testing, and avoid the problem in existing technologies where multiple test cases focusing on different directions of pressure are often used to ensure that test cases can comprehensively cover multiple scenarios of the processor, resulting in excessive server resource consumption.
[0043] In one embodiment of optimizing initial test cases, step S102, which optimizes the initial test cases according to a preset test case optimization strategy to obtain optimized test cases, may include: S102a. Generate new test cases according to the test case generation strategy in the preset test case optimization strategy.
[0044] In this embodiment, new test cases are generated according to the test case generation strategy.
[0045] S102b: Insert the new test cases into the test request packet sequence of the initial test cases to form optimized test cases.
[0046] New test cases can be inserted after the test request packet sequence of the initial test cases to form optimized test cases, or they can be inserted in the middle of the initial test cases. For example, if the initial test request packet sequence is (a0, a1, a2, a3...), the new test case is (b0, b1, b2...), and the optimized test case can be (a0, a1, a2, a3, b0, b1, b2, b3, ...) or (a0, a1, b0, a2, b1, a3, b2, b3, ...).
[0047] In this embodiment, new test cases are inserted into the test request packet sequence of the initial test cases to form optimized test cases, increasing the randomness and richness of the test cases, thereby speeding up the verification process.
[0048] In one embodiment, the test case generation strategy may include the type of test cases to be generated. Correspondingly, the step S102a of generating new test cases according to the test case generation strategy in the preset test case optimization strategy may include: A1. Generate new test cases that are consistent with the specified test case type in the preset test case optimization strategy.
[0049] The specified test case type can be a different type than the initial test case type.
[0050] In another embodiment of optimizing the initial test cases, step S102, which optimizes the initial test cases according to a preset test case optimization strategy to obtain optimized test cases, may include: S102c. According to the test request packet filtering strategy in the preset test case optimization strategy, filter the test request packets of the initial test cases to obtain test cases that meet the current test requirements.
[0051] When performing runtime scenario testing on the processor to be verified, if the initial test cases contain a large number of test request package types and / or a large number of test request packages, the existing technology requires deleting the corresponding sequence modules in the verification platform to reduce the types of test cases and thus the types of test request packages, and / or modifying the sequence modules to reduce the number of test request packages provided by the sequence modules. This results in low efficiency in performing runtime scenario testing on the processor to be verified. To solve this problem, in a specific example, the test request package filtering strategy may include filtering the types of test request packages and / or filtering the number of test request packages.
[0052] In this embodiment, step S102c, which filters the test request packets of the initial test cases according to the test request packet filtering strategy in the preset test case optimization strategy to obtain test cases that meet the current test requirements, may include: Based on the type and / or number of test request packets filtered in the preset test case optimization strategy, the test request packets of the initial test cases are filtered to obtain test cases that meet the current test requirements.
[0053] For example, the initial test request packet sequence (a0, a1, a2, a3, b0, b1, b2, b3…) becomes the filtered test request packet sequence (a0, a1, a3, b0, b2, b3…), which means that a2 and b1 are filtered out to form test cases that meet the current test requirements.
[0054] The verification method in this embodiment can support the requirements of the processor to be verified for the test request package of the test case at different stages of project development, such as filtering some test request packages that are not yet supported in the early stage of project development.
[0055] In another embodiment of optimizing the initial test cases, step S102, which optimizes the initial test cases according to a preset test case optimization strategy to obtain optimized test cases, may include: S102d. Based on the attribute modification strategy in the preset test case optimization strategy, modify the attributes of the test request packet of the initial test case to optimize the initial test case and obtain the optimized test case. The attributes of the test request packet may include the interface name and / or information about each request domain, etc.
[0056] Modifying request domain information can increase the stress on one or more aspects of the processor being verified, enriching the verification scenarios, while avoiding frequent modifications to the sequence modules in the verification platform and increasing environmental adaptability. For example, if the focus is on verifying the storage side of the processor, the address information in the test request packet can be modified to create a specific high stress level without modifying all sequence modules in the verification platform.
[0057] In this embodiment, modifying the attributes of the test request package of the initial test case can reduce the complexity of the test case. For example, modifying the request domain of some unreasonable test request packages can reduce the complexity of the test case.
[0058] In specific implementation, the attribute modification strategy may include modifying attribute values and / or deleting attribute values; correspondingly, in S102d, modifying the attributes of the test request package of the initial test case according to the preset attribute modification strategy in the configuration information may include: Modify the attribute values of the test request package of the initial test case according to the modified attribute values in the preset test case optimization strategy; and / or delete the attribute values of the test request package of the initial test case according to the deleted attribute values in the preset test case optimization strategy.
[0059] It is understood that the initial test cases can be optimized sequentially according to the test case generation strategy, test request packet filtering strategy, and attribute modification strategy in the above embodiments.
[0060] Figure 2 This is a schematic diagram of the structure of a verification platform based on a unified verification method provided in an embodiment of this application, as shown below. Figure 2 As shown, the processor runtime scenario verification device based on the unified verification method verification platform in this embodiment includes: an optimization module 11, used to receive initial test cases for testing the runtime scenario of the processor to be verified; optimize the initial test cases according to a preset test case optimization strategy to obtain optimized test cases; a driving module 12, used to drive the optimized test cases to the input interface of the processor to be verified, so as to perform runtime scenario testing on the processor to be verified according to the optimized test cases and obtain test results; and a comparison module 13, used to compare the test results with expected results to verify the runtime scenario of the processor to be verified.
[0061] The unified verification method verification platform in this embodiment can be used to execute... Figure 1 The technical solutions of the method embodiments shown are similar in principle and in effect, and will not be described again here.
[0062] This embodiment's unified verification method-based verification platform receives initial test cases for testing the operating scenarios of the processor to be verified. Based on a preset test case optimization strategy, the initial test cases are optimized to obtain optimized test cases. Then, based on the optimized test cases, the processor to be verified is tested in the operating scenarios to obtain test results. Finally, the test results are compared with the expected results to verify the processor's operating scenarios. Because the initial test cases are optimized according to the preset test case optimization strategy, optimized test cases can be obtained based on different operating scenarios of the processor. That is, different operating scenarios can be optimized to obtain corresponding test cases, thereby improving the flexibility of verifying the processor in different operating scenarios. Furthermore, it can improve the verification efficiency of verifying the processor in different operating scenarios, reduce the number of initial test cases, save server resources used in daily regression testing, and avoid the problem in existing technologies where multiple test cases focusing on different directions of pressure are often used to ensure that test cases can comprehensively cover multiple scenarios of the processor, resulting in excessive server resource consumption.
[0063] As an optional implementation, the optimization module includes a generator; the generator is used to: generate new test cases according to the test case generation strategy in the preset test case optimization strategy; and insert the new test cases into the test request packet sequence of the initial test cases to form optimized test cases.
[0064] As an optional implementation, the test case generation strategy includes the type of test cases to be generated; the generator is specifically used to: generate new test cases consistent with the specified test case type according to the specified test case type in the preset test case optimization strategy.
[0065] As an optional implementation, the optimization module includes a filter; the filter is used to: filter the test request packets of the initial test cases according to the test request packet filtering strategy in the preset test case optimization strategy, so as to obtain test cases that meet the current test requirements.
[0066] As an optional implementation, the test request packet filtering strategy includes filtering the type of test request packets and / or filtering the number of test request packets; the filter is specifically used to: filter the test request packets of the initial test cases according to the type of test request packets and / or the number of test request packets in the preset test case optimization strategy, so as to obtain test cases that meet the current test requirements.
[0067] As an optional implementation, the optimization module includes a modifier; the modifier is used to modify the attributes of the test request package of the initial test case according to the attribute modification strategy in the preset test case optimization strategy, so as to optimize the initial test case and obtain the optimized test case.
[0068] The apparatus described in the above embodiments can be used to execute the technical solutions of the above method embodiments. The implementation principle and technical effects are similar, and will not be repeated here.
[0069] It can be understood that, in some examples, the optimization module may include at least one of a producer, a filter, and a modifier.
[0070] The following detailed description of the solution in this application is based on a specific embodiment.
[0071] The verification platform based on the unified verification method can include a connection module, an optimization module, a driver module, and a comparison module.
[0072] like Figure 3 In the verification platform based on the unified verification method shown in the embodiment, the sequencer module is a specific implementation of the connection module, and the scoreboard is a specific implementation of the comparison module.
[0073] like Figure 3 The verification platform based on the unified verification method in the embodiment shown includes: a sequencer module, an optimization agent module, a driver module, a first monitoring module (monitor1), a second monitoring module (monitor2), a reference model, and a scoreboard.
[0074] The Sequencer sends the test cases generated by the sequence module (sequence) to the modify agent. The test cases optimized by the modify agent are then sent to the driver.
[0075] monitor1 monitors the input interface of the device under test (DUT), sends the optimized test cases to the reference model, and thus obtains the expected results.
[0076] Monitor2 monitors the test results of the processor to be verified and sends them to the scoreboard.
[0077] The scoreboard performs runtime scenario verification on the processor to be verified based on the test results and expected results.
[0078] Specifically, in this embodiment, `modify_agent` includes a sequence generator, a filter, and a modifier. The sequence generator can generate new test cases, i.e., new test request package sequences, and insert them into the test request package sequence of the initial test cases as needed; the filter can filter out test request packages that are not currently supported by the test; the modifier can modify the attributes of the test request packages according to the environment configuration, thereby changing the stimulus mode and test pressure.
[0079] like Figure 4 The optimization process of modify_agent for the initial test cases is as follows: 1. Determine whether a new test request packet sequence needs to be generated.
[0080] If generation is required, the sequence generator of modify_agent generates a sequence of test request packets and inserts it into the initial sequence of test request packets, then proceeds to step 2; if generation is not required, step 2 is executed directly.
[0081] The modify_agent can include multiple sequence generators to produce different stimulus sequences (also known as test cases or test request packet sequences), thereby enriching the stimulus patterns. In addition, it can reduce the number of test cases generated by sequences in the verification platform.
[0082] 2. Determine whether filtering is needed.
[0083] If filtering is required, the filter of modify_agent filters the sequence of received test request packets and then proceeds to step 3; if filtering is not required, step 3 is executed directly.
[0084] The filters in modify_agent can support the requirements of request sequences at different stages of project development, such as filtering some test request packets that are not yet supported in the early stages of project development.
[0085] 3. Determine whether it is necessary to modify the test request packet attributes.
[0086] If it is necessary to modify the test request packet attributes, the modifier in modify_agent modifies the attributes of the received test request packet sequence and sends the modified test request packet sequence to the driver module; if it is not necessary to modify the test request packet attributes, the test request packet sequence is sent directly to the driver module.
[0087] Modifiers in `modify_agent` can modify certain fields in the request packet to increase pressure on one or more aspects, enriching the verification scenario while avoiding frequent sequence modifications and increasing environmental adaptability. For example, to focus on verifying the storage side of the processor, `modify_agent` can modify the address information in the request packet to create specific high pressure. Since `modify_agent` can receive request packets from all sequences, this avoids modifying all sequences.
[0088] This embodiment of Mosidy_agent enriches the test incentives while reducing sequence (testcase) and regression server resources. In a project applying the above optimization process, the number of test cases was reduced by 2 / 3, and the daily regression submission resources were also reduced by 2 / 3.
[0089] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, as shown below. Figure 5 As shown, it may include a processor 61 and a memory 62, wherein the memory 62 is used to store executable program code; the processor 61 runs the program corresponding to the executable program code by reading the executable program code stored in the memory 62, and is used to execute any of the processor running scenario verification methods based on the unified verification method verification platform provided in the foregoing embodiments, so that it can also achieve the corresponding beneficial technical effects, which have been described in detail above and will not be repeated here.
[0090] The aforementioned electronic devices exist in various forms, including but not limited to: (1) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, have computing and processing capabilities, and generally also have mobile internet access capabilities. These terminals include: PDAs, MIDs, and UMPCs, such as iPads.
[0091] (2) Server: A device that provides computing services. The components of a server include a processor, hard disk, memory, system bus, etc. Servers are similar to general computer architectures, but because they need to provide highly reliable services, they have higher requirements in terms of processing power, stability, reliability, security, scalability, and manageability.
[0092] (3) Other electronic devices with data interaction functions.
[0093] Accordingly, embodiments of this application also provide a computer-readable storage medium storing one or more programs, which can be executed by one or more processors to implement any of the processor running scenario verification methods based on a unified verification method verification platform provided in the foregoing embodiments. Therefore, it can also achieve the corresponding technical effects, which have been described in detail above and will not be repeated here.
[0094] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0095] The various embodiments in this specification are described in a related manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.
[0096] In particular, the device embodiment is basically similar to the method embodiment, so the description is relatively simple. For relevant details, please refer to the description of the method embodiment.
[0097] For ease of description, the above apparatus is described by dividing it into various functional units / modules. Of course, in implementing this application, the functions of each unit / module can be implemented in one or more software and / or hardware.
[0098] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.
[0099] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A processor runtime scenario verification method based on a unified verification method verification platform, characterized in that, include: Receive initial test cases for testing the runtime scenarios of the processor to be verified; The initial test cases are optimized according to the preset test case optimization strategy to obtain optimized test cases; Based on the optimized test cases, the processor to be verified is subjected to runtime scenario testing to obtain test results; The test results are compared with the expected results to verify the processor under test in a runtime scenario.
2. The method according to claim 1, characterized in that, The step of optimizing the initial test cases according to a preset test case optimization strategy to obtain optimized test cases includes: Generate new test cases according to the test case generation strategy in the preset test case optimization strategy; The new test cases are inserted into the test request packet sequence of the initial test cases to form optimized test cases.
3. The method according to claim 2, characterized in that, The test case generation strategy includes the types of test cases to be generated; The step of generating new test cases according to the test case generation strategy in the preset test case optimization strategy includes: Based on the specified test case type in the preset test case optimization strategy, generate new test cases that are consistent with the specified test case type.
4. The method according to claim 1, characterized in that, The step of optimizing the initial test cases according to a preset test case optimization strategy to obtain optimized test cases includes: According to the test request packet filtering strategy in the preset test case optimization strategy, the test request packets of the initial test cases are filtered to obtain test cases that meet the current test requirements.
5. The method according to claim 4, characterized in that, The test request packet filtering strategy includes filtering the type of test request packets and / or filtering the number of test request packets; The step of filtering the test request packets of the initial test cases according to the test request packet filtering strategy in the preset test case optimization strategy to obtain test cases that meet the current test requirements includes: Based on the type and / or number of test request packets filtered in the preset test case optimization strategy, the test request packets of the initial test cases are filtered to obtain test cases that meet the current test requirements.
6. The method according to claim 1, characterized in that, The step of optimizing the initial test cases according to a preset test case optimization strategy to obtain optimized test cases includes: According to the attribute modification strategy in the preset test case optimization strategy, the attributes of the test request packet of the initial test case are modified to optimize the initial test case and obtain the optimized test case.
7. A verification platform based on a unified verification method, characterized in that, include: The optimization module is used to receive initial test cases for testing the runtime scenarios of the processor to be verified; The initial test cases are optimized according to the preset test case optimization strategy to obtain optimized test cases; The driver module is used to drive the optimized test cases to the input interface of the processor to be verified, so as to perform runtime scenario testing on the processor to be verified according to the optimized test cases and obtain test results. The comparison module is used to compare the test results with the expected results in order to verify the processor to be verified in the operating scenario.
8. The verification platform based on a unified verification method according to claim 7, characterized in that, The optimization module includes a generator; the generator is used for: Generate new test cases according to the test case generation strategy in the preset test case optimization strategy; The new test cases are inserted into the test request packet sequence of the initial test cases to form optimized test cases.
9. An electronic device, characterized in that, The electronic device includes a processor and a memory, wherein the memory is used to store executable program code; the processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, for executing the processor running scenario verification method based on the unified verification method verification platform as described in any one of claims 1-6.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the processor runtime scenario verification method based on the unified verification method verification platform as described in any one of claims 1-6.