tamlyn

//////// CONFIG /////////

// your first direct user name
const username = ''
// your password (the one it asks for characters from)
const password = ''
// your memorable word
const memorable = ''
// set to false if you want to see the browser window as it runs
const headless = true

tamlyn

// a very short Cypress test suite
describe('Admin user', () => {
  it('Create posts journey', () => {
    const postTitle = 'Hello testing'
    cy.get('input[id=title]').type(postTitle)
    cy.get('button[title=Create]').click()
    cy.get('table tr:last label').should('contain', postTitle)
  })
})

tamlyn

// a very short TestCafe test suite
fixture('Admin user')
test('Create posts journey', t => {
  const postTitle = 'Hello testing'
  return t
    .typeText(ReactSelector('PostCreator FormControl'), postTitle)
    .click(ReactSelector('PostCreator Button'))
    .expect(ReactSelector('Post').first().find('label').innerText)
    .eql(postTitle)
})

tamlyn

Demo showing that by specifying a resolver for a scalar property, you can override the value.

This is useful for authorization as it means you can centrally check permissions per field. Your general resolvers can return whole objects without caring about which fields the current user may or may not be allowed to see.

tamlyn

Test case

Bug when running Testcafe on Slate Editor inputs in Chrome/Safari

1. Serve index.html on port 8080, e.g. http-server
2. Run test, e.g. testcafe chrome test.js

Expected

New text is appended to input

Actual

tamlyn

Keybase proof

I hereby claim:

• I am tamlyn on github.
• I am tamlyn (https://keybase.io/tamlyn) on keybase.
• I have a public key ASDtLiAyqvI_72LatdxQWOQhNvOLwyMJZtFU0PRAywgROAo

To claim this, I am signing this object:

tamlyn

Shows a list of all node processes and lets you select which one you want to debug.

For example

$ debug.sh
1) 73428 node webpack/webpackDevServer.js
2) 73494 node build/dist/server.js

Select which process to debug: █

tamlyn

pull-modules () {
  BASE_DIR=$(pwd)

  # find symlinks in node_modules
  for MODULE in $(find node_modules -type l -depth 1)
  do
    cd "$MODULE"
    BRANCH=$(git rev-parse --abbrev-ref HEAD)
    echo "Updating $MODULE ($BRANCH)..."

tamlyn

Execution order of Jest/Jasmine test code

While tests run in source order, surrounding code does not which can lead to hard to debug issues.

Compare the test file below with the sample output below that and note the order of the log messages.

Key points

• Any code not inside of it, beforeAll, afterAll, beforeEach or afterEach runs immediately on initialisation.
• This means code at the end of your file runs before even your before hooks.

tamlyn

before_script: 
  - npm install
test: 
  script: npm test