A cross-device picture storage management method, system and storage medium

Abstract

The application discloses a cross-device picture storage management method and system and a storage medium. The method comprises the following steps: in response to a screenshot instruction of a user on a first device, a specified area of a screen of the first device is screenshotted, a first text information group in a first control interface is collected to form a first picture name for the screenshot, the content of the first text information group is updated to obtain a second text information group, and the second text information group is recorded in a configuration file. Then, after the execution program and the configuration file are transferred from the first device to a second device, each information in the second text information group is presented to a second control interface on the second device according to the configuration file. Finally, in response to a screenshot instruction of the user on the second device, a specified area of a screen of the second device is screenshotted, and a second text information group is collected to form a second picture name for the screenshot, so that a verification personnel can realize continuous naming of screenshots and pictures of a verification use case without reconfiguration when switching devices.

Description

Technical Field

[0001] This invention relates to the field of information management technology, and in particular to a cross-device image storage management method, system, and storage medium. Background Technology

[0002] Computer system verification is the process of ensuring that a computer system meets expected requirements when performing specific tasks. During verification, verifiers often use numerous screenshots to record the system's actual interface, operation flow, and status for comparison with expected results. To ensure accuracy, the captured images must be named and archived for later matching with test cases. However, since computer systems often involve multiple devices, verifiers frequently need to switch between them. Most screenshot tools on the market do not support continuous screenshots across devices. Each time a device is switched, verifiers must reconfigure the relevant settings and continue using the naming conventions from the previous device to maintain image naming continuity, making the verification process extremely inconvenient. Summary of the Invention

[0003] This invention addresses the shortcomings of existing technologies by disclosing a cross-device image storage management method, comprising the following steps:

[0004] S1, the program responds to the user's screenshot command on the first device, performs a screenshot operation on a specified area of ​​the screen of the first device, collects the first text information group in the first control interface and combines it according to the set name format to form the first image name for this screenshot, updates the content of the first text information group according to the naming update rules to obtain the second text information group and records it to the configuration file.

[0005] S2, after transferring the executable program and configuration file from the first device to the second device, the executable program responds to the user's first wake-up command on the second device, displays the second control interface on the second device according to the configuration file, and presents each piece of information in the second text information group to the multiple text components corresponding to the second control interface;

[0006] S3, the program responds to the user's screenshot command on the second device, performs a screenshot operation on a specified area of ​​the screen of the second device, collects the second text information group in the second control interface, and combines it according to the set name format to form the second image name used for this screenshot.

[0007] Preferably, the cross-device image storage management method further includes: the screenshot instruction is configured to capture a screenshot of a specified area in the verification test case interface of the computerized system running on the current device, wherein both the first control interface and the second control interface include a first text component for displaying and inputting the content of the first field, a second text component for displaying and updating the content of the second field, and a third text component for displaying and updating the content of the third field; wherein the content of the first field is configured as verification test case identification information, the content of the second field is configured as the step number of the verification test case, and the content of the third field is configured as the image number belonging to the current step number of the verification test case; the configuration file stores a set name format, and the execution program is used to combine the current verification test case identification information, the step number, and the image number according to the set name format and add preset format auxiliary information to form an image name for naming this screenshot.

[0008] Preferably, step S2 specifically includes: after transferring the executable program and configuration file from the first device to the second device, the executable program responds to the user's first wake-up command on the second device and displays the second control interface on the second device according to the configuration file; parses each text information in the second text information group and fills it into the corresponding text component of the second control interface; identifies whether there is a historical screenshot folder in the configuration file, and if so, obtains the address of the historical screenshot folder and sends a message confirming whether to continue using the current historical screenshot folder to store new screenshot images; if not, creates a new screenshot folder to store new screenshot images.

[0009] Preferably, step S2 specifically includes: the execution program responding to the user's first wake-up command on the second device, obtaining the first step number of the corresponding second text component in the second text information group, determining and obtaining the second step number according to the second field content update rule stored in the configuration file, wherein the second step number is the step number located next to the first step number obtained according to the second field content update rule; sending information on whether to update the step number in the second text component, and if the user confirms the update command, filling the second step number into the second text component, and restoring the image number in the third text component to its initial value according to the third field content update rule; if the user confirms not to update, filling each text information in the second text information group into the corresponding text component of the second control interface.

