Data processing method and device, electronic equipment and storage medium

Abstract

This invention provides a data processing method, apparatus, electronic device, and storage medium. The method includes: acquiring commit information for an external branch; then, based on file information in the commit information, acquiring external files from the external branch, corresponding development files from a preset development branch, and corresponding production files from a preset production environment; comparing the external files with the development files and production files respectively to generate content difference data and release difference data corresponding to the external branch; and using the file information in the commit information to acquire test requirement information corresponding to the external files, associating the test requirement information with the content difference data and release difference data to generate file difference data corresponding to the commit information. This simplifies the testing process, ensures the integrity of test data, and greatly improves the accuracy and efficiency of testing.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a data processing method, a data processing apparatus, an electronic device, and a computer-readable storage medium. Background Technology

[0002] In the development process of software products, a version-based development process is often adopted. After the developers confirm the requirements, they can first carry out project development in the development branch, and then periodically submit the content to be released to the pre-release environment. After the content to be released is pre-released, if the testers test it and find no errors, the content to be released can be put into the production environment for use.

[0003] Within the same release cycle, software product features are typically developed by multiple developers working on different development branches. Completed portions of the content can be submitted to the pre-release environment multiple times, out of order. Before releasing all the content to the pre-release environment, testers need to manually analyze the portions released by the developers. They then extract the corresponding files from the development and production branches, and test each file using appropriate methods to confirm that the content to be released has been correctly submitted. However, this method, which relies on testers manually analyzing and testing the development content and assessing whether it has been correctly submitted, is not only cumbersome in terms of file extraction and comparison, but also results in low accuracy and efficiency in testing the released content. Summary of the Invention

[0004] This invention provides a data processing method, apparatus, electronic device, and computer-readable storage medium to solve or partially solve the problems in the prior art where the testing process is cumbersome and inefficient due to reliance on manual analysis by testers and the need to externalize the content being tested.

[0005] This invention discloses a data processing method, the method comprising:

[0006] Obtain commit information for the external branch, the commit information including file information and operation information;

[0007] Based on the file information, retrieve the external files from the external branch, the corresponding development files from the preset development branch, and the corresponding production files from the preset production environment;

[0008] The externally released file is compared with the development file and the production file respectively to generate content difference data and release difference data corresponding to the externally released file;

[0009] Based on the operation information, obtain the test requirement information corresponding to the externally played file;

[0010] The test requirement information is associated with the content difference data and the release difference data to generate file difference data corresponding to the submission information.

[0011] Optionally, obtaining commit information for the external branch includes:

[0012] In response to a commit operation on the external branch, the commit information corresponding to the commit operation is extracted from the external branch.

[0013] Optionally, obtaining commit information for the external branch includes:

[0014] The corresponding commit information is extracted from the external branch at preset intervals.

[0015] Optionally, the file information includes a file name and a file path. The steps of obtaining the external file from the external branch, obtaining the corresponding development file from a preset development branch, and obtaining the corresponding production file from a preset production environment based on the file information include:

[0016] The file path is used to obtain the external file corresponding to the file name from the external branch, the development file corresponding to the file name from the preset development branch, and the production file corresponding to the file name from the preset production environment.

[0017] Optionally, comparing the externally released file with the development file and the production file respectively, and generating content difference data and release difference data corresponding to the externally released file, includes:

[0018] The external files of the same file type are compared with the development files to generate content difference data corresponding to the external files;

[0019] The external files of the same file type are compared with the production files to generate release difference data corresponding to the external files.

[0020] Optionally, the operation information includes an operation log, and the step of obtaining the test requirement information corresponding to the externally played file based on the operation information includes:

[0021] Obtain the test requirement information corresponding to the external file from the operation log.

[0022] Optionally, the operation information includes submitter information, the test requirement information includes a requirement number, a requirement topic, and tester information, and the step of associating the test requirement information with the content difference data and the release difference data to generate file difference data corresponding to the submission information includes:

[0023] Package the submitter information, the request number, the request topic, and the tester information to generate corresponding target association information;

[0024] The target association information, the content difference data, and the publication difference data are associated to generate file difference data corresponding to the submission information.

[0025] Optionally, the method further includes:

[0026] Create a data display interface corresponding to the file difference data, and display the file difference data in the data display interface.

[0027] Optionally, the data display interface includes data filtering controls, and the method further includes:

[0028] In response to a selection operation on the data filtering control, at least one filtering condition corresponding to the file difference data is determined;

[0029] The file differences that meet at least one of the filtering criteria are displayed on the data display interface.

[0030] This invention discloses a data processing apparatus, the apparatus comprising:

[0031] The commit information acquisition module is used to acquire commit information for external branches, including file information and operation information.

