9 results about "Software Problem" patented technology

Embodiments described herein provide a multi-stage rating and re-ranking pipeline for selecting SWE agents for an input issue description. Specifically, a meta-policy may be selected among available agent policies corresponding to a pool of available SWE agents which maximizes the cumulative reward along the trajectory of states (such as status of a file) and actions taken at a series of time steps, and a context of relevant repository information and issue descriptions. By dynamically choosing the most suitable agent policy for each context, the selection pipeline maximizes the expected cumulative reward across all possible contexts. In this way, software issue resolve rate is improved.

The application provides a software quality checking method and related products, wherein the method comprises the following steps: generating a checking report of a first software, the checking report comprising a first problem; and matching the first problem with a plurality of problems in a database, wherein the database comprises the plurality of problems and a confirmation result of each problem. In a case where the first problem matches any one of the plurality of problems, the confirmation result of the first problem is determined as the confirmation result of the matched problem; and in a case where the first problem does not match any one of the plurality of problems, the first problem is presented to a user for confirmation of a software problem, so as to determine whether the first problem is a problem in the first software. The method can reduce the workload of the user.

The invention provides a software problem processing method and system, electronic equipment and a storage medium, and relates to the technical field of vehicles, the method comprises the following steps: obtaining a problem description text of a software problem; extracting target key information from the question description text; determining a target prompt template matched with the question description text based on the target key information; wherein the target prompt template is a pre-created cross-vehicle type and cross-application prompt template; performing semantic enhancement on the target key information according to the target prompt template to generate target prompt information; and determining a problem diagnosis result according to the target prompt information through a preset large language model. According to the method, the accuracy and the high efficiency of the diagnosis of the vehicle-mounted software problem can be well realized.

The application discloses a method for locating software problem source code position through a log, and electronic equipment, comprising the following steps: acquiring a log output point of the target software, creating an index record for the log output point, detecting source code position information of each log output point, analyzing log content of each log output point based on the source code position information, extracting and generating feature values corresponding to the log content, constructing a log index library, receiving an actual running log, extracting feature values of the log, and performing matching in the log index library to determine the source code position corresponding to the log output point, and locating to a specific position of the source code according to a matching result. The application is beneficial to improving code performance and readability, does not depend on code position information output in the log, reduces requirements on the log format, enhances code readability, improves the integrity of the log by scanning the code and providing suggestions for improving the log, and the like.

The invention relates to the technical field of software development, in particular to a positioning method, a program product, a medium and equipment. The method provided by the invention comprises the following steps: acquiring a plurality of codes causing software problems and a code development sequence, and generating a submission record set; obtaining an intermediate code in the submission record set based on the successive development order; executing a test operation to test whether a software problem is caused when the intermediate code is changed; if yes, the codes, earlier than the intermediate codes in development order, in the multiple codes serve as a new submission record set; if not, taking the codes with the development order later than that of the intermediate codes in the plurality of codes as a new submission record set; and obtaining an intermediate code in the new submission record set and executing the same judgment operation until only one code is left in the new submission record set. And the code change which causes the software problem at the earliest can be quickly positioned.

The application discloses a test-oriented software quality evaluation method and device, which is used for rapid, automatic and multiple quantitative evaluation of a quality state of a software or system under test in a software test process. The method and device are used in the software test process, and only test data such as software problem scale can drive the evaluation model to automatically operate, so that the cost of carrying out a software quality evaluation activity in the software test process can be reduced, and the efficiency and feasibility of the software quality evaluation can be improved. The extended comprehensive evaluation set vector used can be customized and adjusted by a user, so that flexibility of the evaluation model is ensured.

The present disclosure provides techniques for improving software development. For software, which can be a user interface or functionality accessed through a user interface, values for both subjective and objective attributes are obtained. Values for subjective attributes can be obtained using techniques such as user surveys. Objective attributes can be automatically captured as a user interacts with a user interface or otherwise during software execution. Objective attributes measure aspects of user interaction with a user interface, such as a number of clicks recorded during an interaction or a duration of the interaction, or information regarding software execution, such as resource use or response time. The values for the subjective and objective attributes are analyzed together, a multi-modal analysis, to obtain a result, such as a clustering result. The clustering result can provide insights into what software issues may exist that are not captured by separately analyzing subjective and objective attributes.

Disclosed in the present invention are a method for locating a source code location of a software issue by means of a log, and an electronic device. The method comprises: acquiring log output points of target software, and creating index records for the log output points; detecting source code location information of each log output point, analyzing the log content of each log output point on the basis of the source code location information, and extracting and generating a feature value corresponding to the log content; constructing a log index database; and receiving an actual running log, extracting a feature value of the log, performing matching in the log index database to determine source code locations corresponding to the log output points, and locating the specific location of a source code on the basis of a matching result. The present invention can improve the code performance and readability, does not depend on code location information outputted in a log, reduces requirements for a log format, enhances code readability, improves the integrity of the log by scanning the code and providing suggestions for perfecting the log.

This invention relates to the field of software testing technology, and proposes a software bug-planting method and system based on software requirements. The method includes the following steps: analyzing software requirements to determine software requirement characteristics and their characteristic states; determining combinations of characteristic states for multiple software requirement characteristics; identifying valid characteristic state combinations to generate identified characteristic state combinations, and determining the software output of the identified characteristic state combinations; constructing software errors for the identified characteristic state combinations based on the software output; and using the software errors to bug-plant the source program to generate bug-planted software. This invention can assess the software test coverage of software requirements based on software requirements, and simultaneously assess the ability of software testing to discover software problems using the bug-planted source program as the implementation carrier. Therefore, it can simultaneously assess and accept the two core objectives of software testing, greatly improving the effectiveness and sufficiency of software test acceptance.