Skip navigation
Help

Unit-testing frameworks for Ruby

warning: Creating default object from empty value in /var/www/vhosts/sayforward.com/subdomains/recorder/httpdocs/modules/taxonomy/taxonomy.pages.inc on line 33.

Stack Exchange

This Q&A is part of a weekly series of posts highlighting common questions encountered by technophiles and answered by users at Stack Exchange, a free, community-powered network of 90+ Q&A sites.

lurkerbelow is the only developer at his company writing unit tests. Management, developers, everyone says they want to write unit tests, but nobody does. To bring developers into line, lurkerbelow has introduced pre-commit code review (Gerrit) and continuous integration (Jenkins). Not working. "How do I motivate my fellow coworkers to write unit tests?" he asks.

Practical deomonstrations help

jimmy_keen Answers (32 votes):

Read 22 remaining paragraphs | Comments

0
Your rating: None

Stack Exchange

This Q&A is part of a weekly series of posts highlighting common questions encountered by technophiles and answered by users at Stack Exchange, a free, community-powered network of 90+ Q&A sites.

Mag20 wants to implement automated testing at his company. Problem is, he's tried several times before, but has failed every time. "Everyone gets excited for the first month or two," he writes. "Then, several months in, people simply stop doing it." But now seems like the right time to try bringing automated testing back to the workplace—Mag20's team of 20 experienced developers are about to embark on a big new project.

How can he finally introduce automated testing at his company?

Read 20 remaining paragraphs | Comments

0
Your rating: None