[0032] The file acquisition module is used to acquire external files from the external branch, corresponding development files from the preset development branch, and corresponding production files from the preset production environment based on the file information.

[0033] The file comparison module is used to compare the externally released file with the development file and the production file respectively, and generate content difference data and release difference data corresponding to the externally released file;

[0034] The test requirement information acquisition module is used to acquire test requirement information corresponding to the external file based on the operation information.

[0035] The file difference data generation module is used to associate the test requirement information with the content difference data and the release difference data to generate file difference data corresponding to the submission information.

[0036] Optionally, the submission information acquisition module is specifically used for:

[0037] In response to a commit operation on the external branch, the commit information corresponding to the commit operation is extracted from the external branch.

[0038] Optionally, the submission information acquisition module is specifically used for:

[0039] The corresponding commit information is extracted from the external branch at preset intervals.

[0040] Optionally, the file information includes the file name and file path, and the file acquisition module is specifically used for:

[0041] The file path is used to obtain the external file corresponding to the file name from the external branch, the development file corresponding to the file name from the preset development branch, and the production file corresponding to the file name from the preset production environment.

[0042] Optionally, the file comparison module is specifically used for:

[0043] The external files of the same file type are compared with the development files to generate content difference data corresponding to the external files;

[0044] The external files of the same file type are compared with the production files to generate release difference data corresponding to the external files.

[0045] Optionally, the operation information includes operation logs, and the test requirement information acquisition module is specifically used for:

[0046] Obtain the test requirement information corresponding to the external file from the operation log.

[0047] Optionally, the operation information includes the submitter's information, the test requirement information includes the requirement number, the requirement subject, and the tester's information, and the file difference data generation module is specifically used for:

[0048] Package the submitter information, the request number, the request topic, and the tester information to generate corresponding target association information;

[0049] The target association information, the content difference data, and the publication difference data are associated to generate file difference data corresponding to the submission information.

[0050] Optionally, the device further includes:

[0051] The data display interface creation module is used to create a data display interface corresponding to the file difference data, and to display the file difference data in the data display interface.

[0052] Optionally, the data display interface includes data filtering controls, and the device further includes:

[0053] A filter condition determination module is used to determine at least one filter condition corresponding to the file difference data in response to a selection operation on the data filter control.

[0054] The file difference data display module is used to display the file difference data that meets at least one filtering condition on the data display interface.

[0055] This invention also discloses an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0056] The memory is used to store computer programs;

[0057] When the processor executes a program stored in the memory, it implements the method described in the embodiments of the present invention.

[0058] This invention also discloses a computer-readable storage medium storing instructions that, when executed by one or more processors, cause the processors to perform the methods described in this invention.

[0059] The embodiments of the present invention have the following advantages:

[0060] In this embodiment of the invention, commit information for an external branch can be obtained. Then, based on the file information in the commit information, external files are obtained from the external branch, corresponding development files are obtained from a preset development branch, and corresponding production files are obtained from a preset production environment. Next, the external files are compared with the development files and production files respectively to generate content difference data and release difference data corresponding to the external branch. Furthermore, the file information in the commit information is used to obtain test requirement information corresponding to the external files. The test requirement information is then associated with the content difference data and release difference data to generate file difference data corresponding to the commit information. On one hand, commit information for an external branch is obtained, and the corresponding external files are automatically obtained based on the file information in the commit information. This system integrates external files, development documents, and production documents. This simplifies the document acquisition process, ensures the completeness of document comparison, and avoids omissions and false positives during manual inspection due to large amounts of submitted data. Furthermore, by comparing external files with development documents to generate content difference data, the accuracy of testing is improved. Comparing external files with production documents to generate release difference data enhances the match between external files and development requirements. Simultaneously, linking test requirement information with content difference data and release difference data generates document difference data, allowing for intuitive browsing of document difference data and rapid tracing and location of corresponding test requirement information, thus accelerating the product development and release schedule. Attached Figure Description

[0061] Figure 1 This is a flowchart of the steps of a data processing method provided in an embodiment of the present invention;

[0062] Figure 2 This is a flowchart of the steps for generating content difference data and publishing difference data provided in this embodiment of the invention;

[0063] Figure 3 This is a flowchart of the steps for generating file difference data provided in an embodiment of the present invention;

[0064] Figure 4 This is a structural block diagram of a data processing device provided in an embodiment of the present invention;

[0065] Figure 5 This is a block diagram of an electronic device provided in an embodiment of the present invention;

[0066] Figure 6 This is a schematic diagram of a computer-readable medium provided in an embodiment of the present invention. Detailed Implementation

