25 Feb, 2013

1 commit

18 Feb, 2013

1 commit

11 Feb, 2013

1 commit

05 Feb, 2013

1 commit

31 Jan, 2013

1 commit

18 Jan, 2013

1 commit

05 Jan, 2013

1 commit

04 Jan, 2013

3 commits

03 Jan, 2013

2 commits

02 Jan, 2013

1 commit

20 Dec, 2012

1 commit

15 Dec, 2012

1 commit

25 Nov, 2012

1 commit

24 Nov, 2012

1 commit

23 Nov, 2012

1 commit

22 Nov, 2012

1 commit

20 Nov, 2012

1 commit

19 Nov, 2012

1 commit

13 Nov, 2012

1 commit

17 Oct, 2012

2 commits

02 Oct, 2012

1 commit

26 Sep, 2012

2 commits

05 Sep, 2012

1 commit

30 Aug, 2012

1 commit

29 Aug, 2012

2 commits

28 Aug, 2012

1 commit

21 Aug, 2012

1 commit

10 Aug, 2012

1 commit

31 Jul, 2012

1 commit

19 Jul, 2012

1 commit

02 Jul, 2012

2 commits

26 Jun, 2012

1 commit

20 Jun, 2012

1 commit

  • dfb5da9d   Disable observers in specs. Enable only when observer is under test. ... Browse File » 
    Used the built-in observer enable/disable feature in ActiveModel[1].
ActiveRecord::Base includes ActiveModel::Observing which provides this
behavior.

Simple wraps to enable the observer under test were added to the specs
for: ActivityObserver, IssueObserver, Admin::Users and Issues.

The spec for Project.last_activity was refactored to separate the tests
for #last_activity and #last_activity_date. Each had doubles added to
isolate the spec from the hidden dependency on the ActivityObserver
action to create an Event for the project when an Issue is created. This
ActivityObserver behavior is already tested by its spec.

[1] http://api.rubyonrails.org/classes/ActiveModel/ObserverArray.html
    Robb Kidd