Category Archives: UnitTests

last day at be2, my career at be2 in a sequence of words

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on February 11, 2011 by Narek Alaverdyan

software engineering, java, j2ee, jboss, mysql email marketing, blacklisting, smtp, rmi, jms, crm, friends, travel, munich, specification, review, coding, esp, project management, gantt chart, matchmaking, tracking, pixels, company event, travelling, hibernate, spring, tomcat, invoker, redundancy, scalability, data complexity, performance,  partitioning, sharding, activemq, broker, soap, http call, queue, strategy, social networks, facebook, lean, agile, architecture,  scrum, scrum alliance, agile manifesto, sprint, continuous integration, hudson, static code analysis, transparency, communication, iteration, definition of done, spm, srm, user story, failure, success, confidence level, pair programming, retrospectives, groovy, grails, nosql, mongodb, rest, jersey, value stream, london, development management Continue reading →

Posted in Agile, Definition of Done, NoSQL, SCRUM, UnitTests, development, dynamic languages, groovy, pair programming, programming style, tdd, test-driven-development, value stream | Tagged , , , , , | 1 Comment

Build quality in every line of code produced

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on January 17, 2011 by Narek Alaverdyan

There is one thing in common with a lot of software development companies, or companies that have a software development unit. That’s the system labeled with the monstrous name “Legacy”.

So what’s in it, really?

Is your software change tolerant? Is your software easy to adapt to changes proposed by the business, or the tech department itself? Are you software’s modules independent and enable change? Does your software enable quick releases?

If you were nodding your head negatively about all of the above mentioned questions, then… I am really sorry but you’re dealing with Legacy software.

There’s something else that makes the system Continue reading →

Posted in Agile, Lean, UnitTests, build quality in, development, testing | Tagged , , , , , | 18 Comments

The Definition of Done (DoD)

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on January 4, 2011 by Narek Alaverdyan

What is a Definition of Done?

Definition of Done is a crucial element of a successful scrum software development. When defined and followed, makes sure that when someone says that a task is done. There is an explicit understanding what it means.

For completeness and integrity you would have 3 different definitions of done: for a User Story (a feature), for a Sprint and for a Release. This is also in line with the SCRUM Alliance recommendation.

A User Story Definition of Done

So, let’s pick the User Story DoD, and elaborate more. The User Story DoD’s Continue reading →

Posted in Agile, Automated Testing, Definition of Done, SCRUM, UnitTests, testing | Tagged , , , , , , , | 25 Comments

Fighting the Software Uncertainty principle. SCRUM+TDD+CI+SELENIUM+cfEngine

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on December 20, 2010 by Narek Alaverdyan

“The outcome of the execution of E-type software entails a degree of uncertainty, the outcome of execution cannot be absolutely predicted”, or more fully, “Even if the outcome of past execution of an E-type program has previously been admissible, the … Continue reading →

Posted in Agile, Automated Testing, Definition of Done, SCRUM, UnitTests, checkstyle, programming style, tdd, test-driven-development | Tagged , , , , | 8 Comments

What does TDD have to offer?

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on November 21, 2010 by Narek Alaverdyan

There is no difference between the notion of Test-Driven-Development and that of Test-Driven-Design; rather the former implies the later, meaning the Test-Driven-Development brings to Test-Driven-Design. The benefits of TDD are obvious, many studies have been carried out and some say … Continue reading →

Posted in UnitTests, tdd, test-driven-development, testing | Tagged , | 2 Comments

to Scala or not to Scala />?

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on November 16, 2010 by Narek Alaverdyan

In a number of sessions I have attended in Software Architect 2010, the speakers mentioned Scala many times, particularly stating that Java is limited and that Scala is great both, since it follows the Functional Programming paradigm (not like Java … Continue reading →

Posted in Functional Programming, Multi-Paradigm-Programming, Scala, UnitTests, dynamic languages | 1 Comment