Test units of code, pieces together, or the full-fledged application
To help with that problem, in this article I’ll give you a guide comparing the different kinds of testing types available, and some recommendations for their use.
Read the article at codeutopia.net
MS Edge adds ES6 features including import and export
Most of ES2015 (aka ES6) language support is already available in Edge, and last week’s Windows Insider Preview build 14342 brings more ES6 capabilities including modules, default parameters, and destructuring. We’re not stopping there – Edge also supports all ES2016 (aka ES7) proposals – the exponentiation operator and Array.prototype.includes – as well as future ECMAScript proposals such as Async Functions and utility methods like Object.values/entries and String.prototype.padStart/padEnd.
Read more from the source: Microsoft Edge Dev Blog
Come on TC39, V8 and Node have implemented all but the most obscure parts of ES6–where is the standard for import?
NodeJS 6.1 passes 96% of ES6 tests, failing only on proper tail calls, iterator closing, and some Proxying of internal `get` calls.
But no standard is in sight for resolving resources based on the string in import statements.
View the compatibility table results at node.green
This is a demonstration of all the data your browser knows about you. All this data can be accessed by any website without asking you for any permission.
Run the test for yourself at webkay.robinlinus.com
npm decides to keep their unpublish functionality but puts in place rules to prevent breaking other packages
npm writes on their blog:
One of Node.js’ core strengths is the community’s trust in npm’s registry. As it’s grown, the registry has filled with packages that are more and more interconnected.
A byproduct of being so interdependent is that a single actor can wreak significant havoc across the ecosystem. If a publisher unpublishes a package that others depend upon, this breaks every downstream project that depends upon it, possibly thousands of projects.
Last Tuesday’s events revealed that this danger isn’t just hypothetical, and it’s one for which we already should have been prepared. It’s our mission to help the community succeed, and by failing to protect the community, we didn’t uphold that mission.
Read the whole post
All engineers write bad code. The best engineers think hard about how to refactor avoid the situation in the future.
“Excellence is never an accident. It is always the result of high intention, sincere effort, and intelligent execution; it represents the wise choice of many alternatives – choice, not chance, determines your destiny.” – Aristotle
Read more at The Full Stack