Message from JavaScript discussions

October 2017

— Like, user behaviour?


#bdd is a way to express the user interactions with the system you build . for #example

In order to sell products by the website
As Seller
I want to register new product

this simple 3 lines show the user prespective off what is his goal . and who is it . what he want to do . then after those simple description lines the developer write the steps to give the user what he or she want . for #example

Sceniero: Product Registration Successfully
Given I am Loged in User
When I go to Product Registeration Form
And Fill The form correctly
Then I see my Product Registered Successfully

this 5 lines can be converted to real code and been test . with tools like #cucumber and #behat (for php)

— TRGWII this is ome examples about #bdd

— Https://

— When I write applications, BDD is the first extension of my model specification :)

— I have domain-driven design on my resume haha

— So the same as integration tests


var Person = function(name) { = name; };

Why should i use:
 Person.prototype.getName = function() { return; };

Instead of:

var Person = function(name) { = name;
this.getName = function(){

Message permanent page

— Why not use the new class feature from es6
class Person {
get name () {
return 'some thing'

— What if you need some sort of inhertance ?

— Why not class syntax ?

— Because in the first example you only define TWO functions, while the second example defines a function per instance you create

Message permanent page