CN111679977B - Method, equipment and storage medium for testing exact project unit based on Jest - Google Patents
Method, equipment and storage medium for testing exact project unit based on Jest Download PDFInfo
- Publication number
- CN111679977B CN111679977B CN202010477390.7A CN202010477390A CN111679977B CN 111679977 B CN111679977 B CN 111679977B CN 202010477390 A CN202010477390 A CN 202010477390A CN 111679977 B CN111679977 B CN 111679977B
- Authority
- CN
- China
- Prior art keywords
- test
- testing
- jest
- project
- function
- 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 112
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000006243 chemical reaction Methods 0.000 claims abstract description 10
- 230000006870 function Effects 0.000 claims description 45
- 238000009877 rendering Methods 0.000 claims description 16
- 239000003638 chemical reducing agent Substances 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 9
- 238000010998 test method Methods 0.000 claims description 8
- 230000009471 action Effects 0.000 claims description 6
- 102000004190 Enzymes Human genes 0.000 claims description 5
- 108090000790 Enzymes Proteins 0.000 claims description 5
- 238000004364 calculation method Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 claims description 5
- 238000013522 software testing Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 101100066896 Drosophila melanogaster cher gene Proteins 0.000 description 1
- 208000027697 autoimmune lymphoproliferative syndrome due to CTLA4 haploinsuffiency Diseases 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 235000020289 caffè mocha Nutrition 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 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/3676—Test management for coverage analysis
-
- 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
- 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/3692—Test management for test results analysis
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, equipment and a storage medium for testing a React project unit based on Jest, and belongs to the technical field of software testing. Comprising the following steps: s101, selecting a testing tool and a framework according to characteristics of a reaction project and unit testing requirements; s102, building a test environment; s103, writing a test case, providing corresponding test contents according to the file type of the act project, and executing a corresponding test strategy; s104, generating a test report; s105, unit testing is automated and integrated into the project. Aiming at the technical problems of high test cost, low code coverage rate and the like, the method can conduct targeted test, and reduces the test cost.
Description
Technical Field
The present invention relates to the field of software testing technologies, and in particular, to a method, an apparatus, and a storage medium for testing a reaction project unit based on Jest.
Background
Unit testing refers to checking and verifying the smallest testable unit in software. A complete unit test method will find many bugs at some stage of software development and the cost of modifying them is low. Testing software products early in the life cycle will result in the best assurance of efficiency and quality. In case a tested software unit is provided, the system integration process will be greatly simplified. The easier a piece of software writes to a unit test, the better its modular structure, the weaker the coupling between the modules. jest is a test framework pushed out by facebook, and integrates the functions of Mocha, chai, jsdom, sin and the like. The componentization and functional programming of the reaction are naturally suitable for unit testing; however, the conventional test method and tool are not suitable for unit test of the act project, and have the problems of high test cost, high test case writing difficulty, low test coverage rate and the like.
Disclosure of Invention
1. Technical problem to be solved by the invention
In order to overcome the technical problems, the invention provides a method, equipment and a storage medium for testing a React project unit based on Jest, which can conduct targeted testing and reduce testing cost.
2. Technical proposal
In order to solve the problems, the technical scheme provided by the invention is as follows:
a method for testing a React project unit based on Jest comprises the following steps: s101, selecting a testing tool and a framework according to characteristics of a reaction project and unit testing requirements; s102, building a test environment; s103, writing a test case, providing corresponding test contents according to the file type of the act project, and executing a corresponding test strategy; s104, generating a test report; s105, unit testing is automated and integrated into the project.
Optionally, the file types of the act item include UI components, logic components, actions, reducer, and tool functions.
Optionally, the step S101 is further: jest, enzyme, and babel-Jest are installed, adding "test: jest- -config. Jest. Js" to the script in package. Json.
Optionally, the test report includes code coverage, which is detected using a code coverage tool.
Optionally, the UI component adopts snapshot to test, and judges whether the rendering result of the UI component accords with the expectation of the last recorded storage result, and adopts a topmatchsnappshot method to compare the difference between the result to be generated and the last recorded storage result.
Optionally, the testing method of the logic component includes: declaring a replacement function, rendering the logic component by adopting a short method, judging whether the logic sub-component needs further rendering, if so, repeating the rendering process, and if not, adopting spyOn to mock the life cycle function of the logic component; testing the internal functions of the components, simulating events by adopting a simultaneity interface, and judging whether the functions on the tips are called, whether the parameters are correct, whether the logic component states are modified in anticipation or not and whether each dom node accords with expectations or not after triggering the events.
Optionally, the testing method of the reducer includes: and storing the corresponding data slice, or traversing the mock, checking whether the calculation is completed correctly, and if not, repeating traversing the mock.
Optionally, the testing method of the tool function is as follows: and introducing a function, calling the set parameters, and judging whether the return value of the function meets the expectations.
Furthermore, the present invention provides an apparatus comprising: one or more processors; a memory for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to perform the method as described above.
Accordingly, the present invention provides a storage medium storing a computer program which, when executed by a processor, implements a method as claimed in any one of the preceding claims.
3. Advantageous effects
Compared with the prior art, the technical scheme provided by the invention has the following beneficial effects:
the test cost is reduced, the writing difficulty of test cases is reduced, and the test coverage rate is improved.
Drawings
Fig. 1 is a schematic view of an apparatus structure according to the present invention.
FIG. 2 is a general architecture of the React project.
FIG. 3 is a flowchart of a method for testing a reactive project unit based on Jest according to an embodiment of the present invention.
Detailed Description
For a further understanding of the present invention, the present invention will be described in detail with reference to the drawings and examples.
The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the invention are shown in the drawings. The first, second, etc. words are provided for convenience in describing the technical scheme of the present invention, and have no specific limitation, and are all generic terms, and do not constitute limitation to the technical scheme of the present invention. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Example 1
The embodiment provides a method for testing a exact project unit based on Jest, as shown in fig. 3, including: s101, selecting a testing tool and a framework according to characteristics of a reaction project and unit testing requirements; s102, building a test environment; s103, writing a test case, providing corresponding test contents according to the file type of the act project, and executing a corresponding test strategy; s104, generating a test report; s105, unit testing is automated and integrated into the project.
The file types of the React item include UI components, logic components, actions, reducer, and tool functions. The step S101 is further: jest, enzyme, and babel-Jest are installed, adding "test: jest- -config. Jest. Js" to the script in package. Json. The test report includes code coverage, which is detected using a code coverage tool. And the UI component adopts a snapshot to test, judges whether the rendering result of the UI component accords with the expectation of the last recorded storage result, and compares the result to be generated with the last recorded storage result by adopting a toMatchSnapshot method. The testing method of the logic component comprises the following steps: declaring a replacement function, rendering the logic component by adopting a short method, judging whether the logic sub-component needs further rendering, if so, repeating the rendering process, and if not, adopting spyOn to mock the life cycle function of the logic component; testing the internal functions of the components, simulating events by adopting a simultaneity interface, and judging whether the functions on the tips are called, whether the parameters are correct, whether the logic component states are modified in anticipation or not and whether each dom node accords with expectations or not after triggering the events. The test method of the reducer comprises the following steps: and storing the corresponding data slice, or traversing the mock, checking whether the calculation is completed correctly, and if not, repeating traversing the mock. The testing method of the tool function comprises the following steps: and introducing a function, calling the set parameters, and judging whether the return value of the function meets the expectations.
In practical application, an alternative implementation mode aims at the problems of high writing difficulty of test cases of a reaction project unit, low test coverage rate and the like, and a common project architecture of a reaction project is shown in fig. 2. In order to write test cases more conveniently and reasonably, files in the project are divided into several types, and each type has the characteristics and unique test methods:
the UI component, namely a stateless pure function component, is tested by using a snapshot, the snapshot can test whether the rendering result of the component accords with the expectation, the expectation is the last recorded and stored result, and the toMatchSnapshot method can compare the result to be generated with the last time. It should be noted that a sufficiently robust test should cover all rendering cases, i.e. if the UI components render results according to the parameters entered by tips may differ, which must be written to cover multiple test cases.
Logic components, i.e., complex React components. Such components typically use the exact component lifecycle functions, internal management states and data, and different methods for testing these functional points are required. Testing logic component nodes, judging whether a sub logic component is rendered or not, and performing logic component rendering by using a shrllow method and then judging; testing the life cycle of the logic component, using spyOn to mock the life cycle function of the logic component, and declaring the proxy function before rendering the logic component; testing the internal functions of the logic component, simulating an event by mainly utilizing a simultaneity interface, and judging whether a specific function on the tips is called, whether the parameters are correct, whether the logic component state is modified in anticipation, and whether each dom node exists or not according with expectations after triggering the event.
The actions test, which is mainly concerned with whether or not an action object is correctly created, generally does not need to be tested, because the hierarchy is very simple and is generally not possible to make mistakes after the facility is set up.
The reducer test, there are roughly two types of reducer: the method is simple, and only corresponding data slices are stored one by one; some complex, with some computational logic inside. The reducer is used as a pure function, has definite input and output, contains service calculation, is very suitable for unit test, and is generally used for carrying out heavy logic processing in the reducer, so that the value of unit test protection is very high. The test method uses simple mechanical traversal mock to check whether the calculation is completed correctly.
The tool functions are pure functions in the ideal state, i.e. functions which do not depend on external states, do not change parameter values and do not maintain internal states. Such a function is also very efficient. The test method directly introduces the function, transfers specific parameters, and judges whether the return value of the function meets the expectations. It should be noted that the method is comprehensive, and each logic judgment of the guarantee function can be covered after all test cases run out.
1. Selecting a test tool and a frame
Jest is a front-end test framework of Facebook open source, mainly used for unit testing of real and real Native, and has been integrated in create-real-app. The Enzyme is a real test tool library with an Airbnb open source, provides a set of simple and powerful API, embeds Cheerio, realizes DOM processing in a jQuery style mode, and has very friendly development experience. The method has ultrahigh popularity in the open source community, and simultaneously, the recommended by the act authorities is also obtained.
2. Test environment construction
Jest, enzyme, and babel-Jest are installed, adding "test: jest- -config. Jest. Js" to the script in package. Json.
TABLE 1 File types in the React project and corresponding test contents and test policies
3. Writing test cases
Writing test cases according to the test method and the strategy, distinguishing files in the reaction project, wherein different types of files have different test contents and strategies, and as shown in table 1, components are logic components.
4. Generating unit test reports
In the test report, code coverage is a primary test indicator that describes whether code of a test case is executed. Statistical code coverage is typically achieved by means of a code coverage tool, jest integrating the Istanbull code coverage tool. There are four total measurement dimensions:
line coverage: whether each row of test cases is executed;
-function coverage (function coverage): whether each function of the test case is called;
branch coverage: whether each if code block of the test case is executed;
statement coverage (statement coverage): whether each statement of the test case is executed.
5. Integration into projects
After the reference unit tests in the project, the test case can be automatically run before the code is submitted when the file to be tested is hoped to be modified each time, so that the correctness and the robustness of the code are ensured. In the project, the task and the line-staged can be used for triggering the hooks of the git to perform some check before code submission.
Example 2
The present embodiment provides an apparatus comprising: one or more processors; a memory for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to perform the method as described above.
Further, the present embodiment provides a storage medium storing a computer program which, when executed by a processor, implements the method as described in embodiment 1 above.
Fig. 1 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
As shown in fig. 1, as another aspect, the present application also provides an apparatus 500 including one or more Central Processing Units (CPUs) 501, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM503, various programs and data required for the operation of the device 500 are also stored. The CPU501, ROM502, and RAM503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input section 506 including a keyboard, a mouse, and the like; an output portion 507 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The drive 510 is also connected to the I/O interface 505 as needed. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as needed so that a computer program read therefrom is mounted into the storage section 508 as needed.
In particular, according to embodiments of the present disclosure, the method described in any of the embodiments above may be implemented as a computer software program. For example, embodiments disclosed herein include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method described in any of the embodiments above. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 509, and/or installed from the removable media 511.
As yet another aspect, the present application also provides a computer-readable storage medium, which may be a computer-readable storage medium contained in the apparatus of the above-described embodiment; or may be a computer-readable storage medium, alone, that is not assembled into a device. The computer readable storage medium stores one or more programs for use by one or more processors in performing the methods described herein.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present application may be implemented by software, or may be implemented by hardware. The described units or modules may also be provided in a processor, for example, each of the units may be a software program provided in a computer or a mobile smart device, or may be separately configured hardware devices. Wherein the names of the units or modules do not in some cases constitute a limitation of the units or modules themselves.
The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the invention referred to in this application is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or their equivalents without departing from the spirit of the application. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.
Claims (3)
1. The method for testing the exact project unit based on Jest is characterized by comprising the following steps of:
s101, selecting a testing tool and a framework according to characteristics of a reaction project and unit testing requirements;
s102, building a test environment;
s103, writing a test case, providing corresponding test contents according to the file type of the act project, and executing a corresponding test strategy;
s104, generating a test report;
s105, automating and integrating the unit test into the project; the file types of the reaction item include UI components, logic components, actions, reducer, and tool functions;
the testing method of the logic component comprises the following steps: declaring a replacement function, rendering the logic component by adopting a short method, judging whether the logic sub-component needs further rendering, if so, repeating the rendering process, and if not, adopting spyOn to mock the life cycle function of the logic component; testing internal functions of the components, simulating events by adopting a simultate interface, and judging whether the functions on tips are called, whether the parameters are correct, whether the logic component states are modified in anticipation or not and whether each dom node accords with expectations or not after triggering the events;
the test method of the reducer comprises the following steps: save the corresponding data slice, or
Traversing the mock, checking whether calculation is completed correctly, and if not, repeating traversing the mock;
the testing method of the tool function comprises the following steps:
introducing a function, calling a set parameter, and judging whether a function return value accords with the expectation;
the step S101 is further: installing Jest, enzyme, and babel-Jest, adding "test: jest-config. Jest. Js" to the script in package. Json;
the test report comprises code coverage, and the code coverage is detected by a code coverage tool;
and the UI component adopts a snapshot to test, judges whether the rendering result of the UI component accords with the expectation of the last recorded storage result, and compares the result to be generated with the last recorded storage result by adopting a toMatchSnapshot method.
2. An apparatus, the apparatus comprising:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of claim 1.
3. A storage medium storing a computer program, which when executed by a processor implements the method of claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010477390.7A CN111679977B (en) | 2020-05-29 | 2020-05-29 | Method, equipment and storage medium for testing exact project unit based on Jest |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010477390.7A CN111679977B (en) | 2020-05-29 | 2020-05-29 | Method, equipment and storage medium for testing exact project unit based on Jest |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111679977A CN111679977A (en) | 2020-09-18 |
| CN111679977B true CN111679977B (en) | 2024-02-27 |
Family
ID=72452795
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010477390.7A Active CN111679977B (en) | 2020-05-29 | 2020-05-29 | Method, equipment and storage medium for testing exact project unit based on Jest |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111679977B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114546816A (en) * | 2020-11-25 | 2022-05-27 | 腾讯科技（深圳）有限公司 | Test method, test platform, test device, electronic equipment and storage medium |
| CN114661623B (en) * | 2022-05-26 | 2022-08-16 | 中建电子商务有限责任公司 | UI automatic test method for testing React Native application |
| CN117724988B (en) * | 2024-02-18 | 2024-05-10 | 杭州玳数科技有限公司 | UI component Library Testing method based on Testing Library, storage medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104834600A (en) * | 2015-04-28 | 2015-08-12 | 南京邮电大学 | Method for testing Android application controls |
| KR20160044305A (en) * | 2014-10-15 | 2016-04-25 | 삼성에스디에스 주식회사 | Apparatus and method for unit test of code |
| CN109446058A (en) * | 2018-09-12 | 2019-03-08 | 深圳点猫科技有限公司 | A kind of unit test method and electronic equipment for programming |
| CN110347378A (en) * | 2019-07-12 | 2019-10-18 | 北京明略软件系统有限公司 | The building method and device of item development environment |
| US10565093B1 (en) * | 2018-10-09 | 2020-02-18 | International Business Machines Corporation | Providing cognitive intelligence across continuous delivery pipeline data |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7730458B2 (en) * | 2004-04-23 | 2010-06-01 | Microsoft Corporation | Built-in diagnostics |
| US9792203B2 (en) * | 2013-11-14 | 2017-10-17 | Sap Se | Isolated testing of distributed development projects |
-
2020
- 2020-05-29 CN CN202010477390.7A patent/CN111679977B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20160044305A (en) * | 2014-10-15 | 2016-04-25 | 삼성에스디에스 주식회사 | Apparatus and method for unit test of code |
| CN104834600A (en) * | 2015-04-28 | 2015-08-12 | 南京邮电大学 | Method for testing Android application controls |
| CN109446058A (en) * | 2018-09-12 | 2019-03-08 | 深圳点猫科技有限公司 | A kind of unit test method and electronic equipment for programming |
| US10565093B1 (en) * | 2018-10-09 | 2020-02-18 | International Business Machines Corporation | Providing cognitive intelligence across continuous delivery pipeline data |
| CN110347378A (en) * | 2019-07-12 | 2019-10-18 | 北京明略软件系统有限公司 | The building method and device of item development environment |
Non-Patent Citations (6)
| Title |
|---|
| React单元测试策略及落地;Thoughtworks;《https://www.sohu.com/a/325448120_487103 》;第1-54页 * |
| react常用工具函数;上官不会飞;《https://blog.csdn.net/weixin_42588966/article/details/105339157》;第1-4页 * |
| 基于Jest+Enzyme的React单元测试;超人666;《https://segmentfault.com/a/1190000009220530/》;第1-16页 * |
| 填坑之路：Jest对React全家桶的单元测试;哦啦吧啦;《https://www.jianshu.com/p/ed4e0d551aae》;第1-21页 * |
| 用Jest来给React完成一次妙不可言的~单元测试;⽤户1462769;《https://cloud.tencent.com/developer/article/1606859》;第1-15页 * |
| 超人666.基于Jest+Enzyme的React单元测试.《https://segmentfault.com/a/1190000009220530/》.2017,第1-16页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111679977A (en) | 2020-09-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111679977B (en) | Method, equipment and storage medium for testing exact project unit based on Jest | |
| US9753838B2 (en) | System and method to classify automated code inspection services defect output for defect analysis | |
| US9201758B2 (en) | System and method for display of software quality | |
| US9317411B2 (en) | Testing coordinator | |
| US9411575B2 (en) | Systems and methods for quality assurance automation | |
| US10089218B2 (en) | Methods circuits apparatuses systems and associated computer executable code for generating a software unit test | |
| CN110674047B (en) | Software testing method and device and electronic equipment | |
| CN112131116B (en) | Automatic regression testing method for embedded software | |
| Oster | Feature model-based software product line testing | |
| CN115080433A (en) | Testing method and device based on flow playback | |
| CN112380118A (en) | Unit testing method, unit testing device, medium and electronic equipment | |
| CN111881025A (en) | Automatic test task scheduling method, device and system | |
| CN113010431B (en) | Java unit test case generation method and device | |
| CN111967961B (en) | Data mining method and device | |
| CN113360368B (en) | Method and device for testing software performance | |
| CN117130945B (en) | Test method and device | |
| CN107783905A (en) | The automated testing method and system sent based on simulation short message | |
| Kim et al. | The new approach to IT testing: real transaction-based automated validation solution | |
| CN114116519A (en) | Interface test method and device, electronic equipment and storage medium | |
| CN113886222A (en) | Test case design method, device and equipment and readable storage medium | |
| CN114579444A (en) | Automated testing method, automated testing device, electronic apparatus, storage medium, and program product | |
| CN114064484A (en) | Interface testing method and device, electronic equipment and readable storage medium | |
| CN117806943A (en) | Test method, test device and storage medium | |
| CN114003492A (en) | Demand test integrated generation method and device | |
| CN115687078A (en) | Test case evaluation method, test case evaluation apparatus, test case evaluation device, test case evaluation medium, and program product |
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 |