[0010] Preferably, step S3 specifically includes: obtaining the last image name in the historical screenshot folder; determining whether the second image name is consecutive to the last image name according to the naming update rule; if the first field content of the second image name is different from that of the last image name, determining whether the second and third field content of the second image name is the initial value; if it is not the initial value, issuing a screenshot naming error reminder; if the first field content of the second image name is the same as that of the last image name, determining whether the second field content of the second image name is the same as that of the last image name; if the second field is also the same, determining whether the third field is an adjacent value arranged according to the third field content update rule; if it is not an adjacent value, issuing a screenshot naming error reminder; if the second field is different, determining whether the second field is an adjacent value arranged according to the second field content update rule; if it is not an adjacent value, issuing a screenshot naming error reminder; if it is an adjacent value, issuing a screenshot naming error reminder when the third field of the second image name is not the initial value.

[0011] This invention also discloses a cross-device image storage management system, including a first screenshot module, an information transfer module, and a second screenshot module. The first screenshot module executes a program to respond to a user's screenshot command on a first device, performs a screenshot operation on a specified area of ​​the first device's screen, collects a first text information group from a first control interface, combines it according to a set naming format to form a first image name for this screenshot, updates the content of the first text information group according to a naming update rule to obtain a second text information group, and records it to a configuration file. The information transfer module, after transferring the executable program and configuration file from the first device to the second device, executes a program to respond to the user's first wake-up command on the second device, displays a second control interface on the second device according to the configuration file, and presents each piece of information in the second text information group to multiple text components corresponding to the second control interface. The second screenshot module executes a program to respond to a user's screenshot command on the second device, performs a screenshot operation on a specified area of ​​the second device's screen, collects a second text information group from the second control interface, combines it according to a set naming format to form a second image name for this screenshot.

[0012] Preferably, the system further includes: the screenshot instruction is configured to capture a screenshot of a specified area in the computerized system verification test case interface running on the current device, wherein both the first control interface and the second control interface include a first text component for displaying and inputting the content of the first field, a second text component for displaying and updating the content of the second field, and a third text component for displaying and updating the content of the third field; wherein the content of the first field is configured as verification test case identification information, the content of the second field is configured as the step number of the verification test case, and the content of the third field is configured as the image number belonging to the current step number of the verification test case; the configuration file stores a set name format, and the execution program is used to combine the current verification test case identification information, the step number, and the image number according to the set name format and add preset format auxiliary information to form an image name for naming this screenshot.

[0013] Preferably, the information transfer module further includes a display interface generation module, a configuration information filling module, and a storage address confirmation module. The display interface generation module is used to, after transferring the executable program and configuration file from the first device to the second device, have the executable program respond to the user's first wake-up command on the second device and display a second control interface on the second device according to the configuration file. The configuration information filling module is used to parse each text information in the second text information group and fill it into the corresponding text component of the second control interface. The storage address confirmation module is used to identify whether a historical screenshot folder exists in the configuration file; if it exists, it obtains the address of the historical screenshot folder and sends a confirmation message asking whether to continue using the current historical screenshot folder to store new screenshots; if not, it creates a new screenshot folder to store new screenshots.

[0014] The present invention also discloses a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of any of the cross-device image storage management methods described above.

[0015] The present invention also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of any of the cross-device image storage management methods described above.

[0016] The present invention discloses a cross-device image storage management method, system, and storage medium. When a user needs to switch verification devices, the execution program first completes the screenshot command in the current first device to capture and name a specified area of ​​the screen, and updates the text information for naming stored in the configuration file. Then, the execution program and the updated configuration file are transferred to the switched second device. The control interface of the execution program is displayed on the second device, and the configuration information in the configuration file is read. Finally, the second device responds to the user's new screenshot command, performs a screenshot operation on the screen of the second device, and renames the current screenshot according to the read configuration information. This realizes the automatic update of configuration information when switching devices, allowing users to complete the computer system verification process on different devices and ensuring the continuity of the naming and numbering of images captured by multiple devices.

[0017] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0018] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0019] Figure 1 This is a schematic diagram illustrating the steps of a cross-device image storage management method disclosed in an embodiment of the present invention.

[0020] Figure 2 This is a schematic diagram of the system used in the cross-device image storage management method disclosed in an embodiment of the present invention.