[0067] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0068] At different stages of the product development cycle, developers can utilize branching development within version control systems to update or optimize product features. This updating or optimization process may involve the development of numerous different types of files, requiring independent, multi-threaded development by individual developers. Therefore, due to the large volume of development data in software products, branching development is typically employed. Development branches are created in advance, and work is then done within each branch based on development requirements. The completed files are then released to a pre-release environment for testing. If the testers confirm the released content is error-free, it can be merged with the main branch and then deployed to the production environment. This approach ensures normal operation while maintaining high-quality data. While this significantly reduces the risk of external release, the process of testing externally released content requires testers to extract corresponding file content from other branches based on the files submitted by developers to the pre-release environment. They then analyze the extracted content and select comparison tools to perform the comparisons. If developers submit too many files at once or testers have too long intervals between tests, the amount of test data can become excessive, requiring testers to manually extract too many files and use complex comparison tools. This can lead to missed detections and low testing efficiency. Furthermore, if the externally released content is inconsistent with the development branch or production environment, testers need to first determine the development requirements corresponding to the inconsistent parts before analyzing and confirming the inconsistencies. This analysis process is cumbersome and time-consuming.

[0069] Version control systems, in particular, are processes for recording, tracking, maintaining, and controlling changes to a series of products or systems resulting from partial improvements or modifications to the same product or system to meet different development needs. Technical personnel often use VCS (Version Control System). Version control systems (VCS) implement version management. Commonly used VCS tools include SVN (Subversion) and Git. Using a VCS tool not only displays the changes between the current and previous versions, but also allows the creation of multiple branches according to development needs, enabling work to be done on each branch. Branch development can include master, develop, feature, and release branches. Specifically, the master branch is the main branch, which can be merged from other branches, but cannot be directly modified within it. The release branch is the pre-release branch; during the release and testing phase, the code on the release branch is used as the basis for testing. The develop branch is the development branch, which maintains the latest completed code and bug-fixed code. When developing new features, feature branches can be created based on the develop branch. Users can use these branches to divide the overall product project into multiple parts and assign them to different developers according to their work content or development needs, ensuring that developers can work in an orderly and multi-threaded manner.

[0070] One of the core inventive points of this invention is its ability to acquire commit information for external branches, and then, based on the file information in the commit information, retrieve external files from the external branch, corresponding development files from a preset development branch, and corresponding production files from a preset production environment. Next, the external files are compared with the development and production files respectively, generating content difference data and release difference data corresponding to the external branch. Furthermore, the file information in the commit information is used to acquire test requirement information corresponding to the external files, and this test requirement information is associated with the content difference data and release difference data to generate file difference data corresponding to the commit information. On one hand, it acquires commit information for external branches, and automatically retrieves files based on the file information in the commit information. The corresponding external files, development files, and production files simplify the file acquisition process and ensure the completeness of file comparison during the comparison of external files and other files. This also avoids omissions and false positives during manual inspection due to the large amount of submitted data. On the other hand, by comparing external files with development files to generate content difference data, the accuracy of testing is improved. By comparing external files with production files to generate release difference data, the matching degree between external files and development requirements is improved. At the same time, the test requirement information is associated with content difference data and release difference data to generate file difference data. This allows for intuitive browsing of file difference data and quick tracing and locating of corresponding test requirement information, thus advancing the product development and release schedule.

[0071] Reference Figure 1 The diagram illustrates a flowchart of a data processing method provided in an embodiment of the present invention, which may specifically include the following steps:

[0072] Step 101: Obtain the commit information for the external branch, the commit information including file information and operation information;

[0073] In this embodiment of the invention, the external branch can be a branch created by relevant technical personnel using the branch development method, based on the develop branch, to store the development content submitted by each developer. Each developer can perform product development and other work based on the develop branch, and then periodically submit the completed content to the external branch so that the external content in the external branch is the latest version of the current period. The external content of the external branch is then released to the pre-release environment, and testers follow up and test the external content in the external branch. If the associated testers find that the external content is correct, the external content of the external branch can be put into the production environment for formal release.

[0074] Optionally, the commit information can be various information generated each time a developer performs a commit operation to an external branch. This information can include file information and operation information. File information can include file type, file path, etc., while operation information can include operation logs, committer information, etc.

[0075] In one embodiment of the present invention, a tracking tool, such as a hook, in version control tools can be used to monitor commit operations for external branches. Then, the information of each commit made by the developer in the external branch can be extracted. By using the tracking tool to obtain the commit information corresponding to each commit operation of the developer in a timely and effective manner, the problem of missed detection caused by excessive commit volume or too many commits can be avoided, thereby reducing the workload of testers and improving the efficiency of testing.

[0076] In another embodiment of the present invention, tools such as scanning scripts can be used to periodically retrieve commit information from external branches at preset intervals. Specifically, the preset interval can be a scanning cycle for periodically retrieving commit information, set in advance by relevant technical personnel when configuring the scanning script, such as 100ms, thereby achieving the timely and automatic acquisition of commit information from external files, reducing the workload of testers and saving labor costs.

