Skip to content
The same JavaScript test coded using: javascript, node, cucumber, jasmine, jest, mocha, nightmarejs, nightwatch, assert, chai, nightwatch-api, protractor, puppeteer, webdriver, webdriverio, zombiejs (in folder: tests/UI). Plus a basic workshop of building an app build and deployment pipeline: GitHub -> HTML -> Tests -> Travis CI-> Netlify Cloud
JavaScript HTML Shell Gherkin
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
api
ci
conf
docs
tests
web
.eslintrc.js
.gitignore
.gitlab.yml
.travis.yml
README.md
codesandbox.png
netlify.toml
package-lock.json
package.json
run-all-tests.sh
set-up.sh

README.md

Build Status

A very important thing to remember when looking at code ...

Don't try and process all the lines at once, guaranteed brain-freeze. Look at each line, and check if you can actually work out what the line is doing. If you don't know, go to the next line and so on. You will probably find that by doing this way, previous lines that were a mystery suddenly become clearer.

Things to remember

  • It's just another language
  • You will recognise parts because of your existing general language knowledge
  • Commonly coding terms are close to a natural language word (e.g. "try") with a loose association with the orginal meaning, i.e. not a way you would talk in normal conversation.
  • Think of this as more of a puzzle (sometimes just basic mathematics)
  • Some times there are parts of coding you will need to look up or be told.
You can’t perform that action at this time.