[0021] Figure 3 This is a schematic diagram of the first control interface disclosed in an embodiment of the present invention.

[0022] Figure 4 This is a schematic diagram illustrating the specific steps of step S2 disclosed in an embodiment of the present invention.

[0023] Figure 5 This is a schematic diagram illustrating the specific steps of user confirmation of configuration information according to an embodiment of the present invention.

[0024] Figure 6 This is a schematic diagram illustrating the specific steps of configuration information verification as disclosed in an embodiment of the present invention.

[0025] Figure 7 This is a structural block diagram of a cross-device image storage management system disclosed in another embodiment of the present invention.

[0026] Figure 8This is a structural block diagram of a server used to execute a cross-device image storage management method, as disclosed in another embodiment of the present invention. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the described embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0028] Unless otherwise defined, the technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this invention pertains. The terms “first,” “second,” and similar terms used in the specification and claims of this patent application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, the terms “an” or “a” and similar terms do not indicate a limitation of quantity, but rather indicate the presence of at least one.

[0029] Computer system verification is the process of ensuring that a computer system meets expected requirements when performing specific tasks. During verification, verifiers often use numerous screenshots to record the system's actual interface, operation flow, and status for comparison with expected results. To ensure accuracy, the captured images must be named and archived for later matching with test cases. However, since computer systems often involve multiple devices, verifiers frequently need to switch between them. Most screenshot tools on the market do not support continuous screenshots across devices. Each time a device is switched, verifiers must reconfigure the relevant settings and continue using the naming conventions from the previous device to maintain image naming continuity, making the verification process extremely inconvenient.

[0030] Therefore, this embodiment discloses a cross-device image storage management method, as shown in the appendix. Figure 1 As shown, it includes the following steps:

[0031] Step S1: The program responds to the user's screenshot command on the first device, performs a screenshot operation on a specified area of ​​the screen of the first device, collects the first text information group in the first control interface, combines it according to the set name format to form the first image name used for this screenshot, updates the content of the first text information group according to the naming update rules to obtain the second text information group and records it to the configuration file.

[0032] Specifically, this cross-device image storage management method is applied to, for example... Figure 2The system shown contains multiple client executables and receivers. Each client executable can be moved between different devices via a USB flash drive or other removable storage device and communicate with the receiver via a local area network.

[0033] When a verification user needs to switch devices during the same verification test case, the client program first captures the current screen interface based on the user's screenshot command on the local device, and automatically generates the image filename according to the configuration information in the local configuration file, for example...

[0034] The image, TestCase1_Step1_Image1.png, is then stored on the local disk, and the configuration file is updated to help with subsequent screenshot naming. This client's local configuration file stores text information groups containing multiple fields for naming images, as well as configuration information such as the naming format that limits the combination of these fields when naming images. The executable program uses the attached... Figure 3 The text components on the control interface shown can read, display, update, and record the configuration information, thereby enabling automatic naming of the captured images.

[0035] In this embodiment, the text information group includes the content of the first field, the content of the second field, and the content of the third field. Therefore, step S1 specifically includes the following content.

[0036] Step S11: After receiving a screenshot command from the user in the first device, a screenshot operation is performed on a specified area of ​​the screen to obtain the target image. This screenshot command is configured to capture a screenshot of a specified area in the computerized system verification test case interface.

[0037] Step S12: Obtain field information from multiple text components within the current first control interface. The first control interface includes a first text component for displaying and entering the content of a first field, a second text component for displaying and updating the content of a second field, and a third text component for displaying and updating the content of a third field.

[0038] Step S13: Combine the obtained first field content, second field content and third field content according to the set name format to form the image name for the target image. Name the target image according to the image name and save it to the local image folder. Modify the current third field content according to the preset second field content update rules, save and display it on the third text component.

[0039] On the first device with a client executable installed, the user sends a screenshot command to call the client to capture a specified area of ​​the computerized system verification test case interface running on the current device, and automatically names and stores the captured image according to preset rules for easy viewing and comparison in subsequent processes.

[0040] In this embodiment, the first field is configured as verification test case identification information, the second field is configured as the step number of the verification test case, and the third field is configured as the image number belonging to the current step number of the verification test case. The executable program then combines the current verification test case identification information, step number, and image number according to a set naming format, adds preset format auxiliary information, and forms an image name for this screenshot.

