CN116361156A - Smoking test method, computer device and computer readable storage medium for test case - Google Patents

Smoking test method, computer device and computer readable storage medium for test case Download PDF

Info

Publication number
CN116361156A
CN116361156A CN202310202032.9A CN202310202032A CN116361156A CN 116361156 A CN116361156 A CN 116361156A CN 202310202032 A CN202310202032 A CN 202310202032A CN 116361156 A CN116361156 A CN 116361156A
Authority
CN
China
Prior art keywords
test
test case
component tool
flow sequence
page element
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310202032.9A
Other languages
Chinese (zh)
Inventor
连�晋
彭邦
幸勋
张宇阳
刘瑶瑶
刘玲
孙长青
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yuanguang Software Co Ltd
Original Assignee
Yuanguang Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Yuanguang Software Co Ltd filed Critical Yuanguang Software Co Ltd
Priority to CN202310202032.9A priority Critical patent/CN116361156A/en
Publication of CN116361156A publication Critical patent/CN116361156A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/0486—Drag-and-drop
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/36—Software reuse
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention provides a smoking test method, a computer device and a computer readable storage medium of a test case, the method comprises the steps of creating a test case, displaying an editable flow sequence and a component tool box on a test flow design page of the test case, wherein the component tool box comprises at least one packaged component tool, and each component tool comprises one or more preset test steps; acquiring a dragging instruction for dragging a target component tool of the component tool box to a flow sequence, and adding a testing step of the target component tool into the flow sequence according to the dragging instruction; after the process sequence is designed, designing test assertion; and acquiring the numerical value of the index parameter according to the flow sequence, and applying the numerical value of the index parameter to finish assertion and output a test result. The invention also provides a computer device for realizing the method and a computer readable storage medium. The invention can improve the convenience of the construction of the test case and the efficiency of the smoking test.

Description