[0077] Step 102: Obtain the external file from the external branch, the corresponding development file from the preset development branch, and the corresponding production file from the preset production environment according to the file information.

[0078] In this embodiment of the invention, after obtaining the commit information submitted by the developer to the external branch, the external file can be obtained from the external branch according to the file information, the corresponding development file can be obtained from the preset development branch, and the corresponding production file can be obtained from the preset production environment. Then, the external file, development file and production file are saved to the corresponding database respectively.

[0079] Optionally, the production environment refers to an environment that includes all the functions of the product and is officially provided to the outside world. The deployed branch can be the master branch (main branch), and the version in the production environment is the old version of the external branch in the same cycle version.

[0080] In practice, the file path can be used to locate the corresponding file location from the external branch, development branch, and production environment, respectively. Then, the external file corresponding to the file name can be obtained from the latest version of the external branch, the development file corresponding to the file name can be obtained from the latest version of the preset development branch, and the production file corresponding to the file name can be obtained from the old version of the preset production environment.

[0081] In one example of the present invention, during the process of obtaining the corresponding development file from a preset development branch or the corresponding production file from a preset production environment based on the file information, there are two situations: one is that a file corresponding to the file path and file name exists in the development branch or production environment, and the corresponding file is used as the development file or production file; the other is that a file corresponding to the file path and file name does not exist in the development branch or production environment, and an empty file corresponding to the development branch or production environment is generated, and then the empty file is used as the development file or production file.

[0082] As an example, we create a repository ① corresponding to the latest version in the development branch, a repository ② corresponding to the latest version in the external branch, and a repository ③ corresponding to the production environment. The version in the production environment corresponds to the old version in the external branch. Then, we use the tracking tool or scanning script in the version control tool to obtain the file path and file name of the file submitted by the developer to the external branch. Using the file path and file name, we obtain the development file, external file, and production file corresponding to the same file path and file name from repository ①, repository ②, and repository ③, respectively.

[0083] Step 103: Compare the external file with the development file and the production file respectively to generate content difference data and release difference data corresponding to the external file;

[0084] In this embodiment of the invention, external files with the same file path and file name can be compared with development files to generate content difference data corresponding to the external files. External files with the same file path and file name can also be compared with production files to generate release difference data corresponding to the external files.

[0085] Optionally, content discrepancy data can be data generated when there is inconsistency between the content of external files and development files, which can be used to evaluate the accuracy between the content committed to the external branch and the content of the development branch. Release discrepancy data can be data generated when there is inconsistency between the content of external files and production files, which can be used to evaluate the degree of matching between the content committed to the external branch and the development requirements of the current cycle version.

[0086] For example, refer to Figure 2This document illustrates a flowchart of the steps for generating content difference data and publishing difference data in an embodiment of the present invention. Three local repositories are created: Repository ①, Repository ②, and Repository ③. Repository ① corresponds to the latest version of the development branch, Repository ② corresponds to the latest version of the external branch, and Repository ③ corresponds to the older version in the production environment (and the older version of the external branch). Using a tracking tool or scanning script in a version control tool, file names, file paths, and operation logs are extracted from the external branch. Then, based on the extracted file names and file paths, it is determined whether files matching the file path and file name exist in Repository ①, Repository ②, and Repository ③. If not, an empty file is generated. If they exist, three files with the same file name (File_A, File_B, and File_C) are retrieved from the same file path. Next, the file type of File_B is obtained, and a comparison tool corresponding to the file type is used. The comparison tool compares File_A with File_B to generate content difference data diff_AB, and compares File_B with File_C to generate publishing difference data diff_BC. Finally, the content difference data diff_AB and the publishing difference data diff_BC are stored in the database.

[0087] In one example of the present invention, the file types of the externally played file and the development file can be obtained. Then, for the same file type, a file comparison tool corresponding to the file type is used to compare the externally played file and the development file to generate content difference data corresponding to the externally played file.

[0088] Specifically, in a complete version cycle, the files submitted by each developer can be code files, configuration files, and resource files. The file types corresponding to the submitted files can include .py files, .cpp files, .txt files, .excel files, .png files, .gim files, etc. Different file types correspond to different file comparison tools. For example, for .txt text files, text comparison tools such as svn diff and beyond compare can be used, or comparison tools can be developed using the difflib library in Python; for .excel chart files, Excel comparison tools can be used.

