e38fc319dc
* Change account and user fabricators to simplify and improve tests - `Fabricate(:account)` implicitly fabricates an associated `user` if no `domain` attribute is given (an account with `domain: nil` is considered a local account, but no user record was created), unless `user: nil` is passed - `Fabricate(:account, user: Fabricate(:user))` should still be possible but is discouraged. * Fix and refactor tests - avoid passing unneeded attributes to `Fabricate(:user)` or `Fabricate(:account)` - avoid embedding `Fabricate(:user)` into a `Fabricate(:account)` or the other way around - prefer `Fabricate(:user, account_attributes: …)` to `Fabricate(:user, account: Fabricate(:account, …)` - also, some tests were using remote accounts with local user records, which is not representative of production code.
36 wiersze
937 B
Ruby
36 wiersze
937 B
Ruby
require 'rails_helper'
|
|
|
|
RSpec.describe BlockService, type: :service do
|
|
let(:sender) { Fabricate(:account, username: 'alice') }
|
|
|
|
subject { BlockService.new }
|
|
|
|
describe 'local' do
|
|
let(:bob) { Fabricate(:account, username: 'bob') }
|
|
|
|
before do
|
|
subject.call(sender, bob)
|
|
end
|
|
|
|
it 'creates a blocking relation' do
|
|
expect(sender.blocking?(bob)).to be true
|
|
end
|
|
end
|
|
|
|
describe 'remote ActivityPub' do
|
|
let(:bob) { Fabricate(:account, username: 'bob', protocol: :activitypub, domain: 'example.com', inbox_url: 'http://example.com/inbox') }
|
|
|
|
before do
|
|
stub_request(:post, 'http://example.com/inbox').to_return(status: 200)
|
|
subject.call(sender, bob)
|
|
end
|
|
|
|
it 'creates a blocking relation' do
|
|
expect(sender.blocking?(bob)).to be true
|
|
end
|
|
|
|
it 'sends a block activity' do
|
|
expect(a_request(:post, 'http://example.com/inbox')).to have_been_made.once
|
|
end
|
|
end
|
|
end
|