Smoking test method, computer device and computer readable storage medium for test case
Technical Field
The invention relates to the technical field of computer program testing, in particular to a smoke test method for test cases, and also relates to a computer device and a computer readable storage medium for realizing the method.
Background
Test cases are descriptions of test tasks for a particular software product, and typically require testing by test cases after the software product has been initially developed to discover defects in the software product. Because for different software products, corresponding test cases are required to be built for testing, and the workload of building the test cases is high.
At present, the automatic test case is built, the problems of large production and test environment page element variability, weak code development level capability of a case builder, low multiplexing degree of the case, large amount of structured and unstructured data required to be uniformly acquired and stored are solved, the test case is easy to make errors in scene operation, the built test case is complex in use due to large code quantity, complex in construction due to incapability of multiplexing, and difficult in integration of different types of data.
When the problems are encountered, the existing processing mode is to update the corresponding page element content responsible person and then maintain the test case, and the requirements of quick deployment and low maintenance of the automatic test cannot be met because a long-time waiting mechanism is required to perform fault tolerance aiming at the lower stability of the tested environment. In addition, when the test case is built at present, the operation of the test flow design page of the built test case is not humanized, the operation is inconvenient, the test case is longer in building time, the steps required to be executed are too many, errors are easy to occur, and the building accuracy of the test case is also affected.
Currently, robot process automation (Robotic process automation, RPA) technology, which is a technology based on artificial intelligence technology capable of simulating and replacing manual labor, has been widely used, and various operations are performed by intelligent robots. However, no method for automatically testing the smoking of the test case based on the RPA technology is proposed at present, so that the smoking test of the test case is still manually performed, the smoking test time of the test case is long, and the efficiency is low.
Disclosure of Invention
The first object of the present invention is to provide a smoke test method for a test case, which is simple in operation room of the test case and improves efficiency.
A second object of the present invention is to provide a computer apparatus for implementing the smoke test method of the test case.
A third object of the present invention is to provide a computer-readable storage medium embodying the smoke test method of the above test case.
In order to achieve the main purpose of the invention, the smoking test method of the test case provided by the invention comprises the steps of creating a test case, displaying an editable flow sequence and a component tool box on a test flow design page of the test case, wherein the component tool box comprises at least one packaged component tool, and each component tool comprises one or more preset test steps; acquiring a dragging instruction for dragging a target component tool of the component tool box to a flow sequence, and adding a testing step of the target component tool into the flow sequence according to the dragging instruction; after the process sequence is designed, designing test assertion; and acquiring the numerical value of the index parameter according to the flow sequence, and applying the numerical value of the index parameter to finish assertion and output a test result.
According to the scheme, when the test case is built, the target component tool in the component tool box can be dragged into the flow sequence, and the step of the target component tool can be automatically added into the flow sequence, so that the development time for inputting the corresponding step is saved, and the building efficiency of the test case can be improved. Moreover, as the target component tool is a component which is verified to be feasible, the accuracy of the work of the used target component can be ensured by directly multiplexing the developed component tool, so that the development accuracy of the test case is improved.
Preferably, the design flow sequence further comprises: creating a new test step in the flow sequence; after the process sequence is designed, the method further comprises the following steps: the created new test steps are packaged into new component tools, which are added to the component toolbox.
Therefore, when the test case is built, a user can package new testing steps into new assembly tools and add the new testing steps into the assembly tool box, so that the assembly tools of the assembly tool box are richer, and the new assembly tools can be utilized in the process of building other test cases later.
Further, adding a new component tool to the component toolbox comprises: a unique identification is created for the new component tool, which is marked in the component toolbox with the unique identification.
It can be seen that, since each component tool has its own unique identifier, when these component tools are subsequently invoked, the component tools can be quickly searched, and the component tools to be used are dragged into the flow sequence,
preferably, the design flow sequence further comprises: and acquiring an instruction of the execution selector, acquiring the content of the target page element by using the selector, and adding the content of the target page element into the flow sequence.
The content of the target page element is selected through the selector, the content of the target page element is directly acquired, the acquired content is added to the flow sequence, repeated development is not needed for the page element with the same content, the content of the existing page element is directly acquired, and the content is added to the flow sequence, so that the operation is very convenient.
Further, adding the content of the target page element to the flow sequence includes: the contents of the target page element are added to the currently edited component tool.
Therefore, the content of the target page element can be added rapidly, so that the test case can be built more efficiently and conveniently.
The further scheme is that an attribute window of the component tool is also displayed on a test flow design page of the test case; adding the contents of the target page element to the currently edited component tool includes: and adding the content of the target page element into the attribute window corresponding to the currently edited component tool.
Therefore, the content of the target page element is added into the attribute window corresponding to the currently edited component tool, the editing of the attribute of the currently edited component tool can be completed, and the attribute of the currently edited component tool is convenient to modify.
Further, the method for obtaining the content of the target page element by using the selector includes: and acquiring a click signal, and determining a target page element corresponding to the click position from the plurality of page elements by the selector according to the position of the click signal.
Therefore, the selector can quickly determine the target page element which needs to be selected by the user from a plurality of page elements, and the selection of the page elements is more convenient.
Further, the method for obtaining the numerical value of the index parameter according to the flow sequence, and completing the assertion by applying the numerical value of the index parameter and outputting the test result includes: and automatically acquiring the numerical value of the index parameter by using the RPA robot, executing a flow sequence by using the RPA robot, and outputting a test result.
The RPA robot is used for realizing automatic smoking test operation, so that the efficiency of smoking test can be improved, and the complexity of manual operation is avoided.
In order to achieve the second object, the present invention provides a computer device including a processor and a memory, wherein the memory stores a computer program, and the computer program when executed by the processor implements the steps of the smoke test method of the test case.
In order to achieve the third object, the present invention provides a computer program stored on a computer readable storage medium, which when executed by a processor, implements the steps of the smoke test method of the test case.
Drawings
FIG. 1 is a flow chart of an embodiment of a smoke test method for a test case of the present invention.
FIG. 2 is a schematic diagram of a test flow design page of a test case in an embodiment of a smoke test method of the test case of the present invention.
FIG. 3 is a schematic diagram of a test flow design page of a display selector in an embodiment of a smoke test method for a test case of the present invention.
FIG. 4 is a schematic diagram of a selector acquiring a first state of a page element in an embodiment of a smoke test method of a test case of the present invention.
FIG. 5 is a schematic diagram of a selector acquiring a second state of a page element in an embodiment of a smoke test method of a test case of the present invention.
The invention is further described below with reference to the drawings and examples.
Detailed Description
According to the smoking test method for the test case, the smoking test is automatically executed through the RPA robot, and the efficiency of the test case construction is improved through the visual mode, the dragging assembly tool, the automatic rotation page element of the selector and other operations when the test case is constructed, so that the test case is constructed more conveniently.
The smoking test method of the test case can be operated on one computer device, for example, the computer device can be a PC, a smart phone, a tablet personal computer and the like, the computer is provided with a processor and a memory, and a computer program is stored in the memory, so that the smoking test method of the test case is realized through the computer program.
Smoking test method embodiment of test case:
referring to fig. 1, the present embodiment first executes step S1 to create a test case, where the newly created test case is a test for a certain software program. Because each program has differences in the operation environment and the implementation function, the operation flow of each test case is different.
When the test case is created, step S2 is executed, and a special interface for editing the flow executed by the test case is displayed, which is called a test flow design page, as shown in fig. 2, a flow sequence 24 is displayed in the middle of the test flow design page, the flow executed by the test case is displayed in a sequence manner, and is displayed in a window of the flow sequence 24, so that a user can intuitively understand which specific steps the currently designed flow sequence contains.
The left side of the test flow design page is a display window of the component toolbox 20, the component toolbox 20 contains a plurality of component tools, each component tool is a pre-packaged component tool, the component tools contain a plurality of preset steps, and each component tool can realize a preset function, such as obtaining index parameters, realizing webpage skip, data transmission and the like.
The test flow design page also displays a window of the current flow 21 and a window of the flow operation field 22, and the user can know which flow the current flow sequence is in through the window of the current flow 21, and can perform operations such as minimization through the window of the flow operation field 22. The test flow design page also displays a window of the component tool attribute bar 23, and the attribute of the currently edited component tool is displayed in the attribute tool bar 23, so that a user can intuitively know the attribute of the currently edited component tool.
The test flow design page also displays a window of a variable and parameter column 25 and a window of a log message column 26, so that a user can know the conditions of the variable, the parameter and the like in the test case construction process through the variable and parameter column 25, and can know the specific construction condition of the test case through the window of the log message column 26.
When the test case is built, a user can directly select the packaged component tools as a part of the flow sequence, namely, aiming at the packaged flow for realizing the specific function, the user does not need to repeatedly develop and only needs to acquire the component tools for realizing the same function from the component tool box. Preferably, in the component toolbox 20, each component tool has a unique identifier, which may be a name of the component tool or a code of the component tool, etc., and the user may identify each component tool through the identifier of the component tool.
When a user needs to apply a component tool, the required target component job can be dragged directly into the flow sequence 24. Specifically, the user may click on the target component tool and drag the target component directly into the flow sequence 24 without loosening the mouse, and release the mouse when the icon of the target component tool is located in the window of the flow sequence 24. When it is detected that the user performs the above-mentioned drag action, the computer device will perform step S3 to obtain a drag instruction of the above-mentioned operation issued by the user, and perform step S4 to add the target component work to the flow sequence 24 according to the drag operation of the user. Since the target instruction tool actually contains one or more steps that are preset, the target component job is added to the flow sequence 24, which is actually adding the steps that are preset to the flow sequence 24.
Of course, when editing the flow sequence of the test case, the component tools in the component tool box are not necessarily used, the steps can be set according to actual needs, and the user can directly input corresponding codes in the flow sequence 24 to embody specific steps.
In addition, in order to facilitate editing of the test case, the user may design a part of the flow sequence 24 by using the content of the existing page element, thereby avoiding repeated development for the same function and improving the construction efficiency of the test case. In this embodiment, the selector is used to extract the page element, and obtain the content in the page element, and directly add the content in the page element to the flow sequence 24.
Thus, in designing the flow sequence, step S5 may be performed, applying a selector to edit the flow sequence 24. Referring to fig. 3, if the user needs to use the function of the selector, an instruction to activate the selector 30 is issued on the test flow design page of the test case, for example, a double click of a mouse or clicking of a specific button, and a window of the selector 30 is displayed on the test flow design page. Preferably, the window of the selector 30 is displayed around the window of the flow sequence 24 so that the user can intuitively understand the window of the selector 30.
Then, the user opens the page requiring the acquisition of the page element, for example, the page requiring the acquisition is on the page as shown in fig. 4, and the user directly opens the page and places the mouse on the page requiring the acquisition. In this embodiment, the target page element that the user needs to acquire is a page element of the login account, and the page element of the login account is displayed on the page shown in fig. 4, where the page element is the target page element 35 that needs to acquire.
The user moves the mouse to the target page element 35 to be acquired, and the selector does not determine which page element the user needs to select because other page elements, such as a login password, a verification code and the like, exist around the login account. To facilitate the user's quick selection of target page elements, each page element may be marked. For example, the user moves the mouse to a certain page element, and the page element is displayed by using a special display mode, for example, changing the display color of the page element, or adding a red frame at the edge of the page element, etc. The user can intuitively understand that when the selector 30 is currently selected, if the currently selected page element of the selector 30 is the target page element desired to be selected by the user, the user clicks the mouse to indicate that the currently selected page element of the selector 30 is the final selected target page element 35. In this embodiment, the selector 30 determines the selected target page element 35 according to the click signal of the mouse, that is, selects the target page element 35 from the plurality of page elements on the page according to the click position, preferably, the target page element 35 is one of the plurality of page elements displayed on the page, for example, the one closest to the click position is the target page element 35.
When the user selects the target page element 35, the content of the target page element 35 is displayed on the page, for example, the content display window 36 is displayed on the page, and the content of the target page element 35 is displayed in the content display window 36. As can be seen from fig. 5, the code of the page element of the login account is shown in the content display window 36, and a "ok" key is shown in the lower right corner of the content display window 36, and if the user determines that these codes need to be used, the selector 30 acquires the code corresponding to the target page element 35.
Then, returning to the test flow design page, as shown in fig. 3, the selector 30 presents the code corresponding to the acquired target page element 35 in the content window 31, and the user can confirm whether the content presented in the content window 31 needs to be added to the flow sequence 30. If the user determines that the content presented in the content window 31 needs to be added to the flow sequence 30, then click the "ok" button in the lower right hand corner of the content window 31.
Further, when the content of the target page element is added to the flow sequence, the content of the target page element may be added to the currently edited component tool. For example, the user may modify the component tool, that is, after the user drags the target component tool to the flow sequence 24, the attribute information of the target component tool is shown on the right side of the test flow design page, and the user may further modify the target component tool, so that the target component tool can better adapt to the current design.
When the content of the target page element is added to the currently edited component tool, the content of the target page element is added to the attribute window corresponding to the currently edited component tool, namely, the attribute of the currently edited component tool is modified, so that the currently edited component tool meets the requirements of the current test case more.
In addition, when editing the current flow sequence, the user can package a part of steps of the current flow sequence into a new assembly tool, so that the new assembly tool can be called when other subsequent test cases are built. For this purpose, step S6 may also be performed when building the test case, encapsulating the preset steps in the flow sequence 24 into new component tools, and step S7 may be performed, adding the newly encapsulated component tools to the component toolbox. In order to identify each component tool, when a new component tool is added to the component tool box, a unique identification needs to be set for each component tool, for example, a unique name or identification code is given to each component tool. In this way, new component tools may be presented in the component toolbox 20.
After the flow sequence 24 of the test case is designed, step S8 is executed to design test assertions of the test case, that is, when the test case runs, the test software is considered to pass the test, and when the test case runs, the test software is considered to fail the test.
After the assertion is designed, the test case can be applied to smoke test the software to be tested. In order to improve the efficiency of the smoking test, the embodiment uses the RPA robot to execute the smoking test, specifically, the RPA robot automatically obtains the numerical value of the index parameter required by the test, and applies the RPA robot to execute the flow sequence and output the test result. Finally, the PRA robot outputs a test result according to the execution condition of the test case, that is, the step S10 is executed, so that the user can intuitively know which problems exist in the tested software.
On one hand, the embodiment improves the construction efficiency of the test case through the dragging operation of the assembly tool, avoids repeated development of a flow sequence through multiplexing of the assembly tool, and reduces the construction time of the test case; on the other hand, the embodiment can improve the testing efficiency of the smoke test by performing automatic test through the RPA robot.
Computer apparatus embodiment:
the computer device of the present embodiment may be an intelligent terminal device or a desktop computer, and the computer device has a processor, a memory, and a computer program stored in the memory and executable on the processor, for example, an information processing program for implementing the above-mentioned information processing method, and the processor implements the steps of the smoke test method of the above-mentioned test case when executing the computer program.
For example, a computer program may be split into one or more modules, which are stored in memory and executed by a processor to perform the various modules of the invention. One or more of the modules may be a series of computer program instruction segments capable of performing specific functions for describing the execution of the computer program in the terminal device.
It should be noted that the terminal device may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, and the like. The terminal device may include, but is not limited to, a processor, a memory. It will be appreciated by those skilled in the art that the schematic diagram of the present invention is merely an example of a terminal device and is not limiting of the terminal device, and may include more or less components than those illustrated, or may combine some components, or different components, e.g., the terminal device may also include an input-output device, a network access device, a bus, etc.
The processor referred to in the present invention may be a central processing unit (Central Processing Unit, CPU), or other general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, the processor being a control center of the terminal device, and the various interfaces and lines being used to connect the various parts of the overall terminal device.
The memory may be used to store computer programs and/or modules, and the processor may implement various functions of the terminal device by running or executing the computer programs and/or modules stored in the memory, and invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the cellular phone, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, memory, plug-in hard disk, smart Media Card (SMC), secure Digital (SD) Card, flash Card (Flash Card), at least one disk storage device, flash memory device, or other volatile solid-state storage device.
Computer-readable storage medium:
the computer program stored in the computer means may be stored in a computer readable storage medium if implemented in the form of software functional units and sold or used as a stand alone product. Based on such understanding, the present invention may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of the smoke test method of the above test case.
Wherein the computer program comprises computer program code, which may be in the form of source code, object code, executable files or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium can be appropriately increased or decreased according to the requirements of the jurisdiction's jurisdiction and the patent practice, for example, in some jurisdictions, the computer readable medium does not include electrical carrier signals and telecommunication signals according to the jurisdiction and the patent practice.
Finally, it should be emphasized that the invention is not limited to the above embodiments, for example, variations in the specific manner in which the selector selects the page elements, or variations in the contents of the test flow design page presentation, which are also intended to be encompassed by the scope of the claims.

