Cypress Commands – UI Interaction Commands
注明本文转载于:https://www.toolsqa.com/cypress/cypress-commands-ui-interaction-commands/
Cypress Commands – UI Interaction Commands
Each UI automation tool provides some APIs or methods to interact with the web elements, so the designated operation can be performed on the UI element. In addition to this, these methods also assist in the needed user journey simulation. Continuing the same practice, Cypress also provides Cypress Commands – UI Interaction Commands which can simulate the user’s interaction with the application.
Subsequently, in this article, we will be covering details of all those commands. Additionally, we will also know how cypress processes these commands on each element, in the following sections:
- What are the UI interaction commands provided by Cypress?
- Click Command
- Double Command
- Right Click Command
- Type Command
- Clear Command
- Check/UnCheck Command
- Select Command
- Trigger Command
- What Cypress performs checks/Actions for each UI action?
Cypress Commands – UI Interaction Commands?
There are multiple commands which Cypress provides, which fires the events a browser would fire. Moreover, they simulate the user’s behavior of interacting with the application under test. Some of these commands are:
Cypress – Click Command
.click() command: The click() command clicks any DOM element. Moreover, one can invoke it using the following syntaxes:
1 2 3 4 5 6 7 8 9 10 11 |
.click() // Syntax 1 .click(options) // Syntax 2 .click(position) //Syntax 3 .click(position, options) //Syntax 4 .click(xCoordinate, yCoordinate) // Syntax 5 .click(xCoordinate, yCoordinate, options) // Syntax 6 |
Where,
Options: The possible values for the “Option” parameter are:
Option |
Default |
Description |
log |
true |
It prints the command in the command log. |
force |
false |
It forces the action. |
multiple |
false |
Serially click multiple elements |
timeout |
defaultCommandTimeout |
Time to wait for |
Positions: The possible values for the “Position” parameter are:
- center (Default value)
- topLeft
- top
- topRight
- left
- right
- bottomLeft
- bottom
- bottomRight
Let’s understand the details and usage of click method with the help of the following examples:
For Example:
1 2 3 4 5 6 7 8 9 10 11 |
cy.get('button1').click() // Example 1 cy.get('button').click({ force: true }) // Example 2 cy.get('button').click('topRight') // Example 3 cy.get('button').click(5, 60, { force: true }) // Example 4 cy.get('button').click(15, 40) // Example 5 cy.get('button').click(5, 60, { force: true }) // Example 6 |
Cypress – Double Click Command
.dblclick() command: The dblclick() command double clicks on a DOM element. Additionally, one can invoke it using the following syntaxes:
1 2 3 4 5 6 7 8 9 10 11 |
.dblclick() // Syntax 1 .dblclick(options) // Syntax 2 .dblclick(position) // Syntax 3 .dblclick(position, options) // Syntax 4 .dblclick(x, y) // Syntax 5 .dblclick(x, y, options) // Syntax 6 |
Where,
Options: It accepts the same options, as mentioned in the “.click()” command above.
Positions: It accepts the same options, as mentioned in the “.click()” command above.
Let’s understand the details and usage of “dblclick” method with the help of the following examples:
For Example:
1 2 3 4 5 6 7 8 9 10 11 |
cy.get('button').dblclick() // Example 1 cy.get('button').dblclick({ force: true }) //Example 2 cy.get('button').dblclick('bottom') // Example 3 cy.get('button').dblclick('bottom', { force: true }) //Example 4 cy.get('button').dblclick(15, 20, { force: true }) //Example 5 cy.get('button').dblclick(15, 20, { multiple: false }) //Example 6 |
Cypress – Right Click Command
.rightclick() command: The rightclick() command right-clicks a DOM element. Moreover, one can invoke it using the following syntaxes:
1 2 3 4 5 6 7 8 9 10 11 |
.rightclick() // Syntax 1 .rightclick(options) // Syntax 2 .rightclick(position) // Syntax 3 .rightclick(position, options) // Syntax 4 .rightclick(x, y) // Syntax 5 .rightclick(x, y, options) // Syntax 6 |
Where,
Options: It accepts the same options, as mentioned in the “.click()” command above.
Positions: It accepts the same options, as mentioned in the “.click()” command above.
Let’s understand the details and usage of “rightclick()” method with the help of the following examples:
For Example:
1 2 3 4 5 6 7 8 9 10 11 |
cy.get('button').rightclick() // Example 1 cy.get('button').rightclick({ force: true }) //Example 2 cy.get('button').rightclick('bottom') // Example 3 cy.get('button').rightclick('bottom', { force: true }) //Example 4 cy.get('button').rightclick(15, 20, { force: true }) //Example 5 cy.get('button').rightclick(15, 20, { multiple: false }) //Example 6 |
Cypress – Type Command
.type() command: The type() command types into a DOM element. Additionally, one can invoke it using the following syntaxes:
1 2 3 |
.type(text) // Syntax 1 .type(text, options) // Syntax 2 |
Where,
Options: The possible values for the “Options” parameter are:
Option |
Default |
Description |
log |
true |
Displays the command in the Command log. |
delay |
10 |
Delay in secs after each keypress |
force |
false |
Forces the action. Additionally, it disables waiting for actionability. |
parseSpecialCharSequences |
true |
Parse special characters for strings surrounded by |
release |
true |
Keep a modifier activated between commands. |
timeout |
defaultCommandTimeout |
Time to wait for |
Let’s understand the details and usage of “type()” method with the help of the following examples:
For Example:
1 2 3 |
cy.get('input').type('Hello, World') // Example 1 cy.get('input').type('Hello, World', { force: true }) // Example 2 |
Cypress – Clear Command
.clear() command: This command clears the values of input or text-area. Additionally, the invoking of clear() command happens using the following syntaxes:
1 2 3 |
.clear() // Syntax 1 .clear(options) // Syntax 2 |
Where,
Options: The possible values for the “Options” parameter are:
Option |
Default |
Description |
log |
true |
Displays the command in the Command log |
force |
false |
Forces the action, disables waiting for actionability |
timeout |
defaultCommandTimeout |
Time to wait for |
Let’s understand the details and usage of “clear()” method with the help of the following examples:
For Example:
1 2 3 |
cy.get('textarea').clear() // Example 1 cy.get('input').clear({ force: true }) // Example 2 |
Cypress – Check/UnCheck Command
.check()/.uncheck command: These methods are used to check/uncheck checkboxes and radio buttons. Moreover, following syntaxes invoke these commands:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
// check() command syntax: .check() // Syntax 1 .check(value) // Syntax 2: Value of checkbox or radio that should be checked. .check(values) // Syntax 3: Values of checkboxes or radios that should be checked. .check(options) // Syntax 4 .check(value, options) // Syntax 5 .check(values, options) // Syntax 6 // uncheck() command syntax .uncheck() // Syntax 1 .uncheck(value) // Syntax 2: Value of checkbox or radio that should be unchecked. .uncheck(values) // Syntax 3: Values of checkboxes or radios that should be unchecked. .uncheck(options) // Syntax 4 .uncheck(value, options) // Syntax 5 .uncheck(values, options) // Syntax 6 |
Where,
Options: The possible values for the “Options” parameter are:
Option |
Default |
Description |
log |
true |
Displays the command in the Command log |
force |
false |
Forces the action, disables waiting for actionability |
timeout |
defaultCommandTimeout |
Time to wait for |
Let’s understand the details and usage of “check() and uncheck()” methods with the help of the following examples:
For Example:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
// check() commands examples cy.get('[type="checkbox"]').check() // Example 1 cy.get('[type="radio"]').check() cy.get('[type="radio"]').check('US') // Example 2 cy.get('[type="checkbox"]').check(['ga', 'ca']) // Example 3 cy.get('.action-checkboxes').should('not.be.visible') .check({ force: true }).should('be.checked') // Example 4 // uncheck() commands examples cy.get('[type="checkbox"]').uncheck() // Example 1 cy.get('[type="radio"]').uncheck() cy.get('[type="radio"]').uncheck('US') // Example 2 cy.get('[type="checkbox"]').uncheck(['ga', 'ca']) // Example 3 cy.get('.action-checkboxes').should('not.be.visible') .uncheck({ force: true }).should('be.unchecked') // Example 4 |
Cypress – Select Command
.select command: The select() command selects an option within <select> tags. Additionally, one can invoke it using the following syntaxes:
1 2 3 4 5 6 7 |
.select(value) // Syntax 1 .select(values) // Syntax 2 .select(value, options) // Syntax 3 .select(values, options) // Syntax 4 |
Where,
Options: It accepts the same options, as mentioned in the “.click()” command above.
Let’s understand the details and usage of “select()” method with the help of the following examples:
For Example:
1 2 3 4 5 |
cy.get('select').select('apples') // Example 1 cy.get('select').select(['apples', 'bananas']) // Example 2 cy.get('select').select('apples', { force: true }) // Example 3 |
Cypress – Trigger Command
.trigger command: The trigger() command triggers an event on a DOM element. Additionally, one can invoke it using the following syntaxes:
1 2 3 4 5 6 7 8 9 10 11 |
.trigger(eventName) // Syntax 1 .trigger(eventName, position) // Syntax 2 .trigger(eventName, options) // Syntax 3 .trigger(eventName, x, y) // Syntax 4 .trigger(eventName, position, options) // Syntax 5 .trigger(eventName, x, y, options) // Syntax 6 |
Where,
Options: The possible values for the “Options” parameter are:
Option |
Default |
Description |
log |
true |
It displays the command in the Command log. |
force |
false |
Forces the action. Additionally, it disables waiting for actionability. |
bubbles |
true |
Whether the event bubbles |
cancelable |
true |
Whether the event is cancelable |
timeout |
defaultCommandTimeout |
Time to wait for |
Let’s comprehend the details and usage of “trigger()” method with the help of the following examples:
For Example:
1 2 3 4 5 6 7 8 9 10 11 |
cy.get('a').trigger('mousedown') // Example 1 cy<span class="token punctuation">.</span><span class="token keyword">get</span><span class="token punctuation">(</span><span class="token string">'button'</span><span class="token punctuation">)</span><span class="token punctuation">.</span><span class="token function">trigger</span><span class="token punctuation">(</span><span class="token string">'mousedown'</span><span class="token punctuation">,</span> <span class="token string">'topRight'</span><span class="token punctuation">) // Example 2 cy.<span class="token keyword">get</span>(<span class="token string">'button'</span>).<span class="token function">trigger</span>(<span class="token string">'mouseover'</span>, { bubbles: <span class="token boolean">false</span> }) // Example 3 cy.<span class="token keyword">get</span>(<span class="token string">'button'</span>).<span class="token function">trigger</span>(<span class="token string">'mouseup'</span>, <span class="token number">15</span>, <span class="token number">40</span>) // Example 4 cy.<span class="token keyword">get</span>(<span class="token string">'button'</span>).<span class="token function">trigger</span>(<span class="token string">'mouseup'</span>, <span class="token string">topRight,</span><span class="token number"> { bubbles: <span class="token boolean">false</span> }</span>) // Example 5 </span> <span class="token punctuation">cy.<span class="token keyword">get</span>(<span class="token string">'button'</span>).<span class="token function">trigger</span>(<span class="token string">'mouseup'</span>, <span class="token number">15</span>, <span class="token number">40, { bubbles: <span class="token boolean">false</span> }</span>) // Example 6</span> |
What Cypress performs Checks/Actions for each UI action?
Cypress performs some pre-checks and actions before it issues any of the commands, as mentioned above. Additionally, these pre-checks and actions ensure that the element is ready for receiving the planned action. Few of these checks and actions are:
- Firstly, it ensures that no element is hidden.
- Secondly, it ensures that the element is not disabled.
- Thirdly, it ascertains that the element is not detached.
- Fourthly, it ensures that the element is not read-only.
- In addition to the above, it ensures that the element is not animating.
- Sixthly, it makes sure that the element is not covered.
- Moreover, it scrolls the element in port-view.
- Finally, it scrolls the element to fix the position if covered by another element.
So, these are few of the validations and actions that Cypress tries in-built to ensure that the element is actionable. Still, if Cypress is not able to interact with the element, it will raise an error mentioning the exact reason why the element was not actionable.
Let’s understand the usage of all these UI interaction commands with the help of following code snippet :
For Example,
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 |
/// <reference types="Cypress" /> describe('Actions', () => { // https://on.cypress.io/interacting-with-elements it('.type() - type into a DOM element', () => { cy.visit('https://example.cypress.io/commands/actions') cy.get('.action-email') .type('fake@email.com').should('have.value', 'fake@email.com') // .type() with special character sequences .type('{leftarrow}{rightarrow}{uparrow}{downarrow}') .type('{del}{selectall}{backspace}') // .type() with key modifiers .type('{alt}{option}') //these are equivalent .type('{ctrl}{control}') //these are equivalent .type('{meta}{command}{cmd}') //these are equivalent .type('{shift}') // Delay each keypress by 0.1 sec .type('slow.typing@email.com', { delay: 100 }) .should('have.value', 'slow.typing@email.com') cy.get('.action-disabled') // Ignore error checking prior to type // like whether the input is visible or disabled .type('disabled error checking', { force: true }) .should('have.value', 'disabled error checking') }) it('.focus() - focus on a DOM element', () => { // https://on.cypress.io/focus cy.get('.action-focus').focus() .should('have.class', 'focus') .prev().should('have.attr', 'style', 'color: orange;') }) it('.blur() - blur off a DOM element', () => { // https://on.cypress.io/blur cy.get('.action-blur').type('About to blur').blur() .should('have.class', 'error') .prev().should('have.attr', 'style', 'color: red;') }) it('.clear() - clears an input or textarea element', () => { // https://on.cypress.io/clear cy.get('.action-clear').type('Clear this text') .should('have.value', 'Clear this text') .clear() .should('have.value', '') }) it('.submit() - submit a form', () => { // https://on.cypress.io/submit cy.get('.action-form') .find('[type="text"]').type('HALFOFF') cy.get('.action-form').submit() .next().should('contain', 'Your form has been submitted!') }) it('.click() - click on a DOM element', () => { cy.get('.action-btn').click() // You can click on 9 specific positions of an element: // ----------------------------------- // | topLeft top topRight | // | | // | | // | | // | left center right | // | | // | | // | | // | bottomLeft bottom bottomRight | // ----------------------------------- // clicking in the center of the element is the default cy.get('#action-canvas').click() cy.get('#action-canvas').click('topLeft') cy.get('#action-canvas').click('top') cy.get('#action-canvas').click('topRight') cy.get('#action-canvas').click('left') cy.get('#action-canvas').click('right') cy.get('#action-canvas').click('bottomLeft') cy.get('#action-canvas').click('bottom') cy.get('#action-canvas').click('bottomRight') // .click() accepts an x and y coordinate // that controls where the click occurs :) cy.get('#action-canvas') .click(80, 75) // click 80px on x coord and 75px on y coord .click(170, 75) .click(80, 165) .click(100, 185) .click(125, 190) .click(150, 185) .click(170, 165) // click multiple elements by passing multiple: true cy.get('.action-labels>.label').click({ multiple: true }) // Ignore error checking prior to clicking cy.get('.action-opacity>.btn').click({ force: true }) }) it('.dblclick() - double click on a DOM element', () => { cy.get('.action-div').dblclick().should('not.be.visible') cy.get('.action-input-hidden').should('be.visible') }) it('.check() - check a checkbox or radio element', () => { // By default, .check() will check all // matching checkbox or radio elements in succession, one after another cy.get('.action-checkboxes [type="checkbox"]').not('[disabled]') .check().should('be.checked') cy.get('.action-radios [type="radio"]').not('[disabled]') .check().should('be.checked') // .check() accepts a value argument cy.get('.action-radios [type="radio"]') .check('radio1').should('be.checked') // .check() accepts an array of values cy.get('.action-multiple-checkboxes [type="checkbox"]') .check(['checkbox1', 'checkbox2']).should('be.checked') // Ignore error checking prior to checking cy.get('.action-checkboxes [disabled]') .check({ force: true }).should('be.checked') cy.get('.action-radios [type="radio"]') .check('radio3', { force: true }).should('be.checked') }) it('.uncheck() - uncheck a checkbox element', () => { // By default, .uncheck() will uncheck all matching // checkbox elements in succession, one after another cy.get('.action-check [type="checkbox"]') .not('[disabled]') .uncheck().should('not.be.checked') // .uncheck() accepts a value argument cy.get('.action-check [type="checkbox"]') .check('checkbox1') .uncheck('checkbox1').should('not.be.checked') // .uncheck() accepts an array of values cy.get('.action-check [type="checkbox"]') .check(['checkbox1', 'checkbox3']) .uncheck(['checkbox1', 'checkbox3']).should('not.be.checked') // Ignore error checking prior to unchecking cy.get('.action-check [disabled]') .uncheck({ force: true }).should('not.be.checked') }) it('.select() - select an option in a <select> element', () => { // Select option(s) with matching text content cy.get('.action-select').select('apples') cy.get('.action-select-multiple') .select(['apples', 'oranges', 'bananas']) // Select option(s) with matching value cy.get('.action-select').select('fr-bananas') cy.get('.action-select-multiple') .select(['fr-apples', 'fr-oranges', 'fr-bananas']) }) it('.scrollIntoView() - scroll an element into view', () => { // normally all of these buttons are hidden, // because they're not within // the viewable area of their parent // (we need to scroll to see them) cy.get('#scroll-horizontal button') .should('not.be.visible') // scroll the button into view, as if the user had scrolled cy.get('#scroll-horizontal button').scrollIntoView() .should('be.visible') cy.get('#scroll-vertical button') .should('not.be.visible') // Cypress handles the scroll direction needed cy.get('#scroll-vertical button').scrollIntoView() .should('be.visible') cy.get('#scroll-both button') .should('not.be.visible') // Cypress knows to scroll to the right and down cy.get('#scroll-both button').scrollIntoView() .should('be.visible') }) it('.trigger() - trigger an event on a DOM element', () => { // To interact with a range input (slider) // we need to set its value & trigger the // event to signal it changed // Here, we invoke jQuery's val() method to set // the value and trigger the 'change' event cy.get('.trigger-input-range') .invoke('val', 25) .trigger('change') .get('input[type=range]').siblings('p') .should('have.text', '25') }) it('cy.scrollTo() - scroll the window or element to a position', () => { // You can scroll to 9 specific positions of an element: // ----------------------------------- // | topLeft top topRight | // | | // | | // | | // | left center right | // | | // | | // | | // | bottomLeft bottom bottomRight | // ----------------------------------- // if you chain .scrollTo() off of cy, we will // scroll the entire window cy.scrollTo('bottom') cy.get('#scrollable-horizontal').scrollTo('right') // or you can scroll to a specific coordinate: // (x axis, y axis) in pixels cy.get('#scrollable-vertical').scrollTo(250, 250) // or you can scroll to a specific percentage // of the (width, height) of the element cy.get('#scrollable-both').scrollTo('75%', '25%') // control the easing of the scroll (default is 'swing') cy.get('#scrollable-vertical').scrollTo('center', { easing: 'linear' }) // control the duration of the scroll (in ms) cy.get('#scrollable-both').scrollTo('center', { duration: 2000 }) }) }) |
In the above code, we covered the below cases :
- In the first case, we are opening the website and typing an email address in one text box. Additionally, we are doing an assertion of the same as well. Moreover, there have been multiple options practiced with type command for typing particular character sequences or special keys. After that, there are assertions to check the disabled of any input.
- The second case is about focussing on a web element. Additionally, it verifies the assertion for the same and also its properties.
- Thirdly, the case is about blur-off a DOM element and verifying the assertion for the same. Moreover, it also verifies its properties.
- Fourthly, we are learning a clear command of how we can clear the input or text area element. Moreover, we verify that it should have an empty value.
- The fifth case is “it” block, where we are checking how we can submit a form. Additionally, we also verify the contain assertion along with it.
- Sixthly, we are checking how we can use click command for a DOM element along with different options of clicking it on different positions.
- In the seventh case, we are verifying the double click command for an element. Additionally, we also carry out the assertions.
- Eighthly, the case involves checking how to check a checkbox or radio element. Additionally, it verifies that the desired action has taken place and ensures the accomplishment of the work.
- In the ninth case, we are verifying how to uncheck a checkbox or radio element. Moreover, we ensure the necessary verifications.
- The tenth case explains how to work with a dropdown where we have to select an option from <select> tag.
- In the 11th case of “it” block, the scrollIntoView( ) command is explained. Additionally, it also includes different usages of what options we can use for scrolling.
- After that, the “it” block explains how we can trigger an event on a DOM element.
- Lastly, we have the scrollTo( ) command and its different usages that how we can scroll on a specific DOM element.
Finally, let’s run the complete test case. Subsequently, it will show the result as follows:
Consequently, as highlighted in the above screenshot, we can see that all test cases we run to cover the UI interaction and its actions have passed. Additionally, I would suggest, please take out some time here to expand through every test and see on the test runner how every command performed on the designated website. The reason being, you will find different situations in your automation journey.
Key Takeaways
- Cypress provides various commands like click(), dblclick(), rightclick(), type() etc. Additionally, these commands simulate user actions on the UI elements.
- Moreover, Cypress internally performs various pre-checks to ensure that the UI element is in the interactable state, before firing the command for the element.
Category: CypressBy Aashish KhetarpalApril 4, 2020
注明本文转载于:https://www.toolsqa.com/cypress/cypress-commands-ui-interaction-commands/
Cypress Commands – UI Interaction Commands相关推荐
- 使用Cypress进行UI测试(一)安装Cypress第一个测试用例
使用Cypress进行UI测试(一)安装Cypress&第一个测试用例 Cypress简介 安装cypress并运行官网示例 项目结构介绍 用例结构介绍 第一个测试用例 Cypress简介 C ...
- Cypress系列(63)- 使用 Cypress.Commands 完成 Custom Commands 自定义命令
如果想从头学起Cypress,可以看下面的系列文章哦 https://www.cnblogs.com/poloyy/category/1768839.html Custom Commands 自定义命 ...
- python commands模块_python commands模块在python3.x被subprocess取代
subprocess 可以执行shell命令的相关模块和函数有: os.system os.spawn os.popen --废弃 popen2.* --废弃 commands.* --废弃,3.x中 ...
- pycharm、webstorm 命令行 Smart commands execution Highlighted commands can be interpreted and executed
解决办法 https://intellij-support.jetbrains.com/hc/en-us/community/posts/360008464899-What-s-the-smart-c ...
- Z-Stack Home Developer's Guide—6. Clusters, Commands and Attributes中文翻译【Z-Stack Home 1.2.0的开发文档】
这篇文章将翻译Z-Stack Home Developer's Guide开发文档中的6. Clusters, Commands and Attributes部分,在Z-Stack中Cluster.C ...
- Python 标准库之 commands
1. 背景 关于 commands 的说明: python 3.0 之后移除此命令,使用 subprocess代替: python 3.x 使用 subprocess 创建一个新进程: 最开始的时候用 ...
- python commands_Windows环境下使用python的commands.getstatusoutput
windows调用系统或其他脚本的,常用的是os.popen,次命令本身并不返回执行后的状态,无法用于后续的判断,故尝试Unix下的commands.getstatusoutput,发现在window ...
- (转载)python调用shell命令之os 、commands、subprocess
linux系统下进入python交互式环境: 一.os 模块 1.1.os模块的exec方法簇: python交互界面中: In [1]: import osIn [2]: os.exec os.ex ...
- 比selenium体验更好的ui自动化测试工具: cypress介绍
话说 Cypress is a next generation front end testing tool built for the modern web. And Cypress can tes ...
最新文章
- 权限表管理之更新权限表数据
- springMVC入门配置及helloworld实例
- 百度地图坐标系相关学习总结
- mysql base64 乱码_PHP base64编码后解码乱码的解决办法
- spring配置mysql事务管理_Spring 数据库事务管理机制
- centos7没有安装ifconfig命令的解决方法
- 02333自考软件工程知识点总结、考点串讲、考前复习
- iOS IOS开发中各种型号的分辨率总结
- python基础之列表函数(10)
- 计算机的工作原理(冯诺依曼体系)
- 2014年12月CCF软考试题
- 软工网络15个人阅读作业2 201521123023 网络1511 戴建钊
- 跨namespace通信
- 手机抓包获取数据,ROOT权限获取,xian鱼,taobao
- matlab ax=b x=,matlab 求解 Ax=B 时所用算法
- oracle rdbms 占CPU,求助,数据库某个进程cpu占用高
- 一本通1032、2032、2048
- 《字字带泪——写在三十岁到来这一天》 By 王潇
- 盘点百度AI To B的2019:“云+AI”突围之年
- ASP.NET Core 修改开源协议为MIT,.NET全平台 MIT协议开源了