discourse/spec/integration/user_api_keys_spec.rb

# frozen_string_literal: true

require 'rails_helper'

describe 'user api keys integration' do

  fab!(:user_api_key) { Fabricate(:readonly_user_api_key) }

  it 'updates last used time on use' do
    user_api_key.update_columns(last_used_at: 7.days.ago)

    freeze_time
    get '/session/current.json', headers: {
      HTTP_USER_API_KEY: user_api_key.key,
    }
    expect(user_api_key.reload.last_used_at).to eq_time(Time.zone.now)
  end
end
DEV: use #frozen_string_literal: true on all spec This change both speeds up specs (less strings to allocate) and helps catch cases where methods in Discourse are mutating inputs. Overall we will be migrating everything to use #frozen_string_literal: true it will take a while, but this is the first and safest move in this direction 2019-04-30 08:27:42 +08:00			`# frozen_string_literal: true`

FEATURE: Automatically expire keys if not used for a configurable amount of time. (#6264) 2018-08-20 23:36:14 +08:00			`require 'rails_helper'`

			`describe 'user api keys integration' do`

DEV: Prefabrication (test optimization) (#7414) * Introduced fab!, a helper that creates database state for a group It's almost identical to let_it_be, except: 1. It creates a new object for each test by default, 2. You can disable it using PREFABRICATION=0 2019-05-07 11:12:20 +08:00			`fab!(:user_api_key) { Fabricate(:readonly_user_api_key) }`
FEATURE: Automatically expire keys if not used for a configurable amount of time. (#6264) 2018-08-20 23:36:14 +08:00
			`it 'updates last used time on use' do`
			`user_api_key.update_columns(last_used_at: 7.days.ago)`

			`freeze_time`
			`get '/session/current.json', headers: {`
			`HTTP_USER_API_KEY: user_api_key.key,`
			`}`
FEATURE: unconditionally update Topic updated_at when posts change in topic Previously we would bypass touching `Topic.updated_at` for whispers and post recovery / deletions. This meant that certain types of caching can not be done where we rely on this information for cache accuracy. For example if we know we have zero unread topics as of yesterday and whisper is made I need to bump this date so the cache remains accurate This is only half of a larger change but provides the groundwork. Confirmed none of our serializers leak out Topic.updated_at so this is safe spot for this info At the moment edits still do not change this but it is not relevant for the unread cache. This commit also cleans up some specs to use the new `eq_time` matcher for millisecond fidelity comparison of times Previously `freeze_time` would fudge this which is not that clean. 2019-03-28 14:28:01 +08:00			`expect(user_api_key.reload.last_used_at).to eq_time(Time.zone.now)`
FEATURE: Automatically expire keys if not used for a configurable amount of time. (#6264) 2018-08-20 23:36:14 +08:00			`end`
			`end`