[0041] For details, see attached. Figure 3 As shown, the prefix CSV-000 is the verification test case identification information, step number 16 is the current step number, and figure number 1 is the current image number. The control interface also displays information such as the upload domain name. When the user clicks the upload button, the image is uploaded to the receiving end according to the upload domain name. Then, the content of the first text information group in the local configuration file is updated according to the naming update rules. Therefore, step S13 specifically includes the following:

[0042] Step S131: After naming the target image according to the image name, save it to the local image folder, and determine whether there is an image upload requirement. If so, obtain the configured upload address and send the named target image to the upload address.

[0043] Step S132: After acquiring and / or naming the screenshot in response to the user's screenshot command, the current image sequence number displayed in the third text component is incremented to the next sequence number according to the preset third field content update rules, while keeping the verification test case identification information in the first text component and the step number in the second text component unchanged. Through the above, the client automatically distinguishes and names different images subsequently captured by the user according to the set rules, automating image renaming and avoiding human errors caused by manual renaming.

[0044] In another embodiment, the text information group may contain only the content of the first field and the content of the second field. In this case, the content of the first field is configured as verification test case identification information, and the content of the second field is configured as the step number of the verification test case. Correspondingly, the client control interface only includes a first text component for displaying and entering the content of the first field, and a second text component for displaying and updating the content of the second field. The execution program is used to combine the current verification test case identification information and the step number according to the set naming format and add preset format auxiliary information to form an image name for naming this screenshot. In this case, the user only takes a screenshot once per step.

[0045] In this embodiment, the screenshot command of the first device specifically includes a first screenshot command and a second screenshot command, wherein the first screenshot command is attached. Figure 3 The "One Step, One Image" button indicates that the current screenshot differs from the previous one, requiring users to switch between steps. Users can trigger this button multiple times to capture images at different steps in sequence; the second screenshot command is attached. Figure 3 The "One Step, Multiple Images" button indicates that the current screenshot and the previous screenshot are in the same step, and no step switching is required. The user can take multiple screenshots in the same step by triggering the "One Step, Multiple Images" button multiple times. If the screenshot instruction is the first screenshot instruction, step S1 specifically includes the following content.

[0046] Step S101: After receiving the user's screenshot instruction in the first device, a screenshot operation is performed on the specified area of ​​the screen to obtain the target image.

[0047] Step S102: The current step number displayed in the second text component is incremented and updated to the next step number according to the preset second field content update rule. It is determined whether the current image sequence number in the third text component is the initial value. If it is not the initial value, the image sequence number is restored to the initial value according to the third field content update rule. The verification test case identification information of the first text component, the step number of the second text component, and the image sequence number of the third text component are obtained. The obtained verification test case identification information, step number, and image sequence number are arranged according to the set name format and filled with auxiliary format content to form the image name used to name the target image.

[0048] Step S103: After naming the target image according to the image name, save it to the local image folder. Update the current image sequence number displayed in the third text component to the next sequence number according to the preset third field content update rule, while keeping the verification test case identification information in the first text component and the image sequence number in the second text component unchanged.

[0049] In step S2, after transferring the executable program and configuration file from the first device to the second device, the executable program responds to the user's first wake-up command on the second device, displays the second control interface on the second device according to the configuration file, and presents each piece of information in the second text information group to the multiple text components corresponding to the second control interface.

[0050] When switching devices, the configuration file and client executable program in the first device are copied to a removable device such as a USB flash drive, and then imported into the second device by inserting the USB flash drive into the second device. At this time, the second device obtains the completed naming number by reading the text information group and setting the name format in the configuration file. When the verifier calls the executable program on the second device, the executable program takes a screenshot of the specified interface on the second device and continues to name according to the completed naming number and preset naming rules.

[0051] In this embodiment, as shown in the appendix Figure 4 As shown, step S2 specifically includes the following contents.

[0052] Step S21: After transferring the executable program and configuration file from the first device to the second device, the executable program responds to the user's first wake-up command on the second device and displays the second control interface on the second device according to the configuration file.

[0053] Step S22: Parse each text information in the second text information group and fill it into the corresponding text component of the second control interface.