Claims (10)

1. The smoking test method of the test case is characterized by comprising the following steps:
creating a test case, and displaying an editable flow sequence and a component tool box on a test flow design page of the test case, wherein the component tool box comprises at least one packaged component tool, and each component tool comprises one or more preset test steps;
acquiring a dragging instruction for dragging a target component tool of the component tool box to the flow sequence, and adding a testing step of the target component tool into the flow sequence according to the dragging instruction;
after the process sequence is designed, designing test assertion;
and acquiring the numerical value of the index parameter according to the flow sequence, and applying the numerical value of the index parameter to finish assertion and output a test result.
2. The smoke test method of a test case according to claim 1, wherein:
designing the flow sequence further includes: creating a new test step in the flow sequence;
after the process sequence is designed, the method further comprises the following steps: the created new test steps are packaged into new component tools, which are added to the component toolbox.
3. The smoke test method of the test case according to claim 2, wherein:
adding the new component tool to the component toolbox comprises: a unique identification is created for the new component tool, which is marked in the component tool kit.
4. A smoke test method for a test case according to any one of claims 1 to 3, wherein:
designing the flow sequence further includes:
and acquiring an instruction for executing a selector, acquiring the content of a target page element by using the selector, and adding the content of the target page element into the flow sequence.
5. The smoke test method of the test case according to claim 4, wherein:
adding the content of the target page element to the flow sequence includes: and adding the content of the target page element into the currently edited component tool.
6. The smoke test method of test cases according to claim 5, wherein:
the test flow design page of the test case also displays an attribute window of the component tool;
adding the contents of the target page element to the currently edited component tool includes: and adding the content of the target page element into an attribute window corresponding to the currently edited component tool.
7. The smoke test method of the test case according to claim 4, wherein:
the step of applying the selector to obtain the content of the target page element comprises the following steps: and acquiring a click signal, and determining a target page element corresponding to the click position from a plurality of page elements by the selector according to the position of the click signal.
8. A smoke test method for a test case according to any one of claims 1 to 3, wherein:
acquiring the numerical value of the index parameter according to the flow sequence, and applying the numerical value of the index parameter to complete assertion and output a test result comprises:
and automatically acquiring the numerical value of the index parameter by using an RPA robot, executing the flow sequence by using the RPA robot and outputting the test result.
9. Computer device, characterized in that it comprises a processor and a memory, said memory storing a computer program which, when executed by the processor, implements the steps of the smoke test method of a test case according to any one of claims 1 to 8.
10. A computer readable storage medium having stored thereon a computer program characterized by: the computer program, when executed by a processor, performs the steps of the smoke testing method of the test case according to any one of claims 1 to 8.
CN202310202032.9A 2023-03-03 2023-03-03 Smoking test method, computer device and computer readable storage medium for test case Pending CN116361156A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310202032.9A CN116361156A (en) 2023-03-03 2023-03-03 Smoking test method, computer device and computer readable storage medium for test case

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310202032.9A CN116361156A (en) 2023-03-03 2023-03-03 Smoking test method, computer device and computer readable storage medium for test case