[0089] As an example, suppose the project being developed is for a Spring Festival event. This project requires product developers to configure the corresponding configuration tables, programmers to write the corresponding code, and graphic designers to design the Spring Festival images. During project development, the graphic designer submitted three Spring Festival event images (Image A, Image B, and Image C) to the development branch. However, when submitting to the external branch, the graphic designer submitted two Spring Festival event images (Image A and Image B1) and one Lantern Festival event image (Image D). Using an image comparison tool, Image A from the development branch is compared with Image A from the external branch. The comparison result ① shows that the images are identical; Image B from the development branch is compared with Image C from the external branch. The tester compares image B1 in the branch. Comparison result ② shows that image B is inconsistent with image B1, generating content difference data b. Comparison result ③ shows that image C exists only in the development branch and not in the external branch, generating content difference data c. Comparison result ④ shows that image D exists only in the external branch and not in the development branch, generating content difference data d. Then, the tester judges and confirms each of the content difference data b, c, and d. This allows for the rapid and automatic generation of content difference data, and the use of content difference data to evaluate whether the relevant technical personnel have accurately submitted the content from the development branch to the external branch, thereby saving manpower costs and improving the accuracy of testing.

[0090] In another example of the present invention, the file types of the externally played file and the production file can be obtained. Then, for the same file type, a file comparison tool corresponding to the file type is used to compare the externally played file and the production file to generate content difference data corresponding to the externally played file.

[0091] As an example, suppose the project being developed is for a Spring Festival event. The project actually requires two images for the Spring Festival event, image A and image B. However, the graphic designer submitted both images (image A and image B) to the development branch, and simultaneously modified image C in the old version to image C1. This modified image C1 was missed during development testing and was submitted to the external branch along with images A and B. At this point, the external branch contains images A, B, and C1. When the development branch and the external branch are automatically compared, the comparison result shows that the images in the development branch match the images in the external branch, and this is then submitted to the production environment. If directly... Directly deploying images A, B, and C1 from the external branch to the production environment could pose quality risks. Since the production environment contains various older versions of data, such as images A, B, and C from older versions of the project, an image comparison tool can be used to compare images A, B, and C1 one by one with their counterparts in the production environment during the deployment process. This generates release difference data c for image C1. Testers can then use this data to determine and confirm the content of the external branch, significantly reducing the quality risks associated with product release.

[0092] Step 104: Obtain the test requirement information corresponding to the external playback file based on the operation information;

[0093] In this embodiment of the invention, the operation information of the developer submitting to the external branch is first obtained, and then the test requirement information corresponding to the submission operation is tracked according to the operation information, which facilitates quick tracing and locating of the corresponding test requirement information and improves test quality.

[0094] Optionally, the operation information includes operation logs. First, the operation logs are parsed, and then the data interface provided by the project management software can be used to obtain the test requirement information corresponding to the external file from the parsed operation logs. This requirement information may include various details such as the requirement number, requirement topic, associated tester information, priority, progress, developers, development content, and submission content. Different project management software retrieves different test requirement information from the operation logs. Using the appropriate project management software, test requirement information used to correlate with content difference data and release difference data can be obtained from the requirement information, such as the requirement number, requirement topic, and associated tester information (tester name, email, contact number, etc.).

[0095] Step 105: Associate the test requirement information with the content difference data and the release difference data to generate file difference data corresponding to the submission information.

[0096] In this embodiment of the invention, after obtaining test requirement information from the operation log, the requirement number, requirement topic, associated tester information, content difference data, and release difference data of the test requirement information can be associated to generate file difference data corresponding to the submission information.

[0097] Optionally, the file difference data can include test requirement information, operation information, content difference data, and release difference data simultaneously. Testers associated with the file difference data can intuitively browse the data differences between the external files and the development and production files. They can also determine whether the file difference data meets the development requirements based on the requirement number and requirement topic, and provide information on the person responsible for submitting the external files, which facilitates timely feedback from testers to developers and advances the project progress.

[0098] In practical implementation, the operation information can include the submitter's information, such as the submitter's name, email, and contact number. The submitter's information, request number, request topic, and tester information can be packaged together to generate corresponding target association information. Then, the target association information, content difference data, and release difference data are associated to generate file difference data corresponding to the submitted information. This file difference data is stored in the database. By monitoring the developers' submissions to the external branch, the file difference data corresponding to the submissions can be aggregated and collected, ensuring that testers can quickly confirm the completeness and correctness of the external content. This improves testing accuracy and efficiency, and reduces the risk of external release.

[0099] As an example, refer to Figure 3 This document illustrates a flowchart of the steps for generating file difference data in an embodiment of the present invention. The steps involve using a version control tool's hook to retrieve commit information from an external branch, parsing the operation logs obtained from the commit information of the external branch, and then using the data query interface provided by the project management software to obtain the requirement number, requirement topic, associated tester information, and committer information corresponding to the operation logs. Target association information corresponding to the commit information is generated and stored in a database. After obtaining the file name and file path of the commit information using a version control tool, and determining the corresponding external file, development file, and production file based on the file name and file path, the external file is compared with the development file to generate content difference data. The external file is then compared with the production file to generate release difference data. Finally, the target association information stored in the database is associated with the content difference data and release difference data to generate file difference data.