[0054] Step S23: Identify whether a historical screenshot folder exists in the configuration file. If it exists, obtain the address of the historical screenshot folder and send a confirmation message asking whether to continue using the current historical screenshot folder to store new screenshots. If not, create a new screenshot folder to store new screenshots.

[0055] After the equipment was replaced, the location where the images were saved was reconfirmed to select the best way to save the images based on the content of different test cases, thereby improving the flexibility and systematic nature of image saving. At the same time, creating a new folder allows users to delete the folder and retake screenshots if verification errors occur.

[0056] In this embodiment, as Figure 5 As shown, step S2 also includes the following.

[0057] Step S201: The program responds to the user's first wake-up command on the second device, obtains the first step number of the corresponding second text component in the second text information group, and obtains the second step number according to the second field content update rule stored in the configuration file. The second step number is the step number located next to the first step number obtained according to the second field content update rule.

[0058] Specifically, device switching usually means switching verification test case steps. To avoid image naming errors caused by operator mistakes, this embodiment automatically updates the step numbers after device switching to improve naming accuracy.

[0059] Step S202: Send information on whether to update the step number in the second text component. If the user confirms the update instruction, fill the second step number into the second text component, and restore the image number in the third text component to its initial value according to the third field content update rule.

[0060] Step S203: If a user confirms that no update is required, then each text information in the second text information group is filled into the corresponding text component of the second control interface.

[0061] By automatically updating the step number after device switching and obtaining user confirmation, image naming errors caused by untimely updates of step numbers are avoided during device switching.

[0062] Step S3: The program responds to the user's screenshot command on the second device, performs a screenshot operation on a specified area of ​​the screen of the second device, collects the second text information group in the second control interface, and combines it according to the set name format to form the second image name used for this screenshot.

[0063] In this embodiment, as Figure 6 As shown, step S3 specifically includes:

[0064] Step S31: Obtain the last image name in the historical screenshot folder, and determine whether the second image name is consecutive to the last image name according to the naming update rules.

[0065] Step S32: If the content of the first field of the second image name is different from that of the last image name, then determine whether the content of the second field and the third field of the second image name are the initial values. If they are not the initial values, then issue a screenshot naming error reminder.

[0066] Specifically, when the content of the first field changes, it indicates that the verification test case has changed, and the content of the second and third fields needs to start from the initial value again. If the content of the second and third fields is not the initial value at this time, it indicates that the system screenshot is named incorrectly.

[0067] Step S33: If the content of the first field of the second image name is the same as that of the last image name, then determine whether the content of the second field of the second image name is the same as that of the last image name; if the second field is also the same, then determine whether the third field is an adjacent value arranged according to the update rule of the third field content; if it is not an adjacent value, then issue a screenshot naming error reminder; if the second field is different, then determine whether the second field is an adjacent value arranged according to the update rule of the second field content; if it is not an adjacent value, then issue a screenshot naming error reminder; if it is an adjacent value, then issue a screenshot naming error reminder when the third field of the second image name is not the initial value.

[0068] By further verifying and confirming the names of the new screenshots, the possibility of image naming confusion caused by information transmission errors due to device replacement is reduced, further enhancing the stability of cross-device image storage management.

[0069] In this embodiment, to further avoid information confusion caused by switching between multiple devices, a configuration information node table can be set up to perform multiple verifications or repeated verifications by reading each node, specifically including the following content.

[0070] Step S301: According to the user node generation instruction, store the content of each field in the first text information group in the current first control interface in the configuration information node table. The configuration information node table stores the storage time, storage sequence number, and the content of the first field, the second field, and the third field of different nodes.

[0071] In step S302, after transferring the executable program and configuration file from the first device to the second device, the executable program responds to the user's first wake-up command on the second device and sends node read command and node read information to the user.

[0072] Step S303: If a user node read instruction and the node information selected by the user are received, the content of the first field, the second field, and the third field corresponding to the node in the configuration information node table are filled into the multiple text components corresponding to the second control interface and a new screenshot folder is created to store the new screenshot images; otherwise, the information in the second text information group is presented to the multiple text components corresponding to the second control interface.

[0073] By setting up nodes, screenshot errors caused by chaotic device switching can be avoided when there are too many devices. Users can re-capture the content being verified on the device by reading the number data of different nodes, thus enhancing the flexibility of the verification system.

