gitlab-org--gitlab-foss/spec/factories/broadcast_messages.rb

FactoryGirl.define do
  factory :broadcast_message do
    message "MyText"
    starts_at 1.day.ago
    ends_at 1.day.from_now

    trait :expired do
      starts_at 5.days.ago
      ends_at 3.days.ago
    end

    trait :future do
      starts_at 5.days.from_now
      ends_at 6.days.from_now
    end
  end
end
Broadcast message model + migrations Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2013-11-12 11:47:28 +00:00			`FactoryGirl.define do`
			`factory :broadcast_message do`
			`message "MyText"`
TST: Use more accurate time windows so tests do not fail Currently, the way the 'starts_at' and 'ends_at' attributes are set, if the specs are run at one second to midnight, the broadcast message will expire in one second. I have changed it so that we are guaranteed a period of one day until expiration. I believe this is the desired behaviour and it's also consistent with the rest of the factory. This corrects the following three specs that can fail depending upon where and when they are run: ./spec/helpers/broadcast_messages_helper_spec.rb:42 ./spec/models/broadcast_message_spec.rb:26 ./spec/models/broadcast_message_spec.rb:47 2016-08-04 00:42:18 +00:00			`starts_at 1.day.ago`
			`ends_at 1.day.from_now`
Simplify BroadcastMessage factory Also make the feature tests less brittle. 2015-12-31 21:04:07 +00:00
			`trait :expired do`
			`starts_at 5.days.ago`
			`ends_at 3.days.ago`
			`end`
Update BroadcastMessage model - Adds default values for `color` and `font` attributes - Adds `active?`, `started?`, `ended?`, and 'status' methods 2015-12-31 22:07:11 +00:00
			`trait :future do`
			`starts_at 5.days.from_now`
			`ends_at 6.days.from_now`
			`end`
Broadcast message model + migrations Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2013-11-12 11:47:28 +00:00			`end`
			`end`