[0100] Specifically, create a data display interface corresponding to the file difference data, such as building a website. The website provides a data display interface for visualizing the file difference data in the database, and displays the file difference data corresponding to the submitted information in the data display interface.

[0101] In one example of the present invention, the data display interface includes a data filtering control, which can determine at least one filtering condition corresponding to the file difference data in response to a selection operation on the data filtering control, and then display the file difference data that meets at least one filtering condition on the data display interface.

[0102] Optionally, the filtering criteria can be the cycle version, the name of the associated submitter, the submitter's email address, etc. Associated testers can view unconfirmed file difference data that meets at least one filtering criterion on the data display interface, and perform confirmation or cancellation operations on the file difference data by selecting the confirmation and cancellation confirmation buttons. At the same time, relevant interfaces are provided for external calls to confirm or cancel the confirmation of file difference data. Thus, the file difference data is clearly displayed through the website, which simplifies the testing process, greatly improves the inspection efficiency and inspection quality, and provides confirmation operations for each file difference data, effectively avoiding the problem of missing the confirmation of file difference data.

[0103] In another example of the present invention, the data display interface corresponding to the file difference data may also include data viewing links for jumping to content difference data and publication difference data. Testers associated with the file difference data can browse the content difference data and publication difference data through the data viewing links. At the same time, corresponding interfaces are provided to view the confirmation progress of file difference data for each tester or the overall project, which solves the problem of not being able to monitor the project progress. Each developer and tester can obtain the confirmation progress of the file difference data submitted in the current cycle version through the corresponding interfaces, summarize the overall progress of the project, promptly enter the next work stage, or advance the current work stage of the project.

[0104] In another example of the present invention, the data display interface corresponding to the file difference data may also include a data reminder button. The data reminder button can be used to remind the associated testers to process the unconfirmed file difference data. It provides a corresponding interface and button, and works with communication software or email to automatically or manually remind the associated testers of the unconfirmed file difference data.

[0105] For example, after relevant technical personnel obtain the progress information of a file's difference data through the corresponding interface, they may find that an Excel file's difference data has not been confirmed for a long time. They can then select the data reminder button corresponding to that file's difference data to generate a reminder message, which can be sent to the relevant testers via communication software or email. The reminder message can include a link to view the data: "This week's version has an unconfirmed Excel_diff file. Please click the link to confirm: http: / / 199.168.xxxx". This will accurately remind or urge the relevant testers who have not completed the confirmation work, thereby reducing the chance of missing file difference data and speeding up the work process.

[0106] It should be noted that the embodiments of the present invention include, but are not limited to, the examples described above. It is understood that, under the guidance of the ideas in the embodiments of the present invention, those skilled in the art can make settings according to actual circumstances, and the present invention does not limit such settings.

[0107] In this embodiment of the invention, commit information for an external branch can be obtained. Then, based on the file information in the commit information, external files are obtained from the external branch, corresponding development files are obtained from a preset development branch, and corresponding production files are obtained from a preset production environment. Next, the external files are compared with the development files and production files respectively to generate content difference data and release difference data corresponding to the external branch. Furthermore, the file information in the commit information is used to obtain test requirement information corresponding to the external files. The test requirement information is then associated with the content difference data and release difference data to generate file difference data corresponding to the commit information. On one hand, commit information for an external branch is obtained, and the corresponding external files are automatically obtained based on the file information in the commit information. The system integrates external files, development files, and production files. This simplifies the file acquisition process, ensures the completeness of file comparisons, and avoids omissions and false positives during manual checks due to large amounts of submitted data. Furthermore, by comparing external files with development files to generate content difference data, the accuracy of testing is improved. Comparing external files with production files to generate release difference data enhances the match between external files and development requirements. Simultaneously, linking test requirement information with content and release difference data generates file difference data, allowing for intuitive browsing of file difference data and rapid tracing and location of corresponding test requirement information, thus accelerating the product development and release schedule.

[0108] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0109] Reference Figure 4 The diagram shows a structural block diagram of a data processing device provided in an embodiment of the present invention, which may specifically include the following modules:

[0110] The commit information acquisition module 401 is used to acquire commit information for the external branch, the commit information including file information and operation information;

[0111] The file acquisition module 402 is used to acquire external files from the external branch, acquire corresponding development files from the preset development branch, and acquire corresponding production files from the preset production environment according to the file information.

[0112] The file comparison module 403 is used to compare the externally released file with the development file and the production file respectively, and generate content difference data and release difference data corresponding to the externally released file;

[0113] The test requirement information acquisition module 404 is used to acquire test requirement information corresponding to the external file based on the operation information.