[0074] In this embodiment, the receiving end can also simultaneously receive image content uploaded by multiple clients and summarize the uploaded images, specifically including the following:

[0075] Step S401: Receive the first client image sent by the first client after taking a screenshot of a selected area of ​​the interface of the computerized system verification test case running on the first client.

[0076] Step S402: Obtain the image name of the second client image stored in the image file library. The second client image is an image obtained by taking a screenshot of another selected area of ​​the same computerized system verification test case running on the second client, sent by the second client.

[0077] Step S403: After sorting the first client image and the second client image according to the update rules of the corresponding fields of the verification test case, store them in the corresponding sorting position in the image file library.

[0078] Specifically, step S403 also includes the following:

[0079] Step S401: Identify the content of each field in the received first client image name according to the field content update rules. If there is a second client image with the same step number as the first client image name, obtain the first client image number in the first client image name and the second client image number in the second client image name.

[0080] In step S402, if the image number of the first client is before the image number of the second client, it is saved to the image file library. If the image number of the first client is after the image number of the second client or is the same as the image number of the second client, a verification step repetition reminder is sent to the first client. If a confirmation save instruction is received from the first client, the first client image is sorted according to the image number order of the first client image and the second client image, and then stored in the corresponding sorting position in the image file library.

[0081] When receiving screenshots uploaded by a client, the system takes into account screenshots uploaded by other clients to reorder and rename images that do not meet the order requirements. This improves the cleanliness and sequence of images stored in the image library and avoids unnecessary naming or screenshot duplication caused by the inability of different clients to communicate in a timely manner.

[0082] Step S402 further includes: if the first client image number is after or the same as the second client image number, then query the image file library for the step numbers of each image name with the same verification test case identification information to form a verified step sequence, and send a verification step duplication reminder to the first client. The verification step duplication reminder includes the step number of the current image that is judged to be duplicated, and replacement step suggestion information containing the verified step sequence. By providing the first terminal with the verified step sequence, the first terminal avoids repeatedly selecting already verified steps, thus improving verification efficiency.

[0083] Step S402 further includes: if the first client image number is after the second client image number, and according to the third field content update rule, a third client image number exists between the first client image number and the second client image number, and the screenshot image with the third client image number has not yet been stored in the image file library, then image supplement information is sent to the first client. This image supplement information includes the step number and image number to which the missing image belongs. By querying the missing image number and sending the missing information and supplement information to the first device, image loss caused by transmission errors during the previous image transmission is screened and supplemented, avoiding incomplete image acquisition during the verification process.

[0084] The present invention discloses a cross-device image storage management method, system, and storage medium. When a user needs to switch verification devices, the execution program first completes the screenshot command in the current first device to capture and name a specified area of ​​the screen, and updates the text information for naming stored in the configuration file. Then, the execution program and the updated configuration file are transferred to the switched second device. The control interface of the execution program is displayed on the second device, and the configuration information in the configuration file is read. Finally, the second device responds to the user's new screenshot command, performs a screenshot operation on the screen of the second device, and renames the current screenshot according to the read configuration information. This realizes the automatic update of configuration information when switching devices, allowing users to complete the computer system verification process on different devices and ensuring the continuity of the naming and numbering of images captured by multiple devices.

[0085] In another embodiment, as shown in the appendix Figure 7As shown, a cross-device image storage management system is also disclosed, including a first screenshot module 1, an information transfer module 2, and a second screenshot module 3. The first screenshot module 1 is used to execute a program in response to a user's screenshot command on the first device, perform a screenshot operation on a specified area of ​​the screen of the first device, collect a first text information group from the first control interface, combine it according to a set naming format to form a first image name for this screenshot, update the content of the first text information group according to a naming update rule to obtain a second text information group, and record it in a configuration file. The information transfer module 2 is used to, after transferring the executable program and configuration file from the first device to the second device, execute a program in response to the user's first wake-up command on the second device, display a second control interface on the second device according to the configuration file, and present the information in the second text information group to multiple text components corresponding to the second control interface. The second screenshot module is used to execute a program in response to a user's screenshot command on the second device, perform a screenshot operation on a specified area of ​​the screen of the second device, collect a second text information group from the second control interface, combine it according to a set naming format to form a second image name for this screenshot.

