SData is a framework-agnostic, datastore-agnostic ORM (Object-Relational Mapper) for Node.js and the Browser.
Adapters allow JSData to connect to various data sources such as Firebase, MySql, MongoDB, REST API, etc.
With JSData you can re-use your data modeling code between environments, and work with a unified data API on the server and the client.
JSData employs conventions for rapid development but allows for endless customisation in order to meet your particular needs.
Considering the use of JSData with JSON-API standards, there are couple of adapters that transpile JSData to JSON-API.
After the release of Headless Chrome browser (v59+) most of the automation tools slowly started reducing the usage of Selenium, by replacing it with the combination of chromedriver + chrome/chromium pre-installed browser (like Travis CI does on their images).
What I wanted was user automation, emulating browsers Page Object Model (POM). The choice fell on NightwatchJS library that works with headless Chrome and needs only minor tweaking.
Setting up NightwatchJS
I’ve used a combination of NightwatchJS with Mocha test framework. Even, Nightwatch has its own support of assertion methods for checks on the browser requests.
sudo: true dist: trusty language: php php: - 5.6 - 7.0 - 7.1 - nightly enabling NodeJS node_js: - "7" setting up stable Chrome, which has headless support out of the box addons: chrome: stable caching Yarn and its node_modules cache: yarn: true directories: - node_modules installing JS packages and starting up the server before_script: - yarn install - ./bin/phpserv >/dev/null 2>&1 & - sleep 5 # once you're done with PHPUnit/PHPCS, # it's time to check the UI with yarn testscript: - ./vendor/bin/phpunit --group example - ./vendor/bin/phpunit --exclude-group example - ./vendor/bin/phpcs - yarn test
The devil is in details, so people say. Few months ago, while working on prototype of cakephp-calendar, we had an interesting debate over front-end stack for Calendar component.
At the same time, WordPress community was buzzing about their text editor – Gutenberg whether to use ReactJS vs VueJS libraries. One of the reasons of choosing VueJS, was licensing agreement.
The license granted hereunder will terminate, automatically and without notice, if you (or any of your subsidiaries, corporate affiliates or agents) initiate directly or indirectly, or take a direct financial interest in, any Patent Assertion…(c)
Investing man-hours into VueJS research and prototyping was right, especially after Raul Kripalani published an interesting article on the license review of ReactJS.