[0114] The file difference data generation module 405 is used to associate the test requirement information with the content difference data and the release difference data to generate file difference data corresponding to the submission information.

[0115] In one optional embodiment, the submission information acquisition module 401 is specifically used for:

[0116] In response to a commit operation on the external branch, the commit information corresponding to the commit operation is extracted from the external branch.

[0117] In one optional embodiment, the submission information acquisition module 401 is specifically used for:

[0118] The corresponding commit information is extracted from the external branch at preset intervals.

[0119] In one optional embodiment, the file information includes a file name and a file path, and the file acquisition module 402 is specifically used for:

[0120] The file path is used to obtain the external file corresponding to the file name from the external branch, the development file corresponding to the file name from the preset development branch, and the production file corresponding to the file name from the preset production environment.

[0121] In one optional embodiment, the file comparison module 403 is specifically used for:

[0122] The external files of the same file type are compared with the development files to generate content difference data corresponding to the external files;

[0123] The external files of the same file type are compared with the production files to generate release difference data corresponding to the external files.

[0124] In one optional embodiment, the operation information includes an operation log, and the test requirement information acquisition module 404 is specifically used for:

[0125] Obtain the test requirement information corresponding to the external file from the operation log.

[0126] In one optional embodiment, the operation information includes submitter information, the test requirement information includes requirement number, requirement subject, and tester information, and the file difference data generation module 405 is specifically used for:

[0127] Package the submitter information, the request number, the request topic, and the tester information to generate corresponding target association information;

[0128] The target association information, the content difference data, and the publication difference data are associated to generate file difference data corresponding to the submission information.

[0129] In one alternative embodiment, the device further includes:

[0130] The data display interface creation module is used to create a data display interface corresponding to the file difference data, and to display the file difference data in the data display interface.

[0131] In one optional embodiment, the data display interface includes data filtering controls, and the device further includes:

[0132] A filter condition determination module is used to determine at least one filter condition corresponding to the file difference data in response to a selection operation on the data filter control.

[0133] The file difference data display module is used to display the file difference data that meets at least one filtering condition on the data display interface.

[0134] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0135] In addition, embodiments of the present invention also provide an electronic device, such as... Figure 5 As shown, it includes a processor 501, a communication interface 502, a memory 503, and a communication bus 504, wherein the processor 501, the communication interface 502, and the memory 503 communicate with each other through the communication bus 504.

[0136] Memory 503 is used to store computer programs;

[0137] When processor 501 executes the program stored in memory 503, it performs the following steps:

[0138] Obtain commit information for the external branch, the commit information including file information and operation information;

[0139] Based on the file information, retrieve the external files from the external branch, the corresponding development files from the preset development branch, and the corresponding production files from the preset production environment;

[0140] The externally released file is compared with the development file and the production file respectively to generate content difference data and release difference data corresponding to the externally released file;

[0141] Based on the operation information, obtain the test requirement information corresponding to the externally played file;

[0142] The test requirement information is associated with the content difference data and the release difference data to generate file difference data corresponding to the submission information.

[0143] In one optional embodiment, obtaining commit information for the external branch includes:

[0144] In response to a commit operation on the external branch, the commit information corresponding to the commit operation is extracted from the external branch.

[0145] In one optional embodiment, obtaining commit information for the external branch includes:

[0146] The corresponding commit information is extracted from the external branch at preset intervals.

[0147] In one optional embodiment, the file information includes a file name and a file path. The steps of obtaining the external file from the external branch, obtaining the corresponding development file from a preset development branch, and obtaining the corresponding production file from a preset production environment based on the file information include:

[0148] The file path is used to obtain the external file corresponding to the file name from the external branch, the development file corresponding to the file name from the preset development branch, and the production file corresponding to the file name from the preset production environment.

[0149] In one optional embodiment, the step of comparing the externally released file with the development file and the production file respectively, and generating content difference data and release difference data corresponding to the externally released file, includes:

[0150] The external files of the same file type are compared with the development files to generate content difference data corresponding to the external files;

[0151] The external files of the same file type are compared with the production files to generate release difference data corresponding to the external files.

[0152] In one optional embodiment, the operation information includes an operation log, and the step of obtaining test requirement information corresponding to the externally played file based on the operation information includes:

[0153] Obtain the test requirement information corresponding to the external file from the operation log.

[0154] In one optional embodiment, the operation information includes submitter information, the test requirement information includes a requirement number, a requirement topic, and tester information, and the step of associating the test requirement information with the content difference data and the release difference data to generate file difference data corresponding to the submission information includes:

[0155] Package the submitter information, the request number, the request topic, and the tester information to generate corresponding target association information;

[0156] The target association information, the content difference data, and the publication difference data are associated to generate file difference data corresponding to the submission information.

