mirror of
https://github.com/discourse/discourse-ai.git
synced 2025-02-07 12:08:13 +00:00
3f9973586e
Previous to this change we relied on client side settings to determine if an end user has access to the ai bot. This meant that if a user was not aware they are a member of a group (as it is with restricted visibility ones) they would not see the bot button. All checking has now moved to the server side, and tests were added to cover.
37 lines
1.1 KiB
Ruby
37 lines
1.1 KiB
Ruby
# frozen_string_literal: true
|
|
RSpec.describe "AI chat channel summarization", type: :system, js: true do
|
|
fab!(:user) { Fabricate(:user) }
|
|
fab!(:group) { Fabricate(:group, visibility_level: Group.visibility_levels[:staff]) }
|
|
|
|
before do
|
|
SiteSetting.ai_bot_enabled = true
|
|
SiteSetting.ai_bot_enabled_chat_bots = "gpt-4|gpt-3.5-turbo"
|
|
SiteSetting.ai_bot_allowed_groups = group.id.to_s
|
|
sign_in(user)
|
|
end
|
|
|
|
it "does not show AI button to users not in group" do
|
|
visit "/latest"
|
|
expect(page).not_to have_selector(".ai-bot-button")
|
|
end
|
|
|
|
it "shows the AI bot button, which is clickable (even if group is hidden)" do
|
|
group.add(user)
|
|
group.save
|
|
|
|
visit "/latest"
|
|
expect(page).to have_selector(".ai-bot-button")
|
|
find(".ai-bot-button").click
|
|
|
|
expect(page).to have_selector(".ai-bot-available-bot-content")
|
|
find("button.ai-bot-available-bot-content:first-child").click
|
|
|
|
# composer is open
|
|
expect(page).to have_selector(".d-editor-container")
|
|
|
|
SiteSetting.ai_bot_add_to_header = false
|
|
visit "/latest"
|
|
expect(page).not_to have_selector(".ai-bot-button")
|
|
end
|
|
end
|