[0086] In this embodiment, the screenshot command is configured to capture a screenshot of a specified area in the computerized system verification test case interface running on the current device. Both the first and second control interfaces include a first text component for displaying and inputting the content of a first field, a second text component for displaying and updating the content of a second field, and a third text component for displaying and updating the content of a third field. The first field content is configured as verification test case identification information, the second field content is configured as the step number of the verification test case, and the third field content is configured as the image number belonging to the current step number of the verification test case. The configuration file stores a set name format, and the executable program combines the current verification test case identification information, the step number, and the image number according to the set name format, adds preset format auxiliary information, and then forms an image name for naming this screenshot.

[0087] In this embodiment, the information transfer module further includes a display interface generation module, a configuration information filling module, and a storage address confirmation module. The display interface generation module is used to, after transferring the executable program and configuration file from the first device to the second device, have the executable program respond to the user's first wake-up command on the second device and display a second control interface on the second device according to the configuration file. The configuration information filling module is used to parse the text information in the second text information group and fill it into the corresponding text components of the second control interface. The storage address confirmation module is used to identify whether a historical screenshot folder exists in the configuration file. If it exists, it obtains the address of the historical screenshot folder and sends a confirmation message asking whether to continue using the current historical screenshot folder to store new screenshots. If not, it creates a new screenshot folder to store new screenshots.

[0088] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar parts between embodiments can be referred to interchangeably. Regarding the cross-device image storage management system disclosed in the embodiments, since it corresponds to the cross-device image storage management method disclosed in the embodiments, the description is relatively simple, and relevant parts can be referred to the foregoing method section.

[0089] In other embodiments, as shown in the appendix Figure 8 As shown, a server is also provided, including a memory 504, a processor 503, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the various steps of the cross-device image storage management method described in the above embodiments. The server may include, but is not limited to, a processor and a memory. Those skilled in the art will understand that the schematic diagram is merely an example of a server and does not constitute a limitation on the server; it may include more or fewer components than illustrated, or combine certain components, or use different components.

[0090] If the cross-device image storage management system is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various cross-device image storage management method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory, random access memory, electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0091] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

[0092] In summary, the above description is only a preferred embodiment of the present invention. All equivalent changes and modifications made within the scope of the claims of the present invention should be covered by the present invention.

Claims

1. A cross-device image storage management method, characterized in that, Includes the following steps: S1, the execution program responds to the user's screenshot command on the first device, performs a screenshot operation on a specified area of ​​the screen of the first device, collects the first text information group in the first control interface, combines it according to a set name format to form the first image name for this screenshot, updates the content of the first text information group according to the naming update rule to obtain the second text information group and records it to the configuration file; the screenshot command is configured to capture a screenshot of a specified area in the computerized system verification test case interface running on the current device, wherein both the first control interface and the second control interface include a first text component for displaying and entering the content of the first field, a second text component for displaying and updating the content of the second field, and a third text component for displaying and updating the content of the third field; wherein the content of the first field is configured as the verification test case identification information, the content of the second field is configured as the step number of the verification test case, and the content of the third field is configured as the image number belonging to the current step number of the verification test case, the configuration file stores a set name format, and the execution program is used to combine the current verification test case identification information, the step number and the image number according to the set name format and add preset format auxiliary information to form the image name for naming this screenshot; S2, after transferring the executable program and configuration file from the first device to the second device, the executable program responds to the user's first wake-up command on the second device, displays the second control interface on the second device according to the configuration file, and presents each piece of information in the second text information group to the corresponding multiple text components of the second control interface; the executable program responds to the user's first wake-up command on the second device, obtains the first step number of the corresponding second text component in the second text information group, and determines and obtains the second step number according to the second field content update rule stored in the configuration file. The second step number is the step number located next to the first step number obtained according to the second field content update rule; it sends information on whether to update the step number in the second text component. If the user confirms the update command, the second step number is filled into the second text component, and the image number in the third text component is restored to its initial value according to the third field content update rule; if the user confirms not to update, each piece of text information in the second text information group is filled into the corresponding text component of the second control interface; S3, the program responds to the user's screenshot command on the second device, performs a screenshot operation on a specified area of ​​the screen of the second device, collects the second text information group in the second control interface, and combines it according to the set name format to form the second image name used for this screenshot.