[0157] In an optional embodiment, the method further includes:

[0158] Create a data display interface corresponding to the file difference data, and display the file difference data in the data display interface.

[0159] In one optional embodiment, the data display interface includes data filtering controls, and the method further includes:

[0160] In response to a selection operation on the data filtering control, at least one filtering condition corresponding to the file difference data is determined;

[0161] The file differences that meet at least one of the filtering criteria are displayed on the data display interface.

[0162] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0163] The communication interface is used for communication between the aforementioned terminal and other devices.

[0164] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0165] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0166] like Figure 6 As shown, in another embodiment of the present invention, a computer-readable storage medium 601 is also provided, which stores instructions that, when run on a computer, cause the computer to perform the data processing method described in the above embodiments.

[0167] In another embodiment of the present invention, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to perform the data processing method described in the above embodiments.

[0168] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0169] 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.

[0170] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0171] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.

Claims

1. A data processing method, characterized by, The method comprises the following steps: obtaining submission information for a release branch, the submission information comprising file information and operation information; obtaining a release file from the release branch according to the file information, obtaining a corresponding development file from a preset development branch, and obtaining a corresponding production file from a preset production environment; the release file is a file obtained by submitting the development file to the release branch, and the version in the production environment is an old version of the release branch in the same cycle; comparing the release file with the development file and the production file respectively to generate content difference data corresponding to the release file and release difference data; the content difference data is used to evaluate the accuracy between the content submitted to the release branch and the content of the development branch, and the release difference data is used to evaluate the matching degree between the content submitted to the release branch and the development requirements of the current cycle; obtaining test requirement information corresponding to the release file according to the operation information; the operation information comprises submitter information, and the test requirement information comprises a requirement serial number, a requirement theme, and test personnel information; packaging the submitter information, the requirement serial number, the requirement theme, and the test personnel information to generate corresponding target association information; associating the target association information with the content difference data and the release difference data to generate file difference data corresponding to the submission information.

2. The method of claim 1, wherein, The method comprises the following steps: In response to a submission operation for the release branch, extracting submission information corresponding to the submission operation from the release branch.

3. The method of claim 1, wherein, The method comprises the following steps: Extracting corresponding submission information from the release branch every preset time length.

4. The method of claim 1, wherein, The file information comprises a file name and a file path, and the method comprises the following steps: obtaining a release file corresponding to the file name from the release branch, a development file corresponding to the file name from the preset development branch, and a production file corresponding to the file name from the preset production environment through the file path.

5. The method of claim 1, wherein, The method comprises the following steps: comparing the release file of the same file type with the development file to generate content difference data corresponding to the release file; comparing the release file of the same file type with the production file to generate release difference data corresponding to the release file.

6. The method of claim 1, wherein, The operation information comprises an operation log, and the method comprises the following steps: obtaining test requirement information corresponding to the release file from the operation log.

7. The method of claim 1, wherein, The method further comprises the following steps: Create a data display interface corresponding to the file difference data, and display the file difference data in the data display interface.

8. The method of claim 7, wherein, The data display interface includes a data filtering control, and the method further includes: In response to a selection operation on the data filtering control, determining at least one filtering condition corresponding to the file difference data; Displaying file difference data satisfying the at least one filtering condition in the data display interface.

9. A data processing apparatus, characterized by, Comprise: A submission information acquisition module is configured to acquire submission information for a release branch, wherein the submission information includes file information and operation information; A file acquisition module is configured to acquire a release file from the release branch, a corresponding development file from a preset development branch, and a corresponding production file from a preset production environment according to the file information; the release file is a file obtained by submitting the development file to the release branch; the version in the production environment is an old version of the release branch in the same cycle; A file comparison module is configured to compare the release file with the development file and the production file respectively, and generate content difference data corresponding to the release file and release difference data; The content difference data is used to evaluate the accuracy between the content submitted to the release branch and the content of the development branch, and the release difference data is used to evaluate the matching degree between the content submitted to the release branch and the development requirements of the current cycle version; A test requirement information acquisition module is configured to acquire test requirement information corresponding to the release file according to the operation information; the operation information includes submitter information, and the test requirement information includes a requirement serial number, a requirement theme, and test personnel information; A file difference data generation module is configured to package the submitter information, the requirement serial number, the requirement theme, and the test personnel information to generate corresponding target association information; associate the target association information with the content difference data and the release difference data to generate file difference data corresponding to the submission information.

10. An electronic device, comprising: A processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; The memory is configured to store a computer program; The processor is configured to execute the program stored on the memory to implement the method of any one of claims 1-8.

11. A computer-readable storage medium having instructions stored thereon, which, when executed by one or more processors, cause the processors to perform the method of any one of claims 1-8.

Images