ECLint is a tool for validating or fixing code that doesn’t adhere to settings defined in .editorconfig. It also infers settings from existing code. See the EditorConfig Project for details about the .editorconfig file.
A free chapter of the book “Continuous Delivery”: Anatomy of the Deployment Pipeline.
Mandatory reading for mobile testing.
THERE IS NO SUCH THING AS “THE” ANDROID BROWSER
Memorable site for testing clients against bad SSL configs. https://badssl.com
Ruby exposes several different methods for handling equality:
a.equal?(b) # object identity - a and b refer to the same object a.eql?(b) # object equivalence - a and b have the same value a == b # object equivalence - a and b have the same value with type conversions
rspec-expectations ships with matchers that align with each of these methods:expect(a).to equal(b) # passes if a.equal?(b) expect(a).to eql(b) # passes if a.eql?(b) expect(a).to be == b # passes if a == b
It also ships with two matchers that have more of a DSL feel to them:expect(a).to be(b) # passes if a.equal?(b) expect(a).to eq(b) # passes if a == b
It turns out that this works:
login_page.fill_in login_page.email[:name], with: ‘email@example.com’
The [:name] symbol is any unique input attribute you may have in the code.
will wait (until the default_timeout has elapsed) for #foo. Jus’ sayin, don’t wait() if you don’t have to.