2. The cross-device image storage management method according to claim 1, characterized in that, Step S2 specifically includes: After the executable program and configuration file are transferred from the first device to the second device, the executable program responds to the user's first wake-up command on the second device and displays the second control interface on the second device according to the configuration file; Parse each text message in the second text information group and fill it into the corresponding text component of the second control interface; If a historical screenshot folder exists in the configuration file, the address of the historical screenshot folder is obtained and a confirmation message is sent to indicate whether to continue using the current historical screenshot folder to store new screenshots. If not, a new screenshot folder is created to store new screenshots.

3. The cross-device image storage management method according to claim 2, characterized in that, Step S3 specifically includes: Get the last image name in the historical screenshot folder, and determine whether the second image name is consecutive to the last image name according to the naming update rules; If the content of the first field of the second image name is different from that of the last image name, then it is determined whether the content of the second field and the third field of the second image name are the initial values. If they are not the initial values, a screenshot naming error reminder is issued. If the content of the first field of the second image name is the same as that of the last image name, then it is determined whether the content of the second field of the second image name is the same as that of the last image name. If the second field is also the same, then it is determined whether the third field is an adjacent value arranged according to the update rule of the third field content. If it is not an adjacent value, then a screenshot naming error warning is issued. If the second field is different, then it is determined whether the second field is an adjacent value arranged according to the update rule of the second field content. If it is not an adjacent value, then a screenshot naming error warning is issued. If it is an adjacent value, then a screenshot naming error warning is issued when the third field of the second image name is not the initial value.

4. A cross-device image storage management system, characterized in that, include: The first screenshot module is used to execute a program in response to a user's screenshot command on the first device, perform a screenshot operation on a specified area of ​​the screen of the first device, collect a first text information group from the first control interface, combine it according to a set name format to form a first image name for this screenshot, update the content of the first text information group according to the naming update rules to obtain a second text information group and record it in the configuration file; the screenshot command is configured to capture a screenshot of a specified area in the computerized system verification test case interface running on the current device, wherein both the first control interface and the second control interface include a first text component for displaying and entering the content of the first field, a second text component for displaying and updating the content of the second field, and a third text component for displaying and updating the content of the third field; wherein the content of the first field is configured as verification test case identification information, the content of the second field is configured as the step number of the verification test case, and the content of the third field is configured as the image number belonging to the current step number of the verification test case, the configuration file stores a set name format, and the executing program is used to combine the current verification test case identification information, the step number, and the image number according to the set name format and add preset format auxiliary information to form an image name for naming this screenshot; The information transfer module is used to, after transferring the executable program and configuration file from the first device to the second device, respond to the user's first wake-up command on the second device, display the second control interface on the second device according to the configuration file, and present each piece of information in the second text information group to multiple text components corresponding to the second control interface; responding to the user's first wake-up command on the second device, the executable program obtains the first step number of the corresponding second text component in the second text information group, determines and obtains the second step number according to the second field content update rule stored in the configuration file, the second step number being the step number located next to the first step number obtained according to the second field content update rule; sends information on whether to update the step number in the second text component, if a user confirmation update command is received, the second step number is filled into the second text component, and the image number in the third text component is restored to its initial value according to the third field content update rule; if a user confirmation not to update command is received, each piece of text information in the second text information group is filled into the corresponding text component of the second control interface; The second screenshot module is used to execute the program in response to the user's screenshot command on the second device, perform a screenshot operation on a specified area of ​​the screen of the second device, collect the second text information group in the second control interface, and combine it according to the set name format to form the second image name used for this screenshot.

5. The cross-device image storage management system according to claim 4, characterized in that, The information transfer module also includes: The display interface generation module is used to display the second control interface on the second device according to the configuration file after the executable program and configuration file are transferred from the first device to the second device. The configuration information filling module is used to parse each text information in the second text information group and fill it into the corresponding text component of the second control interface; The storage address confirmation module is used to identify whether a historical screenshot folder exists in the configuration file. If it exists, the module obtains the address of the historical screenshot folder and sends a confirmation message asking whether to continue using the current historical screenshot folder to store new screenshots. If it does not use the folder, a new screenshot folder is created to store new screenshots.

6. A server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1-3.

7. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-3.

Images