Publications (1)

Publication Number Publication Date
CN116361156A true CN116361156A (en) 2023-06-30

Family

ID=86932291

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310202032.9A Pending CN116361156A (en) 2023-03-03 2023-03-03 Smoking test method, computer device and computer readable storage medium for test case

Country Status (1)

Country Link
CN (1) CN116361156A (en)

Similar Documents

Publication Publication Date Title
US11983154B2 (en) Recipe management system
US7367006B1 (en) Hierarchical, rules-based, general property visualization and editing method and system
US20170192877A1 (en) Mobile application development and deployment
CN109690473B (en) Graphical programming method and device, computer storage medium and visual system
CN108830383B (en) Method and system for displaying machine learning modeling process
CN105224458A (en) A kind of database method of testing and system
CN110795085A (en) Mobile application visual editing method and tool
CN111797998A (en) Method and system for generating combined features of machine learning samples
CN110673842A (en) Visual programming method and system, storage medium and equipment
CN111722842A (en) Pipeline arranging method and device, electronic equipment and storage medium
CN113010359A (en) Bus test system generation method, system, device and storage medium
CN111191161B (en) Page display method, storage medium, electronic device and system
CN113515275A (en) WYSIWYG cloud industrial configuration software system and development method thereof
CN116361156A (en) Smoking test method, computer device and computer readable storage medium for test case
CN110895460A (en) Jenkins-based robot system integration method and device and terminal equipment
CN114238072A (en) HIL requirement design method, HIL requirement design device, computer equipment and storage medium
CN112486378B (en) Graph generation method, device, terminal and storage medium
CN114518875A (en) Graphical programming system and programming method thereof
CN112764357A (en) Engineering machinery simulation method, device, equipment and storage medium
JP7391269B1 (en) FA control program generation support program, FA control program generation support device, FA control program generation support method
CN116740301B (en) Three-dimensional virtual monitoring system and method and monitoring equipment
KR20130060523A (en) Data minig process automation system, method thereof and recordable medium storing the method
CN114840123A (en) Method and device for configuring process rules and electronic equipment
US10902181B2 (en) Program creation apparatus
CN114818557A (en) Differential line measuring method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination