One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
var libxmljs = require("libxmljs"); | |
var xml = [ | |
'<?xml version="1.0" encoding="utf-8"?>', | |
'<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">', | |
' <soap:Body>', | |
' <Response xmlns="http://tempuri.org/">', | |
' <Result>', | |
' <client xmlns="">', | |
' <msg>SEARCH OK.</msg>', | |
' <code>0</code>', |
/** | |
* With this helper you can start emulators from the command line with some easy questions. | |
* It will automatically list all AVD's that you've configuered on your machine. | |
* | |
* NOTE 1: MAKE SURE YOU'VE ADDED inquirer WITH `npm install inquirer --D` TO YOUR DEV DEPENDENCIES | |
* NOTE 2: MAKE SURE YOU'VE SETUP UP YOUR ENVIRONMENT CORRECTLY WITH ALL THE ENVIRONMENT VARIABLES NEEDED | |
* FOR MAKING ANDROID WORK ON YOUR MACHINE | |
* NOTE 3: MAKE SURE YOU'VE SET THE `ANDROID_EMULATOR_PATH` TO THE CORRECT PATH ON YOUR MACHINE | |
* WHERE ALL THE EMULATORS ARE LISTED | |
* |
/** | |
* Here you'll find some swipe methods for a native iOS or Android app | |
* which can be used when you are using webdriver.io | |
* | |
* I work a lot based on percentages, so it is working on all screens and all devices | |
* and I hope you understand how to use it based on the docs. | |
* | |
* Feel free to use it for all kinds of purposes, a star is much appreciated ;-) | |
* | |
* Grtz, |
btn Button chk CheckBox ckl CheckedListBox | |
cmb ComboBox dtp DateTimePicker lbl Label | |
llb LinkLabel lst ListBox lvw ListView | |
mtx MaskedTextBox cdr MonthCalendar icn NotifyIcon | |
nud NumeircUpDown pic PictureBox prg ProgressBar | |
rdo RadioButton rtx RichTextBox txt TextBox | |
tip ToolTip tvw TreeView wbs WebBrowser | |
容器 | |
flp FlowLayoutPanel grp GroupBox pnl Panel |
node_modules | |
*.swp |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
var Article = require('../../../models/article');
Those suck for maintenance and they're ugly.
As the web component specs continue to be developed, there has been little information on how to test them.
In particular the /deep/
combinator has been deprecated in Shadow DOM 1.0. This is particularly painful since
most end-to-end testing frameworks rely on elements being discoverable by XPath or calls to querySelector.
Elements in Shadow DOM are selectable by neither.
Webdriver.io has the standard actions by selectors, but also allows browser executable scripts to return an element
Bunch of stuff broken? Don't fear..the Actions API is on it's way and it will probably be a good thing! Chin up! | |
OVERVIEW: | |
The purpose of this document is to explain the new actions API and what it has to do with certain commands | |
such as moveto and keys being depricated in webdriverio (due to them being deprecated in certain browser drivers). | |
MAIN ISSUE: | |
1. The issue is that these new drivers suppress these commands on purpose because they are deprecated, | |
but the drivers have not yet implemented the new WC3 standard called "actions API". | |
"The user-facing API for emulating complex user gestures. Use this class rather than using the Keyboard or Mouse directly." |
// # Mocha Guide to Testing | |
// Objective is to explain describe(), it(), and before()/etc hooks | |
// 1. `describe()` is merely for grouping, which you can nest as deep | |
// 2. `it()` is a test case | |
// 3. `before()`, `beforeEach()`, `after()`, `afterEach()` are hooks to run | |
// before/after first/each it() or describe(). | |
// | |
// Which means, `before()` is run before first it()/describe() |