CN112631938B - Automatic regression testing method - Google Patents
Automatic regression testing method Download PDFInfo
- Publication number
- CN112631938B CN112631938B CN202011629214.7A CN202011629214A CN112631938B CN 112631938 B CN112631938 B CN 112631938B CN 202011629214 A CN202011629214 A CN 202011629214A CN 112631938 B CN112631938 B CN 112631938B
- Authority
- CN
- China
- Prior art keywords
- data
- test
- value
- variable
- regression testing
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 83
- 238000000034 method Methods 0.000 claims abstract description 56
- 230000005540 biological transmission Effects 0.000 claims 4
- 238000013515 script Methods 0.000 abstract description 7
- 230000009471 action Effects 0.000 abstract description 2
- 230000009286 beneficial effect Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
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/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method for automatic regression testing. The test cases are managed by an excel table, each test case is composed of a plurality of test steps, and each test step comprises test description, test objects, actions and test data. The repeated steps of the operation are individually packaged into individual keys. The test data are taken out individually and put in a table for management. How to acquire test data in excel, how to read test case information of an excel table, and the like, which are all implemented in an execution engine. The beneficial effects of the invention are as follows: the workload of writing scripts is reduced by half, test cases can be written by a tester without programming, and the threshold is low.
Description
Technical Field
The invention relates to the field of automatic testing, in particular to a method for automatic regression testing.
Background
The test data and the page elements are stored in an excel file, the test data and the page elements are read through the script, each step in the test cases is realized, one test case corresponds to one script, script development workload is very large, if the service changes, the corresponding script needs to be modified, the workload caused by the modification is added to an automatic test development engineer, and the maintenance cost is high.
Disclosure of Invention
The invention aims to overcome the defect of low efficiency in the prior art and provides a high-efficiency automatic regression testing method.
The aim of the invention is achieved by the following technical scheme: an automatic regression testing method, wherein an execution engine is connected with a test case by adopting a signal, the execution engine reads data in the test case, the data is operated in the execution engine according to a testing step, a plurality of repeated operation types are packaged into a plurality of keywords in the execution engine, the execution engine is connected with an application program by adopting a signal, the execution engine outputs the keywords to the application program, the sheet name storing the keywords is a keyword table, and a test object is placed in a table, the testing step also comprises a step description, an operation type, a test object and test data, and the sheet name storing the test case is steps; the sheet name for storing the test case is data; and storing the sheet name of the test object as elements.
Preferably, the execution engine reads the data, judges the corresponding relation between the data and the appointed browser in the configuration file, creates a corresponding browser driver, and creates a default driver without the corresponding browser driver.
Preferably, the execution engine acquires test data by taking out certain cell data as a key word from the beginning of initializing the number of columns to two and the number of rows to one, if the corresponding condition is met, the corresponding cell is put in the dictionary data as a value, and if the corresponding condition is not met, the dictionary data is added to the original test data.
The method comprises the steps of optimizing a table first behavior table head of a test case, wherein the number of initialization lines is one, if i meets a corresponding condition, calling a default running step to act on an ith running action, adding a default running step to continue calling the value of i to act on i+1 after each completion, and if the condition is not met, ending the circulation, wherein the default running step is placed in a corresponding statement module.
Optimally, the operation steps are placed in the corresponding modules, and the test data are placed in the data modules; the operation type is placed in the step type module, the operation type in the step type module meets different execution conditions, and each condition corresponds to a different execution method.
Optimally, the execution method acquires the value of the platform type from the test data, the browser opens the corresponding platform, inputs related information for login, throws out an abnormality if the login fails, and captures a screenshot by the corresponding program.
Optimally, the execution method needs to take out the page element from the file and put it in a variable, thus directly going to the variable to obtain when each operation is performed, reading the element from the first row, and ending the cycle when the number of rows of the table name is more than 1; and initializing an element dictionary when the number of lines of the table name is less than 1, reading the value of the corresponding cell to be assigned to the element variable, reading the value of the second column of the corresponding cell to be assigned to the finDBy variable, and reading the value of the third column of the corresponding cell to be assigned to the expression variable.
Optimally, judging whether the expression contains data or not, if the expression contains the variable, firstly, changing the variable into data, and then obtaining the element through the coding program in the corresponding positioning mode
Optimally, the page has a connection to exit the system, and can exit the system by finding and clicking the link.
The invention has the following advantages: the workload of writing scripts is reduced by half, test cases can be written by a tester without programming, and the threshold is low. .
Drawings
FIG. 1 is a schematic diagram of an execution engine workflow architecture;
FIG. 2 generates a driver structure schematic of a browser;
FIG. 3 is a schematic diagram of a method for acquiring test data;
FIG. 4 is a schematic diagram of a step structure of executing a test case;
FIG. 5 is a schematic structural diagram of the runStep method;
FIG. 6 is a schematic diagram of the method of loadElementFromSheet;
FIG. 7 is a schematic diagram of the method of getWebElementFromXls;
FIG. 8 is a schematic diagram of a process architecture implemented by the getWebElements (findBy, expression) method;
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, based on the embodiments of the invention, which are apparent to those of ordinary skill in the art without inventive faculty, are intended to be within the scope of the invention.
In addition, the embodiments of the present invention and the features of the embodiments may be combined with each other without collision.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the description of the present invention, it should be noted that, directions or positional relationships indicated by terms such as "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., are directions or positional relationships based on those shown in the drawings, or are directions or positional relationships conventionally put in use of the inventive product, or are directions or positional relationships conventionally understood by those skilled in the art, are merely for convenience of describing the present invention and for simplifying the description, and are not to indicate or imply that the apparatus or element to be referred to must have a specific direction, be constructed and operated in a specific direction, and thus should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and the like, are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance.
In the description of the present invention, it should also be noted that, unless explicitly specified and limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present invention will be understood in specific cases by those of ordinary skill in the art.
As shown in FIG. 1, an automated regression testing method is provided, an execution engine is connected with a test case by a signal, the execution engine reads data in the test case, the data is operated in the execution engine according to a testing step, a plurality of repeated operation types are packaged into a plurality of keywords in the execution engine, the execution engine is connected with an application program by a signal, the execution engine outputs the keywords to the application program, the table names of the stored keywords are keyword tables, and the test objects are placed in a table, wherein the testing step also comprises step description, operation types, test objects and test data, and the table names of the stored testing steps are step tables; the table name of the stored test case is a data table; the table name for storing the test object is a storage table.
In this embodiment, the execution engine reads the data, determines the correspondence between the data and the designated browser in the configuration file, and creates a corresponding browser driver, and creates a default driver without the corresponding browser driver, further, as shown in fig. 2, the configuration file designates the browser, determines whether the browsing form path is the designated browser, creates a driver of the google browser if the browsing form path is the designated browser, otherwise determines that the browsing form path is an fox browser, creates an fox browser driver if the browsing form path is the designated browser, otherwise determines that the browsing form path is an IE browser, creates an IE driver if the browsing form path is the designated browser, and creates an fox browser driver by default if the configuration file does not designate the browser.
In this embodiment, as shown in fig. 3, the execution engine acquires test data from the initialization column number of two and the line number of one, which corresponds to the subscript of the cell from 0 and 0, and the test data is placed in the third column, so the initialization value j is 2; the first row is the header, so data is fetched starting from the second row with an initialization value i of 1. Taking out the data of the cell (i, 1) as a key word, if the data meets the specified value of i < data, putting the cell (i, j) as a value in dictionary data, adding the dictionary data into a data list, and ending the cycle; j+1, j < data specified value is judged, if i=1 is satisfied, and if no, the loop is ended.
In this embodiment, as shown in fig. 4, since the sheet of the test case is the first table, initializing i=1, taking the operation step of the i-th line, calling the self.runstep method to execute, if i+1, judging whether i+1 satisfies i < self_stepsheet.nrows, if so, executing the self.runstep method, if not, ending the loop, putting the execution statement in the try statement block, capturing the exception by intercepting, and capturing the screenshot of the exception page.
In this embodiment, as shown in fig. 5, the runStep method is described as follows:
(1)self.currentStepRow＝stepRow
self.currentData＝data
stepType＝stepRow[1].value
the operation steps to be currently performed are placed in the self.currentsteprow variable, the test data are placed in the self currentdata variable, and the operation type is placed in the stepType variable.
(2) If steptype= = = 'logic', then the _dologic method is performed.
(3) If steptype= = 'page_action', then the_dopageaction method is performed.
(4) If steptype= = 'to_current_page', then the_to_current_page method is performed.
(5) If steptype= = 'click', then the _doclick method is performed.
(6) If steptype= = = 'input', then the _doinput method is performed.
(7) If steptype= = = 'wait', then the_dowait method is performed.
(8) If steptype= = = 'logo', then the _dologout method is performed.
(9) If steptype= = 'get_list_element', then the_get_list_element method is performed.
(10) If steptype= = = 'verify', then the _doverify method is performed.
For example, the first step in the test case is to log on the management platform, if the operation type is logic. The _doLogin method is implemented by acquiring a value of the platform_type from test data, and if the platform_type= manager, opening a management platform by a browser, inputting a user name, a password and a verification code, and clicking to log in. If the login fails, the exception is thrown. If the platform logs in other platforms, the processing mode is the same; if the operation type is page_action, the description is to call the packaged repeated operation, the first parameter is an Excel file where the repeated operation to be called is located, the second parameter is a sheet where the repeated operation is located, the sheet where the repeated operation is located is found, if the elements exist, the data in the elements are read by using a_loadelementfrom sheet method, then the operation steps are sequentially read, and a runStep method is called for execution.
In this embodiment, as shown in fig. 6, the loadelementfrom sheet method requires that the description, the element name, the location mode, and the expression of the page element be placed in elements in an excel file, and when the page is to be operated, the page element needs to be fetched from the file and placed in a variable, so that the page element is directly fetched from the variable every time the operation is performed, and the page element does not need to be fetched from the file every time the operation is performed. Reading element i=1 from the first row, the webentitssheet. Nros represents the number of rows of sheets, and the loop ends when i > elementsssheet. Nrows; when i < elementssheet. Nrows, initializing an element dictionary, reading the value assignment of the corresponding cell to the element variable, reading the value assignment of the second column of the corresponding cell to the finDBy variable, reading the value assignment of the third column of the corresponding cell to the expression variable, corresponding to the value assignment of the reading cell (i, 1) to the elementName variable, the value assignment of the reading cell (i, 2) to the findBy variable, and the value assignment of the reading cell (i, 3) to the expression variable. If the fileName parameter is transmitted when the method is called, the fileName is required to be added when the elementName is used as a key, otherwise, the fileName is not required to be added, and the element is stored in self_elementsFromXLs as a value. Further, if the operation type is to_current_page, the method of_to_current_page is executed, and the method is used for entering the Page to be tested, and because each Page to be tested needs to find the test Page, the test Page is packaged into a keyword, and each time the keyword is directly called. The code is as follows:
toMenu＝self._getWebElementFromXls(self._getCellValue(2)
ActionChains(self._driver).move_to_element(toMenu).perform()
clickMenu＝self._getWebElementFromXls(self._getCellValue(3))
clickMenu.click()
interpretation: the getWebElementFromXls () method is to obtain the real elements of the page from the element names of the cells. The performance () and click () methods operate on elements.
In this embodiment, as shown in fig. 7, the_getwebelementfromxls () method first determines whether the parameter elementName exists in self_elementsfromxls, and if so, takes out the value corresponding to the elementName and puts it into the findByExpression variable; if not, judging whether the elementName contains an |symbol, if the condition is met, taking out a file name in front of the |symbol from the elementName, opening the file, taking out all element information of an elementpage in the file, putting the element information into self_elementsFromXLs, taking out a value corresponding to the elementName, putting the value into a findByExpress variable, and further taking out a value of findBy from the findByExpress, and putting the value into a findBy variable. The value of expression is fetched from findByExpression and put into the expression variable, and then the_getWebelements (findBy, expression) method is called to obtain the element.
In this embodiment, as shown in fig. 8, the_getwebelements (find, expression) method is used to locate an element, if the location mode is xpath, it needs to determine whether the expression contains data, if the expression contains a description expression contains a variable, it needs to change the variable into data first, and then locate the element in xpath; if the positioning mode is id, obtaining an element by the mode of elements=self_driver.find_elements_by_ id (expression); if the positioning mode is className, obtaining an element by the mode of elements=self_driver. If the positioning mode is linkText, obtaining an element by the mode of elements=self_driver. If the positioning mode is cssSelect, the element is obtained by the mode of element=self_driver_find_elements_by_css_ selector (expression), further, if the operation type is input, the_doInput () method is executed, firstly) the extraction parameter 1 is placed in the element name variable, the element is obtained by calling the self_ getWebElementFromXls (elementName) method and placed in the element variable, the element is clicked by element_click (), the element is emptied by the element_clear () method, finally the content in the element_key (self_getValue (3)) is executed, the test data is obtained by calling the_getCellValue () method, then the element is assigned by the sensor_key () method, and the further_getValue method code is as follows:
def_getCellValue(self,cellIndex):
value＝self.currentStepRow[cellIndex].value
if(isinstance(value,float)):
value＝str(value)
if(value.find('data:')>-1):
value＝self.currentData[value.replace('data:',”)]
if(isinstance(value,float)):
value＝str(value)
return value
if the operation type is click, then the _doclick method is performed:
def_doClick(self):
elementName＝self._getCellValue(2)
element＝self._getWebElementFromXls(elementName)
sleep(3)
self._driver.execute_script("arguments[0].click()；",element)
if the operation type is verify, executing a _dorverify method, firstly acquiring a verification type and an expected result from the operation step, if the expected result is the same as the actual result, executing the test case successfully, and if the expected result is different from the actual result, throwing out an exception; if the operation type is logo, then the _dologo method is executed, which is used to exit the system. And if the link which exits the system exists in the page, the system can be exited by finding the link and clicking.
Although the present invention has been described with reference to the foregoing embodiments, it will be apparent to those skilled in the art that modifications may be made to the embodiments described, or equivalents may be substituted for elements thereof, and any modifications, equivalents, improvements and changes may be made without departing from the spirit and principles of the present invention.
Claims (6)
1. A method of automated regression testing, characterized by: the execution engine is connected with the test case by adopting a signal, reads data in the test case, enables the data to operate in the execution engine according to the test steps, encapsulates a plurality of repeated operation types into a plurality of keywords in the execution engine, and is connected with the application program by adopting a signal, outputs the keywords to the application program, stores the table names of the keywords as keyword tables and places the keywords and the test objects in one table, wherein the test steps also comprise step descriptions, operation types, test objects and test data, and stores the table names of the test steps as step tables; the table name of the stored test case is a data table; the table names of the test objects are stored as the stored table, the table of the test case is the first table head, so the number of the initialized rows is one, if i meets the corresponding condition, a default operation step is called to act on the i-th running, after each completion, the value of i is added with one and then the default operation step is continuously called to act on i+1, if the condition is not met, the circulation is ended, the default operation step is placed in the corresponding statement module, the operation step is placed in the corresponding module, and the test data is placed in the data module; the operation type is placed in a step type module, the operation type in the step type module meets different execution conditions, each condition corresponds to different execution methods, the execution methods acquire the value of the platform type from test data, a browser opens a corresponding platform, inputs relevant information to log in, if the log in fails, an exception is thrown out, a screenshot is captured by a corresponding program, page elements are required to be taken out of a file and placed in a variable, thus the operation methods are directly carried out in the variable in each operation, the elements are read from the first row, and the cycle is ended when the number of lines of the table name is more than 1; and initializing the element dictionary when the number of lines of the table names is less than 1, reading the value assignment of the corresponding cell to the element variable, reading the value assignment of the second column of the corresponding cell to the edit variable, and reading the value assignment of the third column of the corresponding cell to the complex variable.
2. The method of automated regression testing of claim 1 wherein: and the execution engine reads the data, judges the corresponding relation between the data and the appointed browser in the configuration file, creates a corresponding browser driver, and creates a default driver without the corresponding browser driver.
3. The method of automated regression testing of claim 2 wherein: the execution engine acquires test data by taking out certain cell data as a key word from the beginning of initializing the number of columns to be two and the number of rows to be one, if the corresponding condition is met, the corresponding cell is taken as a value to be placed in dictionary data, and if the corresponding condition is not met, the dictionary data is added to the original test data.
4. The method of automated regression testing of claim 1 wherein: the method comprises the steps of firstly judging whether a parameter transmission element name exists, taking out a corresponding value and putting the value into a variable if the parameter transmission element name exists, judging whether the element name exists with an 'sign' or not if the parameter transmission element name does not exist, taking out a file name in front of the 'sign' from the element name if the parameter transmission element name exists, opening a file, taking out all element information and putting the all element information into a storage table, taking out an edited value from an edited complex storage table and putting the edited value into an edited variable, taking out a complex value from the edited complex storage table and putting the complex value into a complex variable, and calling a related execution method to obtain elements.
5. The method of automated regression testing of claim 1 wherein: whether the expression contains data or not is judged first, if the expression contains the variable, the variable is needed to be changed into the data, and then the element is obtained through the coding program by the corresponding positioning mode.
6. The method of automated regression testing of claim 1 wherein: the page has a link to exit the system, find the link and click, exit the system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011629214.7A CN112631938B (en) | 2020-12-31 | 2020-12-31 | Automatic regression testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011629214.7A CN112631938B (en) | 2020-12-31 | 2020-12-31 | Automatic regression testing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112631938A CN112631938A (en) | 2021-04-09 |
| CN112631938B true CN112631938B (en) | 2024-02-09 |
Family
ID=75290620
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011629214.7A Active CN112631938B (en) | 2020-12-31 | 2020-12-31 | Automatic regression testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112631938B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114780425A (en) * | 2022-04-30 | 2022-07-22 | 重庆长安新能源汽车科技有限公司 | Method for designing hardware-in-loop automatic test case of vehicle control unit |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1877544A (en) * | 2005-06-06 | 2006-12-13 | 华为技术有限公司 | Keyword-driven automatic testing system and method |
| CN101996131A (en) * | 2009-08-19 | 2011-03-30 | 航天信息股份有限公司 | Automatic test method and automatic test platform for graphic user interface (GUI) based on x extensive makeup language (XML) packaging key word |
| CN104484269A (en) * | 2014-11-27 | 2015-04-01 | 北京广利核系统工程有限公司 | Method for automatically generating testing script |
| CN105912460A (en) * | 2016-04-05 | 2016-08-31 | 浪潮电子信息产业股份有限公司 | Software test method and system based on QTP |
| CN108536584A (en) * | 2018-03-12 | 2018-09-14 | 广东睿江云计算股份有限公司 | A kind of automated testing method based on Sikuli |
| CN109766280A (en) * | 2019-01-16 | 2019-05-17 | 广东飞企互联科技股份有限公司 | Method for testing software and software test platform |
| CN110750441A (en) * | 2019-09-06 | 2020-02-04 | 平安健康保险股份有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN110765012A (en) * | 2019-10-15 | 2020-02-07 | 北京信安世纪科技股份有限公司 | Automatic test script generation and analysis execution method |
| CN111061526A (en) * | 2019-10-12 | 2020-04-24 | 平安普惠企业管理有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN111240968A (en) * | 2020-01-06 | 2020-06-05 | 苏州浪潮智能科技有限公司 | Automatic test management method and system |
| CN111338970A (en) * | 2020-03-25 | 2020-06-26 | 广州棒谷科技股份有限公司 | WEB-side keyword-driven UI (user interface) automatic testing method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10838848B2 (en) * | 2017-06-01 | 2020-11-17 | Royal Bank Of Canada | System and method for test generation |
-
2020
- 2020-12-31 CN CN202011629214.7A patent/CN112631938B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1877544A (en) * | 2005-06-06 | 2006-12-13 | 华为技术有限公司 | Keyword-driven automatic testing system and method |
| CN101996131A (en) * | 2009-08-19 | 2011-03-30 | 航天信息股份有限公司 | Automatic test method and automatic test platform for graphic user interface (GUI) based on x extensive makeup language (XML) packaging key word |
| CN104484269A (en) * | 2014-11-27 | 2015-04-01 | 北京广利核系统工程有限公司 | Method for automatically generating testing script |
| CN105912460A (en) * | 2016-04-05 | 2016-08-31 | 浪潮电子信息产业股份有限公司 | Software test method and system based on QTP |
| CN108536584A (en) * | 2018-03-12 | 2018-09-14 | 广东睿江云计算股份有限公司 | A kind of automated testing method based on Sikuli |
| CN109766280A (en) * | 2019-01-16 | 2019-05-17 | 广东飞企互联科技股份有限公司 | Method for testing software and software test platform |
| CN110750441A (en) * | 2019-09-06 | 2020-02-04 | 平安健康保险股份有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN111061526A (en) * | 2019-10-12 | 2020-04-24 | 平安普惠企业管理有限公司 | Automatic testing method and device, computer equipment and storage medium |
| CN110765012A (en) * | 2019-10-15 | 2020-02-07 | 北京信安世纪科技股份有限公司 | Automatic test script generation and analysis execution method |
| CN111240968A (en) * | 2020-01-06 | 2020-06-05 | 苏州浪潮智能科技有限公司 | Automatic test management method and system |
| CN111338970A (en) * | 2020-03-25 | 2020-06-26 | 广州棒谷科技股份有限公司 | WEB-side keyword-driven UI (user interface) automatic testing method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112631938A (en) | 2021-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100461197C (en) | Automatic analysis system and method for malicious code | |
| CN101241467B (en) | Automatized white box test system and method facing to WEB application | |
| CN106445811B (en) | A kind of automatization test system and method based on SecureCRT | |
| CN110716870B (en) | Automatic service testing method and device | |
| US20100115496A1 (en) | Filter generation for load testing managed environments | |
| Marchetto et al. | A case study-based comparison of web testing techniques applied to AJAX web applications | |
| Hemmati et al. | Prioritizing manual test cases in rapid release environments | |
| CN103034575B (en) | Collapse analytical approach and device | |
| CN103186467B (en) | Data correctness verification method and device | |
| CN106682036A (en) | Data exchange system and exchange method thereof | |
| CN103049373B (en) | A kind of localization method of collapse and device | |
| CN112631938B (en) | Automatic regression testing method | |
| CN106227654A (en) | A kind of test platform | |
| CN108228464A (en) | A kind of mobile application UI test frames and its implementation based on data-driven | |
| CN110069736A (en) | Page loading method and equipment | |
| US8381185B2 (en) | Apparatus, system, and method for dynamic module flow analysis | |
| CN107832176A (en) | Hard disk pressure automatic test approach and system under a kind of Windows | |
| CN102521132A (en) | Automated testing method and automated testing system for real-time output logs | |
| CN116955207A (en) | Automatic test method, system and medium for identifying software and hardware completed by test case | |
| CN115514677B (en) | Method and system for server dial testing | |
| CN112084108A (en) | Test script generation method and device and related components | |
| CN108021431A (en) | Method and its system based on web data interactive maintenance Hive | |
| CN113485919B (en) | Test method, test device, and computer-readable storage medium | |
| CN115934559A (en) | Testing method of intelligent form testing system | |
| CN109144867A (en) | A kind of test method and test macro |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |